CC skills-summarize-audit
面向中文用户，提供技能库翻译精炼、项目画像和基于证据的技能/插件推荐操作。用于“技能审查”“技能翻译精炼”“项目画像”“技能推荐”；结合来源、版本、使用证据、冲突与 MCP/Agent 状态给出优化步骤。默认只读，不执行安装、卸载、配置或发布。
面向中文用户，提供技能库翻译精炼、项目画像和基于证据的技能/插件推荐操作。用于“技能审查”“技能翻译精炼”“项目画像”“技能推荐”；结合来源、版本、使用证据、冲突与 MCP/Agent 状态给出优化步骤。默认只读，不执行安装、卸载、配置或发布。
As a process C 53/100 · Has gaps — 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.
- 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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Secrets in code
secret-high-entropy-tokenscripts/extract_usage_signals.py:612High-entropy token-like string (may be an id, hash or a credential) (placeholder value)# roll…53-<uuid>.jsonl
placeholder
A further 1 matches are quotations in this security skill's documentation and are not counted as findings.
Files scanned: 57. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 53/100
- 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
- 20When it triggers. No condition that starts the skill
- 100Tools and files. No external tools needed
- 100Steps. 12 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 912 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
- +4No input/output examples
- -33 of 7 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +3Description length 122: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 12 items
- +4Reference files are cited in the instructions (16 of 23)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.