Skills System
Overdeck’s skills system provides reusable workflows and best practices for AI agents. The dashboard’s Skills page lists every skill side by side per harness — hereOverdeck (108) and Claude (123) — with each skill’s on-disk path, internal name, and a sync indicator linking to its SKILL.md. It’s the quickest way to confirm a skill landed where the agent (or the conversation you’re driving) can invoke it.
What Are Skills
Skills are reusable, shareable workflows that encode best practices for common development tasks. They are:- Universal - Work across all AI coding tools (Claude Code, Codex, Cursor, Gemini CLI, Google Antigravity)
- Shareable - Distribute via
pan syncto sync to all connected AI tools - Contextual - Invoked with
/skill-namein AI tool prompts - Best-practice-driven - Encode proven workflows and checklists
/code-review-security and the agent follows the established workflow.
Built-In Skills
Overdeck ships with 70+ built-in skills organized by category:Development Workflows
AI Self-Monitoring
Overdeck Operations (pan-*)
Utilities
Using Skills
Skills are invoked via slash commands in any AI coding tool:Creating Custom Skills
Skills are markdown files stored in~/.overdeck/skills/. Create your own with:
/pan-skill-creator for guided creation.
Skill Distribution
Skills can be distributed via:- Project-specific - Store in
.overdeck/skills/in your repo - User-specific - Store in
~/.overdeck/skills/(synced to AI tools) - Team-shared - Commit to version control and share via git
- Public packages - Distribute via npm or GitHub
Syncing Skills
pan sync command:
- Copies skills from
~/.overdeck/skills/to each AI tool’s config directory - Updates existing skills if versions differ
- Preserves local customizations (doesn’t overwrite modified files)
Subagents
Overdeck includes specialized subagent templates for common development tasks. Subagents are invoked via the Task tool or convoy orchestration for parallel execution.Code Review Subagents
Usage Example:
Planning & Exploration Subagents
Usage Examples:
Best Practices
When creating skills:- Be specific - Include exact commands, not just concepts
- Include examples - Show concrete usage patterns
- Add checklists - Help agents verify completion
- Cross-reference - Link to related skills and guides
- Test thoroughly - Verify skills work end-to-end
- Invoke early - Start with a skill, don’t switch mid-task
- Follow fully - Don’t skip steps or customize on-the-fly
- Report issues - If a skill doesn’t work, improve it
- Combine wisely - Some skills complement each other, others conflict
Related Guides
- Creating Skills - Detailed skill creation guide
- Convoys - Parallel subagent execution
- Subagents - Custom subagent templates