
CreateSkill
Mandatory orchestrator for all LifeOS skill work: scaffold, edit, validate...
Install
npx skills add danielmiessler/LifeOS --skill CreateSkill -g -a claude-code -y- Repository
- danielmiessler/LifeOS19.7k
- Category
- Testing
- Updated
- 8d ago
- License
- MIT
- Context cost
- Mediumabout 1,696 tokens
- Runs scripts
- Yes, review before use
What it does
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).
CreateSkill
Contents: Ideal State · Intent Routing · Data & Config · Gotchas · Examples
CreateSkill is the one door for skill work in LifeOS: it creates, edits, validates, canonicalizes, tests, improves and retires skills, and every skill it touches leaves written to the intent standard in ~/.claude/LIFEOS/DOCUMENTATION/Skills/SkillSystem.md § Intent anatomy. An intent is a small ISA. It opens with ## Ideal State (testable outcomes of the deliverable) and ## Anti-criteria (what must never happen), then carries only Inputs, Safety gates, Tool contract, Gotchas, Output format, Examples and References. Choreography of the model's reasoning is cut, never relocated; the four keep-classes (safety gate, verified gotcha with provenance, tool contract, output-format contract) are the only legitimate how (LIFEOS/RULES/Philosophy.md § Ideal-State Prompting, skills/Prompting/Standards.md). This skill (CreateSkill/SKILL.md and its intents) is written to the standard it teaches and is the exemplar to copy.
Shared facts the intents rely on:
- Intents and skills are born from the template through
Tools/Scaffold.ts, nevertouchor a hand-typed skeleton. - The checks are code first:
LIFEOS/TOOLS/IntentLint.ts(the standard),LIFEOS/TOOLS/IntentPreserve.ts(nothing load-bearing lost),LIFEOS/TOOLS/SkillHygieneGate.ts(publishable-clean),LIFEOS/TOOLS/SkillCoverage.ts(does this skill already exist). Judgment covers only what code cannot decide. - An intent's Ideal State and Anti-criteria are also its grading criteria: Assay checks a run against them (
Proof.ts run --intent) and builds a skill suite's rubric from them. Lanes and when suites run follow the one progressive contract,skills/Assay/References/Progressive.md.


