AC feature-modification-workflow
A structured workflow for modifying existing features. TRIGGER when: user says "I want to change a feature", "optimize xxx", "check if xxx has room for improvement", "fix a bug", or any request involving feature modifications. Choose the appropriate workflow based on scenario complexity: simple issues go straight to code, complex issues follow the full process.
As a process C 63/100 · Has gaps — weak spots: inputs and preconditions, running it twice, progress reporting
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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: A structured workflow for modifying existing features. TRIGGER whe… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 63/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 55Failures and branches. 1 branches
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 100Steps. 73 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2235 tokens
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
- +4Description does not say when NOT to use the skill (false activations)
- +2Single-language instructions
- +5Description quotes 4 example trigger phrases
- +3Description length 363: enough signal without eating the budget
- +4Structure: 28 headings
- +3Step-by-step instructions: 73 items
- +3Output format is stated explicitly
- +4Has examples (7 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.