← ClaudeAtlas

meta-skill-authorlisted

Use when creating a skill or reviewing its format. Defines the catalogue frontmatter and its real length limits, the two-layer principle/binding anatomy, the five-question portability gate, section order, skill shapes, naming, rule ownership, and which plugin a skill belongs to.
wntic/pyhouse · ★ 3 · Code & Development · score 76
Install: claude install-skill wntic/pyhouse
# Meta — Skill Author A skill is **narrow**: it covers one artifact, or one set of artifacts that always arrive together. Skills are read as reference knowledge; the job is to show how the right file gets written. Uniformity matters more than expressiveness — a reader who has applied one skill should be able to apply any other. This catalogue is distributed on the Claude Code marketplace, so a skill is written for someone whose stack is not yours: state the obligation mechanism-free, then bind it to exactly one concrete stack. This skill produces one new `SKILL.md`; editing other skills is an audit task. **Read the sibling `CONVENTIONS.md` in this skill's own directory before writing anything.** It carries the catalogue's shared placeholder vocabulary (`Foo`, `Bar`, `myapp`, `myschema` and the names derived from them), the banned vocabulary, the index of what each existing skill covers, the six-plugin packaging layout, the four skill shapes, and what is deliberately out of scope. Only this file is loaded automatically; the sibling is not, so open it rather than working from this summary of it. ## When to use vs. neighbours - Adding a brand-new skill → this skill. - Editing an existing skill to fix a rule or a template → not this skill; edit the file directly. - Sweeping cross-references after a rename → not this skill; that is an audit task. - Deciding which plugin a skill ships in → the packaging table in the sibling `CONVENTIONS.md`. - Documenting a process rather tha