CF dev-expert
P8级全栈编程专家(Java/PHP-CMS/前端/MySQL):API设计、Bug诊断、代码生成与审查、重构、测试、性能基准、技术选型、文档、Spec驱动、任务拆解、项目知识图谱,及工程纪律层(根因调试、阶段导航、事故复盘/SLO、威胁建模/供应链、生产就绪/渐进式发布、AI编码治理、Agent可读性、LLM安全、技术战略、技术影响力、效能度量)。支持 @标识 显式调用。
P8级全栈编程专家(Java/PHP-CMS/前端/MySQL):API设计、Bug诊断、代码生成与审查、重构、测试、性能基准、技术选型、文档、Spec驱动、任务拆解、项目知识图谱,及工程纪律层(根因调试、阶段导航、事故复盘/SLO、威胁建模/供应链、生产就绪/渐进式发布、AI编码治理、Agent可读性、LLM安全、…
As a process F 31/100 · No process to follow — References files that are not bundled: FAQ.md, references/<子技能>.md
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 asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 2
✓ No critical or high findings
Medium and low: 2
-
medium Broad scope
meta-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Shell, Bashallowed-tools: Read Grep Glob Shell Bash Edit Write Task WebSearch
-
low Secrets in code
secret-high-entropy-tokenreferences/java-testing.md:54High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file)void crea…201() throws Exception {fixture
Files scanned: 79. 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") - warning
missing-refreference to a missing file: FAQ.md - warning
missing-refreference to a missing file: references/<子技能>.md
Process rating: all ten parameters 31/100
- 0Tools and files. 2 referenced file(s) missing: FAQ.md, references/<子技能>.md
- 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
- 40Consistency. Frontmatter name (dev-expert) differs from the folder (weimingli-123)
- 100Steps. 12 steps
- 100Execution cost. Instruction body is 1903 tokens
- 100Running it twice. No mutating operations
- low 14 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
- +4No input/output examples
- +2Single-language instructions
- +3Description length 188: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 12 items
- +4Reference files are cited in the instructions (9 of 45)
- +3All 2 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.