BD skills-summarize-audit
面向中文用户，审查当前已安装技能与插件的问题、来源、版本、可用性和元数据，并结合用户画像定位、评分、检测触发冲突与能力互补，覆盖 MCP+Agent+Skill 三层生态评估；同时支持可见技能中文翻译精炼、项目画像和技能推荐。用于“技能审查”“技能翻译精炼”“项目画像”“技能推荐”“技能体检”“生态评估”等独立请求；默认只读，不安装、更新、发布、迁移、清理或修改配置。
面向中文用户，审查当前已安装技能与插件的问题、来源、版本、可用性和元数据，并结合用户画像定位、评分、检测触发冲突与能力互补，覆盖 MCP+Agent+Skill…
As a process D 46/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.
- 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:592High-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: 55. 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 46/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
- 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
- 100Steps. 85 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2805 tokens
- 100Running it twice. No mutating operations
- low 11 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)
- +3Output format is not stated: the model decides each time
- -31 of 5 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +3Description length 185: enough signal without eating the budget
- +4Structure: 25 headings
- +3Step-by-step instructions: 85 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (15 of 24)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.