CD gov-procurement-analyst
>
>
As a process D 38/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
For the model run — optional
- 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 · 0
✓ No critical or high findings
Files scanned: 12. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Missing closing "quote at line 4, column 178: …compliance_checker核心逻辑做快速路径，跳过深度采集；21+模块复杂度藏在一个钩子后面，对标SkillHub防骗大师102.2万下载传播模型） ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-shortdescription under 40 chars: too little signal for triggering - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 24645 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "changelog"
Process rating: all ten parameters 38/100
- 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
- 0Progress reporting. Says nothing while it works
- 10Execution cost. Instruction body is 24645 tokens: crowds the task out of the window
- 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
- 100Steps. 171 steps
- 100Consistency. Name and required fields are in place
- 100Running it twice. No mutating operations
- low 33 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 1: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -2136 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +4Structure: 177 headings
- +3Step-by-step instructions: 171 items
- +4Has examples (155 code blocks)
- +4Reference files are cited in the instructions (1 of 3)
- +3All 6 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 45.
External checks
ClawHub: suspicious
The skill is purpose-aligned for government procurement analysis, but needs Review because it stores sensitive enterprise/procurement data and overstates local-only privacy despite remote-style fallbacks and integrations.
LLM: suspicious (high) · 9 Oct 2026