Menu

Individual skill

skill-author

The section-by-section anatomy standard every paid-quality SKILL.md must meet. Use when drafting or restructuring the BODY of a skill, deciding what sections it needs, or checking a draft against the house standard - "what sections does a skill need", "structure this SKILL.md", "is this skill body complete". Do NOT use for the end-to-end creation process from a raw idea (use skill-creator), grading a finished skill (use skill-auditor), or writing only the description field (use skill-description-writer).

skills/skill-author/SKILL.md

Read pinned source

Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
24
Repository last updated
Oct 13, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Skill Author

The anatomy standard for a skill worth paying for. A free skill is a blog post in frontmatter; a paid skill is an operating procedure that produces a measurably better outcome than the model gives unprompted. Apply this standard while drafting; hand the finished draft to skill-auditor for grading.

## Inputs to collect before drafting

Ask for whichever of these the requester has not supplied, and do not draft until you have the first three:

1. The job - the single outcome the skill produces, in one sentence.
2. The trigger - three or more exact phrases a user would type when they need it.
3. The audience - practitioner level and context (a founder pricing a SaaS reads differently than a growth analyst).
4. Domain source material - frameworks, thresholds, templates the skill should encode. If none is given, use established practitioner methods and say which you used.

## The nine-part anatomy