Writing a skill
A skill of your own is a folder with a SKILL.md in it. What goes in that file is the method you would otherwise explain every time.
Creating custom skills
When the catalog does not cover a workflow specific to your team or project, you can create a custom skill. A custom skill defines the task objective, the step-by-step methodology, and any constraints or output formats.
For example, a team might create a "database migration review" skill that checks for backward compatibility, verifies rollback procedures, and flags missing indexes, specific to their schema conventions. Once saved, a custom skill behaves identically to a catalog skill: it appears in the slash command menu and can be matched automatically.
Because skills are stored with your project, everyone working in the same project shares the same workflows. This turns individual expertise into team capability: a senior engineer's code review checklist becomes a skill that every team member can invoke.
