BF 敏感词筛查-CMT-1.0
This skill should be used when the user wants to check files (PDF, Word, Excel) for sensitive/prohibited words from a word library, and highlight them in yellow. The skill has a built-in word library (65 words, 9 categories) and also supports external word files.
This skill should be used when the user wants to check files (PDF, Word, Excel) for sensitive/prohibited words from a word library, and highlight them in…
As a process F 37/100 · Will not run — References files that are not bundled: scripts/sensitive_word_checker.py
The same skill appears in 1 more place: ClawHub
How to improve
- 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 · 0
✓ No critical or high findings
Files scanned: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
missing-refreference to a missing file: scripts/sensitive_word_checker.py - note
frontmatter-keyunknown frontmatter key "agent_created" - note
frontmatter-keyunknown frontmatter key "disable"
Process rating: all ten parameters 37/100
- 0Tools and files. 1 referenced file(s) missing: scripts/sensitive_word_checker.py
- 0Result and completion. Does not say what the result is
- 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
- 40Consistency. Frontmatter name (敏感词筛查-CMT-1.0) differs from the folder (sensitive-word-checker-cmt)
- 70When it triggers. States when to use, but not when not to
- 100Steps. 14 steps
- 100Execution cost. Instruction body is 450 tokens
- 100Running it twice. No mutating operations
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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 263: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 14 items
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.