Agent skills

A skill is a folder with a SKILL.md file that teaches a coding agent one job. Agents load a skill when your request matches its description, and most let you call one by name. In Claude Code, for example, you start a message with /postgres-expert.

The kit ships 49 skills. The same copies live in three folders so every agent finds them:

• .claude/skills/ for Claude Code
• .agents/skills/ for Codex, Copilot, Junie, Gemini CLI and other agents that follow the AGENTS.md convention
• .cursor/skills/ for Cursor

Every skill is listed in tooling/scripts/src/agent-skills.json with its source repository and licence. Most third-party entries also record the upstream commit they were copied from; the 14 entries marked sync: ui-skills are refreshed with pnpm ui-skills:sync instead.

Where they come from

• 9 are part of the kit and follow its patterns: postgres-expert, server-action-builder, service-builder, react-form-builder, playwright-e2e, rls-review, reviewer, bug-hunt and bug-hunt-lite.
• 40 are third-party: 38 under the MIT licence and 2 under Apache-2.0 (frontend-design, impeccable). Each folder carries its licence file.

By job

The six phone-app skills only help if you have the phone app (All-in plan).

When a skill disagrees with the kit

Third-party skills give general advice. Where one conflicts with how this kit works, the AGENTS.md files win, and the known conflicts are written down: apps/web/supabase/AGENTS.md for the row-level security helpers, apps/native/AGENTS.md for Expo upgrades, styling and network calls.

The marketing skills (copywriting, launch, aso, ai-seo, seo-audit, schema) read .agents/product-marketing.md first. It describes shipanysaas today: replace it with your own product before you use them.

Using them together

Name several skills in one request, for example: "Add a projects feature: the table with /postgres-expert, the actions with /server-action-builder, the form with /react-form-builder, then run /reviewer and /rls-review."

Adding a skill

1. Add an entry to tooling/scripts/src/agent-skills.json with the skill's name, source (the GitHub repository), path (its folder in that repository) and license.
2. Run pnpm skills:sync <name>. It copies the skill into all three folders as real files, adds the repository's licence if the folder has none, and records the commit in the manifest.
3. If you kept the kit's sales page, raise proof.skills in apps/web/config/kit-offer.config.ts.
4. Run pnpm skills:check.

pnpm skills:check also runs in CI. It fails if the three folders differ, a folder is a symlink, a SKILL.md has a bad name or no description, a third-party skill is not MIT or Apache-2.0 or lacks its licence file, or the sales page count does not match.