Custom Skills
You can create your own skills to enforce repeated tasks, package domain knowledge, and keep agents aligned with the same rules every time they run.
Repeated tasks
Use skills for workflows you repeat often, such as docs sync checks, route scaffolding, review checklists, or AI prompt validation.
Shared rules
Put reusable constraints in instructions, and use skills when the work is multi-step, task-shaped, or needs bundled assets and examples.
Better discovery
A good description makes the skill discoverable by the agent when the task matches the right trigger words and repeated workflow.
What To Create
| Primitive | Best use | Common location |
|---|---|---|
| Instructions | Always-on or file-scoped rules | .github/copilot-instructions.md, AGENTS.md, .github/instructions/*.instructions.md |
| Prompt | Single focused task with inputs | .github/prompts/*.prompt.md |
| Agent | Specialized subagent or restricted workflow | .github/agents/*.agent.md |
| Skill | Multi-step repeated workflow with packaged assets | .github/skills/<name>/SKILL.md |
Good Skill Candidates
Docs sync review
Compare docs route pages against packaged docs and produce a drift report with missing routes, rename candidates, and stale content.
Route scaffolding
Scaffold a new route with the right index.html, optional index.py, single-root template shape, and PulsePoint-ready script placement.
Feature gate check
Read caspian.config.json before touching Prisma, MCP, TypeScript, Tailwind, or other optional features.
Runtime ownership lookup
Jump from a task to the owning app file, then to the installed runtime only when the app layer does not control the behavior.
Authoring Notes
- Use a clear description with task keywords. The description is the discovery surface for the agent.
- Use instructions for broad rules and skills for repeated task workflows.
- Keep skill scope narrow enough that the agent knows when to invoke it.
- When a skill documents file locations, keep them aligned with the current repo and packaged docs.
- For team-shared customizations, prefer workspace files under
.github/.