BC ideaforge
从模糊想法到可执行方案的完整工作流。 不只是写计划——是把一个念头聊透、选对方案、沉淀成任何 agent 都能接手的文档。 适用于：想做个工具/小产品/页面/功能，但还没想清楚怎么做的人。 触发词：我想做个xxx、帮我做个工具、vibe coding、想做一个东西、有个idea
从模糊想法到可执行方案的完整工作流。 不只是写计划——是把一个念头聊透、选对方案、沉淀成任何 agent 都能接手的文档。 适用于：想做个工具/小产品/页面/功能，但还没想清楚怎么做的人。 触发词：我想做个xxx、帮我做个工具、vibe coding、想做一个东西、有个idea
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 · 0
✓ No critical or high findings
Files scanned: 2. 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. 35 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 447 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
- +1No license
- +2Single-language instructions
- +3Description length 139: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 35 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.