SKILLEMALL.ai
GitHub ↗ RU Sign in

AB focused-fix

Use when the user asks to fix, debug, or make a specific feature/module/area work end-to-end. Triggers: 'make X work', 'fix the Y feature', 'the Z module is broken', 'focus on [area]'. Not for quick single-bug fixes — this is for systematic deep-dive repair across all files and dependencies.

alirezarezvani/claude-skills Agent Skills author: alirezarezvani MIT 1 file body ≈ 3 330 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Triggers: 'make X work', 'fix the Y feature', 'the Z module is broken', 'focus on [area]'.

As a process B 77/100 · Nearly there — weak spots: inputs and preconditions

GeneratorSoftware developmenttype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
A
94/100
safety, quality, tests
Safety 60%
100
Quality 40%
86
Run on models
none yet
Process rating
B
77/100
Nearly there
Inputs and preconditions w 11
0
Failures and branches w 10
55
Result and completion w 14
60
the three weakest of ten parameters · all ten

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: 1. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note edit-residue the text marks something as outdated (lines 100): check that old rules are not kept next to new ones — the full check reads the text for contradictions

    Process rating: all ten parameters 77/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 55Failures and branches. 1 branches
    • 60Result and completion. Output format stated, no completion criterion
    • 85Steps. 77 steps, 1 vague phrases
    • 100Tools and files. No external tools needed
    • 100When it triggers. States when to use and when not to
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 3330 tokens
    • 100Running it twice. Mutating operations check current state
    • 100Progress reporting. Reports progress

    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
    • -5TODO / placeholder text left in the skill
    • +1No license
    • +2Single-language instructions
    • +4Description says when NOT to use the skill
    • +3Description length 292: enough signal without eating the budget
    • +4Structure: 14 headings
    • +3Step-by-step instructions: 77 items
    • +3Output format is stated explicitly
    • +4Has examples (8 code blocks)

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 86.