# Writing Skills > Use when authoring, editing, or verifying a SKILL.md, or promoting a demonstrated procedure into a skill; select evidence of task lift and preserve the catalog contract. - Skill: `ryan-brosas/writing-skills` (Agent Skill, multi-file: 14 files) - Install (CLI): `npx skillmds@latest add ryan-brosas/writing-skills` - Raw SKILL.md: https://api.skillmd.com/api/skills/ryan-brosas/writing-skills/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Productivity - Author: ryan-brosas (https://skillmd.com/u/ryan-brosas) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/ryan-brosas/writing-skills --- # Writing Skills A skill earns its load by improving work, not by making the model obey more rules. Use this for skill authoring, not ordinary project documentation. Start with `../../templates/skill.md`; omit sections that add no task-specific value. ## Author for lift Identify what the model repeatedly gets wrong or rediscovers, what unique context is missing, and what work the candidate should remove. Preserve decisions that belong to the model or project. Reusable code and exact recurring checks belong in implementation or gates rather than prose. For hot promotion, material changes to load-bearing skills, overlapping owners, large loaders, or observed slowdown, compare a representative task without the skill and with the smallest candidate. Judge outcome quality, errors, turns, tool calls, loaded context, and unintended artifacts or effects. Use the same starting conditions; do not force a baseline failure or reward citation of rules. Keep, compress, demote, merge, or retire based on the tradeoff. An unmeasured candidate is not demonstrated lift. Select the cheapest meaningful evidence by skill type. References need relevant, usable information and valid links; routers need reliable selection; deterministic helpers need execution tests. Guardrails need evidence that an expensive failure is prevented, including legitimate exceptions. Pressure tests serve that purpose, not universal obedience testing. See `references/lift-evaluation.md` when designing a comparison. Evaluation is selective authoring work, not mandatory CI or a runtime scoring engine. ## Metadata and discovery - `name`: kebab-case, identical to the directory name. - `description`: trigger-first (`Use when ...`), under 1024 characters; aim for 512 or fewer. Triggers must be distinguishable enough for reliable selection. For legitimate overlap, state precedence or use one small router. - `invocation`: `entry`, `internal`, `manual`, or `vendor`, chosen from actual callers. Only visible local entries are generically hot. Internal/manual skills require `disable-model-invocation: true`; vendor visibility follows its integration. Hot promotion needs recurring use and distinct demonstrated lift, not automatic publication of every useful skill. - `kind: foundation`: only for cold source evidence; follow `references/foundation-kind.md` when authoring one. - Parse strict YAML: known scalar fields are strings; visibility flags are real booleans. Quote values containing colon-space or hash syntax. ## Keep invocation small Aim for leaf bodies under about 600 words and routers under about 200. These are review targets, not proof of value. Keep the loader usable alone; put deep mechanics in focused references loaded only for the active question. Do not duplicate live tool schemas, another skill, or the global constitution. Use host-neutral guidance and probe optional capabilities. Add structured output only for a real parser. Prefer choices and evidence over prohibitions. Reserve hard constraints for safety, protocol integrity, or demonstrated expensive failures, not architectural taste. ## Verify and stop Choose checks for the destination, not the shell's current directory. For changes inside universal-template, resolve the target checkout root from the changed files and run there: `python3 scripts/skill-validator.py`, `python3 scripts/skill-catalog.py generate`, then `python3 scripts/skill-catalog.py generate --check`. Ensure `SKILLS_ROOT`, if set, points to that checkout's `skills/`, not another installed copy. For external skills, use that project's available checks and conventions. If it has no publication tooling, inspect metadata, links, discovery, and callers directly; report universal-template publication checks as not applicable. Do not run or regenerate the global catalog to validate an unrelated external skill. Confirm referenced files exist, intended host discovery works, and changed callers still work; universal-template additionally requires disjoint hot/cold sets. Check diff hygiene. Review prose using `../house-writing-style/SKILL.md`; models review meaning, scripts check exact contracts. Report evidence, unmeasured claims, and remaining limitations separately.