Agent Skills for Deep Code
Create reusable instructions for Deep Code to use in your current project or across projects.
A skill stores a repeatable workflow in a SKILL.md file. Start with the review example below, save it in your project, and select it from the CLI. Set up your DeepSeek connection before trying the skill.
Still need to set up the CLI?Install Deep Code and connect your API credentials.Setup guideCreate your first skillOn this page
Where should your skill live?
Use a project folder for instructions that belong with the repository, or a user folder for personal workflows. These four locations are checked in the order shown; the first matching skill name takes precedence.
| Scope | Location | Use |
|---|---|---|
| 1 · Project | ./.deepcode/skills/ | Deep Code project skills |
| 2 · Project | ./.agents/skills/ | Shared with other agent clients |
| 3 · User | ~/.deepcode/skills/ | Personal Deep Code skills |
| 4 · User | ~/.agents/skills/ | Personal skills shared across clients |
A complete example
Create a folder named review inside .deepcode/skills, then save this example as .deepcode/skills/review/SKILL.md. Create the folders yourself if they do not exist.
The name identifies the skill. The description tells the agent when to use it; the Markdown body gives the actual instructions.
---
name: review
description: >-
Review this project's changes for bugs and regressions.
Use when asked to review a diff or a pull request.
---
# Review project changes
1. Read AGENTS.md and inspect the changed files.
2. Check how each change affects its callers.
3. Report concrete bugs with file and line references.
4. Explain any checks you could not perform.
5. Do not modify files during the review.Invoke it in the terminal
Open your project directory in a terminal and start Deep Code. Inside the CLI, enter /skills to check that review is available. Type / to open the menu, or /review to select your skill.
Try a concrete request, such as: “Review my current changes for regressions.” Compare the findings with the code before acting on them.
cd /path/to/my-project
deepcodeIf the skill is missing
Check the project directory, the exact filename SKILL.md, and the enclosing skill folder. Also check whether enabledSkills disables review or a higher-priority skill uses the same name.
For unreliable automatic selection, make the description more specific. A skill with metadata.allow-implicit-invocation: false must be selected manually.
Keep the workflow focused
Our review example deliberately asks for findings without editing files. Adapt its checks to your project and try it on a small, familiar change first.
Keep general repository conventions in AGENTS.md. Give each skill one recurring task; reference longer checklists or examples from separate files when needed.
Further resources
Continue with the CLI setup guide for installation and API configuration, or read the project documentation for more Skill options.
Frequently asked questions
Does each skill need its own folder?
Yes. For this example, the file is .deepcode/skills/review/SKILL.md; saving it directly inside .deepcode/skills does not follow the documented structure.
Which skill wins if names are duplicated?
Deep Code uses the first matching name in the documented search order: project .deepcode, project .agents, user .deepcode, then user .agents. Bundled skills follow these locations.
How do I list available skills?
Enter /skills inside Deep Code. Use / to open the selection menu.
Can I use a skill without automatic matching?
Yes. Add metadata.allow-implicit-invocation: false in YAML frontmatter and select the skill manually.
Is a skill an MCP server?
A skill supplies reusable instructions and supporting files. MCP connects the agent to tools and external services.