SKILLEMALL.ai
GitHub ↗ RU Sign in

AC CreateSkill

Mandatory orchestrator for all LifeOS skill work: scaffold, edit, validate, canonicalize, test, and improve any skill; handrolling skill files is forbidden. USE WHEN create skill, new skill, make a skill, build a skill, set up a skill, private skill, make a X skill, add an intent, add a tool, edit/change/update/rename a skill, skill frontmatter, validate skill, check skill, canonicalize, scaffold skill, test skill, improve skill, optimize description, skill not triggering, overtriggering. NOT FOR TypeScript CLI generation (CreateCLI).

danielmiessler/Personal_AI_Infrastructure Agent Skills author: danielmiessler MIT 16 files · 3 scripts body ≈ 1 697 tokens Open the sourcegithub.com↗ analyzed 27 h ago

Mandatory orchestrator for all LifeOS skill work: scaffold, edit, validate, canonicalize, test, and improve any skill; handrolling skill files is forbidden.

As a process C 60/100 · Has gaps — weak spots: inputs and preconditions, running it twice, progress reporting

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
95/100
safety, quality, tests
Safety 60%
99
Quality 40%
89
Run on models
none yet
Process rating
C
60/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 Risky intent intent-offensive-security References/Conventions.md:30
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      The test and the table that decide it live in one place, `~/.claude/LIFEOS/DOCUMENTATION/Skills/SkillSystem.md` § Public vs Private Skills; this section does not restate the table. Ask: **"Could a str

    Files scanned: 16. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
    • note frontmatter-key unknown frontmatter key "evals"
    • note edit-residue the text marks something as outdated (lines 78, 80): check that old rules are not kept next to new ones — the full check reads the text for contradictions

    Process rating: all ten parameters 60/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 16 mutating operations with no state check
    • 50When it triggers. No condition that starts the skill
    • 50Failures and branches. 0 branches, has a failure section
    • 60Tools and files. Uses tools (bash) that frontmatter does not declare
    • 60Result and completion. Output format stated, no completion criterion
    • 100Steps. 11 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1697 tokens
    • low The response is described with custom markup (3 tags): a typed call is more reliable

    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
    • +1No license
    • +2Single-language instructions
    • +4Description says when NOT to use the skill
    • +3Description length 540: enough signal without eating the budget
    • +4Structure: 9 headings
    • +3Step-by-step instructions: 11 items
    • +3Output format is stated explicitly
    • +4Has examples (3 code blocks)
    • +4Reference files are cited in the instructions (2 of 2)

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