AB sop-generator
Turn messy recordings, transcripts, voice notes, or brain dumps into clean, team-ready Standard Operating Procedures (SOPs). Use when you have Loom videos, meeting transcripts, rough notes, or verbal walkthroughs that need to become documented processes. Covers SOP structure, extraction from various input types, quality checklist, and automation strategies. Trigger on "create SOP", "turn this into an SOP", "document this process", "make this team-ready", "convert transcript to SOP", "write a procedure".
Turn messy recordings, transcripts, voice notes, or brain dumps into clean, team-ready Standard Operating Procedures (SOPs).
As a process B 68/100 · Nearly there — weak spots: result and completion, inputs and preconditions, running it twice
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: 2. 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 68/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 7 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 55Failures and branches. 1 branches
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 68 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2425 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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 6 example trigger phrases
- +3Description length 508: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 68 items
- +4Has examples (5 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 89.