AB context-not-control
Enable "Context, not Control" workflow - clarify requirements through multi-turn dialogue, reduce rework, and execute with appropriate permission levels. Use when users want AI to take more autonomy, need help clarifying vague requirements, or want to establish trust-based collaboration patterns. Supports three permission levels (Master/Collaborative/Assistant) and automatic context management.
Enable "Context, not Control" workflow - clarify requirements through multi-turn dialogue, reduce rework, and execute with appropriate permission levels.
As a process B 65/100 · Nearly there — weak spots: result and completion, when it triggers, 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: 12. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
edit-residuethe text marks something as outdated (lines 180): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 65/100
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Result and completion. Does not say what the result is
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 79 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1846 tokens
- 100Running it twice. Mutating operations check current state
- low 12 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
- +1No license
- +2Single-language instructions
- +3Description length 397: enough signal without eating the budget
- +4Structure: 32 headings
- +3Step-by-step instructions: 79 items
- +4Has examples (8 code blocks)
- +4Reference files are cited in the instructions (3 of 4)
- +3All 4 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.