Skills
Extend Verdent's capabilities with reusable knowledge packs for specialized workflows and domain expertise
Verdent Skills are reusable knowledge packs that extend the Agent's expertise. Each Skill contains domain-specific prompts, scripts, references, and best practices. Simply invoke a Skill by name, and the Agent loads the corresponding context and follows the predefined workflow.
What Are Skills?
Core Concept
A Skill is a structured knowledge pack stored in a folder. Every Skill contains a SKILL.md file that defines its name, description, and detailed prompt. When you invoke a Skill in conversation, Verdent reads this file and injects its content into the Agent's context.
How Skills Differ from Subagents and MCP
| Dimension | Skills | Subagents | MCP |
|---|---|---|---|
| Trigger | Manual invocation via @skill or mention | Auto-spawned by the main Agent | Auto-invoked or explicitly called |
| Execution | Expands the main conversation context | Runs as an independent sub-task with isolated context | Calls external tools via JSON-RPC 2.0 |
| Purpose | Domain guidance (e.g., "how to write tests") | Independent operations (e.g., "run code review") | External data/tool access (e.g., database queries) |
| Lifecycle | One-time context injection | Completes sub-task then returns results | Persistent server process during session |
| Implementation | Markdown files + optional scripts | Built-in Agent logic | Executable server processes |
In short: Skills provide knowledge and workflow guidance, Subagents execute independent tasks, and MCP connects external tools and data sources.
How to Use Skills
Invoking a Skill
You can invoke a Skill in two ways:
1. Mention the Skill name in conversation
Use the skill-creator skill to help me create a new Skill2. Use the @ mention syntax
@skill-creator help me create a Skill for API documentation generationWhen a Skill is triggered:
- The Agent calls the
skilltool to read the Skill'sSKILL.mdfile - The file content is injected into the current conversation context
- The Agent continues working according to the Skill's guidance
Browsing Available Skills
Access the Skills panel through Settings:
- Open the Settings menu
- Select the Skills tab
- Browse installed Skills and available Skills in the Skill Store
You can also type @ in the input box to trigger autocomplete and quickly select an available Skill.
Built-in Skills
Verdent ships with a set of built-in Skills covering common workflows:
| Skill | Description |
|---|---|
| docx | Read, create, or edit Word documents (.docx) with format-faithful visual checks |
| find-skills | Discover and install Skills — use when asking "how do I do X?" or looking for new capabilities |
| frontend-design | Create distinctive, production-grade frontend interfaces with high design quality |
| Read, create, or review PDF files with visual rendering and content extraction | |
| pptx | Read, create, or edit PowerPoint presentations (.pptx) |
| skill-creator | A guided workflow for creating and iterating on custom Skills |
| xlsx | Read, analyze, visualize, and smart-edit Excel spreadsheets |
More Skills are available in the Skill Store. Open Settings → Skills → Store to browse and install additional Skills.
Creating Custom Skills
You can create custom Skills to encapsulate your team's domain expertise or project-specific workflows.
Skill Directory Structure
A standard Skill folder looks like this:
my-custom-skill/
├── SKILL.md # Required: Skill definition file
├── agents/
│ └── verdent.yaml # Optional: UI configuration (icons, display name)
├── scripts/ # Optional: helper scripts
└── references/ # Optional: reference docs or examplesSKILL.md Format
SKILL.md is the core Skill file, containing YAML frontmatter and a Markdown body:
---
name: my-custom-skill
description: A concise description shown in the Skill list
metadata:
version: "1.0.0"
author: "Your Name"
license: "MIT"
---
# Detailed Instructions
This is the detailed prompt content the Agent reads.
## Workflow
1. Step one
2. Step two
3. ...
## Best Practices
- Practice suggestion 1
- Practice suggestion 2Frontmatter field requirements:
name(required): Must match the folder name. Only lowercase letters, numbers, and hyphens (a-z0-9-) allowed. Length: 1–64 characters. No consecutive hyphens or leading/trailing hyphens.description(required): A short description, max 1024 characters.metadata(optional): Version, author, license, and other meta information.
Installing Custom Skills
Method 1: Import via Settings
- Open Settings → Skills
- Click Import Skill
- Select the Skill folder (or a
.zip/.skillarchive) - Verdent validates
SKILL.mdand installs it to~/.verdent/skills/
Method 2: Manual copy
cp -r my-custom-skill ~/.verdent/skills/The Skill becomes available after restarting Verdent or refreshing the Skills list.
Method 3: Project-level Skill
Place the Skill inside your project directory:
cp -r my-custom-skill /path/to/your/project/.verdent/skills/Project-level Skills are only visible within that project and take priority over global Skills with the same name.
Skill Scopes
Verdent supports three levels of Skill scoping:
| Level | Location | Visibility |
|---|---|---|
| Global | ~/.verdent/skills/ | All projects and workspaces |
| Project | <project>/.verdent/skills/ | Current project's workspaces only |
Priority rules:
When Skills with the same name exist at multiple scopes:
- Project overrides Global
Skill Store
Verdent provides a Skill Store for browsing and installing community and official Skills.
Browsing the Skill Store
- Open Settings → Skills
- Switch to the Store tab
- Browse available Skills or use the search box
Installing from the Store
- Find the desired Skill in the Store
- Click Install
- The Skill is automatically downloaded and installed to
~/.verdent/skills/
Security verification:
Skills installed from the Store undergo SHA256 checksum verification to ensure file integrity and security.
Practical Examples
Example 1: Creating a New Skill with skill-creator
@skill-creator help me create a Skill for guiding the team on writing Go unit testsThe Agent will:
- Read the
skill-creatorSkill content - Guide you through filling in the Skill name, description, and core prompt
- Generate a standard
SKILL.md - Suggest installation path and verification steps
Example 2: Analyzing Data with spreadsheet
@spreadsheet read sales-2025.xlsx from the project root, analyze Q1 sales trends, and generate a chartThe Agent will:
- Load the
spreadsheetSkill - Use
pandasandopenpyxlto read the Excel file - Analyze the data and generate visualizations
- Save results or display them in the conversation
Example 3: Fixing CI with gh-fix-ci
@gh-fix-ci my PR #123 GitHub Actions tests are failing, help me debugThe Agent will:
- Use
ghCLI to retrieve CI logs for PR #123 - Analyze the failure (e.g., test case errors, dependency issues)
- Propose a fix
- With your approval, modify the code and push the fix
FAQs
Do Skills consume credits?
When a Skill is invoked, the Agent reads the SKILL.md file, which counts toward token usage and therefore consumes credits. However, the Skill itself does not make additional API calls.
Can I share custom Skills across projects?
Yes. Install the Skill to ~/.verdent/skills/ (global scope) and it will be available in all projects.
How do I delete a Skill I no longer need?
In Settings → Skills, right-click the Skill and select Delete. Built-in Skills marked as undeletable cannot be deleted and will be reinstalled on next startup.
Can I import Skills from Cursor, Claude Desktop, or Codex?
Yes. Verdent automatically detects Skills in ~/.cursor/skills, ~/.claude/skills, and ~/.codex/skills, and prompts you to import them. Click Import from External Sources in Settings → Skills.
What's the difference between a Skill and a Project Rule?
- Project Rule: Always-active instructions automatically injected into every conversation
- Skill: On-demand knowledge packs injected only when invoked
Use Rules for universal coding standards; use Skills for specific domain workflows.
How do I update an installed Skill?
Skills installed from the Skill Store are automatically checked for updates in the background. Manually installed Skills need to be re-imported (overwriting the old version) to update.
Advanced Usage
Embedding Scripts in Skills
Add a scripts/ directory to your Skill and reference the scripts in SKILL.md:
## Data Processing Script
Run the following command to process data:
\`\`\`bash
python scripts/process_data.py --input data.csv --output results.json
\`\`\`The Agent reads this instruction and executes the script as needed.
Referencing Documentation
Store API docs, specs, or sample code in a references/ directory and link them in SKILL.md:
## Reference Documentation
See [references/api-spec.md](references/api-spec.md) for the detailed API specification.The Agent can read these reference files based on the Skill's instructions.
Best Practices
Keep Skills focused. Each Skill should target a single domain or workflow. Avoid creating "do-everything" Skills—split them into smaller, specialized ones instead.
Use clear naming. Skill names should be concise and descriptive, e.g., api-doc-generator rather than my-skill-1.
Provide examples and references. Include concrete examples and reference links in SKILL.md to help the Agent better understand the expected output.
Maintain version numbers. Use the metadata.version field to track updates and compatibility.
Test before sharing. Validate your Skill in a test project before rolling it out to the team or publishing to the Skill Store.