SKILLEMALL.ai

AC skill-governance

Governs the Claude Code/Codex Skill surface: reconciles source/install/catalog-visibility drift without losing cold capability. Use when users ask how many Skills load, why the catalog is truncated, want routers visible while other bundles stay cold, or need duplicate/superseded-Skill or old-cache cleanup. Not for building a marketplace manifest (use marketplace-dev) or repo audits (use marketplace-health-check).

daymade/claude-code-skills Agent Skills author: daymade MIT 10 files · 8 scripts body ≈ 1 978 tokens Open the sourcegithub.com↗ analyzed 6 d ago

Governs the Claude Code/Codex Skill surface: reconciles source/install/catalog-visibility drift without losing cold capability.

As a process C 58/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice

AnalyzerSoftware developmentCommercetype and topics are labelled automatically from the skill text
JSON
Technical rating
A
95/100
safety, quality, tests
Safety 60%
99
Quality 40%
89
Run on models
none yet
Process rating
C
58/100
Has gaps
Inputs and preconditions w 11
0
Progress reporting w 2
0
Running it twice w 4
30
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 · 1

    ✓ No critical or high findings

    Medium and low: 1
    • low Dangerous commands cmd-eval-dynamic scripts/audit_codex_skill_surface.py:510
      Dynamic code execution from decoded/untrusted input (documentation of a security skill)
      exec(compile(resolver_path.read_text(encoding="utf-8"), str(resolver_path), "exec"), owner.__dict__)
      security skill

    Files scanned: 6. 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 46): check that old rules are not kept next to new ones — the full check reads the text for contradictions

    Process rating: all ten parameters 58/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 2 mutating operations with no state check
    • 40Result and completion. Does not say what the result is
    • 50When it triggers. No condition that starts the skill
    • 55Failures and branches. 1 branches
    • 60Tools and files. Uses tools (bash) that frontmatter does not declare
    • 100Steps. 33 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1978 tokens

    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
    • +3Output format is not stated: the model decides each time
    • -31 of 4 scripts are never mentioned in SKILL.md
    • +1No license
    • +2Single-language instructions
    • +4Description says when NOT to use the skill
    • +3Description length 416: enough signal without eating the budget
    • +4Structure: 10 headings
    • +3Step-by-step instructions: 33 items
    • +4Has examples (3 code blocks)
    • +4Reference files are cited in the instructions (1 of 1)

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