AC code-language-analyzer
项目编程语言代码量分析专家。扫描项目目录，统计各编程语言的文件数、代码行数及占比，生成可视化的语言分布报告。当用户需要分析项目使用了哪些语言、各语言代码量占比、技术栈构成、代码行数统计时触发此技能。典型场景包括：分析项目语言占比、统计代码行数、看看这个项目用了哪些语言、分析技术栈、code language analysis 等。
项目编程语言代码量分析专家。扫描项目目录，统计各编程语言的文件数、代码行数及占比，生成可视化的语言分布报告。当用户需要分析项目使用了哪些语言、各语言代码量占比、技术栈构成、代码行数统计时触发此技能。典型场景包括：分析项目语言占比、统计代码行数、看看这个项目用了哪些语言、分析技术栈、code language…
As a process C 57/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches
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 · 0
✓ No critical or high findings
Files scanned: 3. 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") - note
frontmatter-keyunknown frontmatter key "agent_created"
Process rating: all ten parameters 57/100
- 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 (code-language-analyzer) differs from the folder (code-language-analyzer-claw)
- 60Result and completion. Output format stated, no completion criterion
- 100Tools and files. No external tools needed
- 100Steps. 21 steps
- 100Execution cost. Instruction body is 931 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)
- +1No license
- +2Single-language instructions
- +3Description length 166: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 21 items
- +3Output format is stated explicitly
- +4Has examples (6 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.