BB oma-refactor
Restructure existing code while preserving observable behavior. Use for targeted technical debt or hotspot work with characterization tests.
Restructure existing code while preserving observable behavior.
As a process B 69/100 · Nearly there — weak spots: result and completion, running it twice
This is a copy of a skill from another catalog; the rating counts the canonical one: oma-refactor (first-fluke/oh-my-agent)
How to improve
For the model run — optional
- 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: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
edit-residuethe text marks something as outdated (lines 11, 17): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 69/100
- 0Result and completion. Does not say what the result is
- 30Running it twice. 20 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 82 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3564 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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 140: enough signal without eating the budget
- +4Structure: 25 headings
- +3Step-by-step instructions: 82 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.