AC i-have-an-idea
Capture and co-develop a user's new product, feature, experience, architecture, or creative-workflow idea into one traceable, AI-friendly Markdown document without starting implementation. Use on explicit triggers such as "/idea", "我有一个想法", "我想做一个...", "I have an idea", and on high-confidence implicit new directions such as "要是...就好了" or "What if...". For an ambiguous feature-like statement, clarify whether the user wants idea exploration or immediate execution. Do not use for bugs, factual questions, mechanical edits, progress on an existing task, or implementation of an already-understood requirement.
Capture and co-develop a user's new product, feature, experience, architecture, or creative-workflow idea into one traceable, AI-friendly Markdown document…
As a process C 54/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
How to improve
- 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: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 54/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
- 30Running it twice. 1 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 100Tools and files. No external tools needed
- 100Steps. 68 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 907 tokens
- low 10 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
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +5Description quotes 5 example trigger phrases
- +4Description says when NOT to use the skill
- +3Description length 610: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 68 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 89.