SKILLEMALL.ai
GitHub ↗ RU Sign in

AD agentsmd-scaffold

Generate or update repository-specific AGENTS.md instruction files from real repo evidence. Use when asked to create, design, scaffold, split, or improve root or scoped AGENTS.md files for Codex/Claude/agent workflows, especially when a repo needs directory-specific rules, validation commands, generated-file boundaries, or a short agent onboarding router.

majiayu000/spellbook Agent Skills author: majiayu000 MIT 4 files · 1 script body ≈ 1 418 tokens Open the sourcegithub.com↗ analyzed 3 d ago

Generate or update repository-specific AGENTS.md instruction files from real repo evidence. Use when asked to create, design, scaffold, split, or improve root…

As a process D 49/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, failures and branches

GeneratorAI and agentstype 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
96/100
safety, quality, tests
Safety 60%
100
Quality 40%
91
Run on models
none yet
Process rating
D
49/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • 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: 3. 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 49/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 2 mutating operations with no state check
    • 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
    • 70When it triggers. States when to use, but not when not to
    • 100Steps. 32 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1418 tokens
    • medium 3 test cases, all positive: not one "should refuse" or "should ask first"

    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 357: enough signal without eating the budget
    • +4Structure: 11 headings
    • +3Step-by-step instructions: 32 items
    • +4Has examples (2 code blocks)
    • +4Reference files are cited in the instructions (1 of 1)
    • +3All 1 scripts are documented

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