SKILLEMALL.ai
GitHub ↗ RU Sign in

AB invariant-guard

Correctness-first: forces writing the function contract, loop invariant, termination argument, and edge cases BEFORE code. Catches Boyer-Moore, leftmost binary search, QuickSelect traps.

sickn33/agentic-awesome-skills Agent Skills author: sickn33 MIT 1 file body ≈ 4 366 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Correctness-first: forces writing the function contract, loop invariant, termination argument, and edge cases BEFORE code.

As a process B 73/100 · Nearly there — weak spots: inputs and preconditions, running it twice

AnalyzerSoftware 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
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
80
Run on models
none yet
Process rating
B
73/100
Nearly there
Inputs and preconditions w 11
0
Running it twice w 4
30
When it triggers w 12
50
the three weakest of ten parameters · all ten

The same skill appears in 2 more places: agentic-awesome-skills, agentic-awesome-skills

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 frontmatter-key unknown frontmatter key "risk"
    • note frontmatter-key unknown frontmatter key "source"
    • note frontmatter-key unknown frontmatter key "source_repo"
    • note frontmatter-key unknown frontmatter key "source_type"
    • note frontmatter-key unknown frontmatter key "date_added"
    • note frontmatter-key unknown frontmatter key "tools"
    • note frontmatter-key unknown frontmatter key "license_source"

    Process rating: all ten parameters 73/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 30Running it twice. 1 mutating operations with no state check
    • 50When it triggers. No condition that starts the skill
    • 60Result and completion. Output format stated, no completion criterion
    • 70Execution cost. Instruction body is 4366 tokens
    • 100Tools and files. Tools declared in frontmatter
    • 100Steps. 79 steps
    • 100Failures and branches. 2 branches, has a failure section
    • 100Consistency. Name and required fields are in place
    • 100Progress reporting. Reports progress
    • low 16 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)
    • -5TODO / placeholder text left in the skill
    • +2Single-language instructions
    • +3Description length 186: enough signal without eating the budget
    • +4Structure: 19 headings
    • +3Step-by-step instructions: 79 items
    • +3Output format is stated explicitly
    • +4Has examples (5 code blocks)
    • +1License stated

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