CF kingdoc
(no description)
本版本针对第三方评测(综合 4.5/5「优秀」)的降分项做了逐项闭环: 本地生成文档、本地 OCR、硬件画像完全不需要 Key,开箱即用。
As a process F 29/100 · Will not run — References files that are not bundled: assets/icon.png
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
How to improve
- Add a description to the frontmatter: without it the skill never triggers.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 1
✓ No critical or high findings
Medium and low: 1
-
medium Dangerous commands
cmd-execpolicy-bypassREADME.md:35Runs PowerShell with execution policy bypassedpowershell -ExecutionPolicy Bypass -File D:\skill\kingdoc\setup.ps1
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
description-missingSKILL.md: no `description` — the skill can never trigger - warning
body-longSKILL.md body ≈ 9070 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: assets/icon.png
Process rating: all ten parameters 29/100
- 0Tools and files. 1 referenced file(s) missing: assets/icon.png
- 0Result and completion. Does not say what the result is
- 0When it triggers. No condition that starts the skill
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 30Running it twice. 14 mutating operations with no state check
- 40Execution cost. Instruction body is 9070 tokens: crowds the task out of the window
- 100Steps. 80 steps
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- low 40 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 0: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -5TODO / placeholder text left in the skill
- -286 emoji in the instructions: noise for the model
- -31 of 1 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +4Structure: 128 headings
- +3Step-by-step instructions: 80 items
- +4Has examples (43 code blocks)
- +4Reference files are cited in the instructions (12 of 12)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 14.