SKILLEMALL.ai

AB claude-md-bootstrap

Use when the user wants to create or bootstrap a project-local CLAUDE.md - the auto-loading project context file for the agent. Russian triggers: "сделай/создай проектный CLAUDE.md", "настрой контекст проекта для агента", "забутстрапь CLAUDE.md", "CLAUDE.md для проекта". English triggers: "bootstrap project CLAUDE.md", "set up project agent context". Generates an opinionated CLAUDE.md adapted to project type (code/ops/agent/content): iron rules and gotchas as IF-THEN with primacy+recency placement, a work protocol including a keep-docs-live rule, and progressive-disclosure pointers to docs/ and project memory. Extends an existing CLAUDE.md instead of overwriting. Do NOT use for editing arbitrary files, the generic codebase summary that built-in /init produces, or non-CLAUDE.md docs.

Desko77/claude-code-skills-1c Agent Skills author: Desko77 MIT 1 file body ≈ 2 040 tokens Open the sourcegithub.com↗ analyzed 6 d ago

md - the auto-loading project context file for the agent.

As a process B 71/100 · Nearly there — weak spots: result and completion, inputs and preconditions

GeneratorAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
96/100
safety, quality, tests
Safety 60%
100
Quality 40%
90
Run on models
none yet
Process rating
B
71/100
Nearly there
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
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

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 71/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 60Failures and branches. 2 branches
    • 100Tools and files. No external tools needed
    • 100Steps. 29 steps
    • 100When it triggers. States when to use and when not to
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2040 tokens
    • 100Running it twice. No mutating operations
    • 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

    • +3Output format is not stated: the model decides each time
    • -5TODO / placeholder text left in the skill
    • +1No license
    • +5Description quotes 6 example trigger phrases
    • +4Description says when NOT to use the skill
    • +3Description length 793: enough signal without eating the budget
    • +4Structure: 11 headings
    • +3Step-by-step instructions: 29 items
    • +4Has examples (1 code blocks)
    • +2Bilingual instructions (RU + EN)

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