Load context on-demand instead of cramming everything into the system prompt.
What are Skills?
Skills are reusable packages of instructions and context that agents retrieve when needed. Instead of a massive system prompt, your agent sees:
- A list of available skills (name + short description)
- A
skill_gettool to load the full content
This progressive disclosure pattern is used by industry-leading agents like Claude Code and ChatGPT.
Why Use Skills?
| Without Skills | With Skills |
|---|---|
| Long system prompts slow down every response | Context loaded only when relevant |
| All knowledge visible all the time | Agent chooses what to retrieve |
| Hard to maintain and update | Modular, reusable packages |
| Single monolithic prompt | Composable building blocks |
Adding Skills
- Open your agent's settings
- Go to the Prompt tab
- Scroll to the Skills section
- Click + URL or + Text
URL-based Skills
Fetch skill content from a URL:
- Name:
api-docs - Description: API documentation for our service
- URL:
https://example.com/skills/api-docs.md
The content is fetched once per session and cached.
Inline Skills
Write skill content directly:
- Name:
code-review - Description: Guidelines for reviewing pull requests
- Content:
markdown
1# Code Review Guidelines23When reviewing code, check for:41. Security vulnerabilities52. Performance issues63. Code style consistency
How Agents Use Skills
The agent sees available skills in its skill_get tool description:
1skill_get: Retrieves the full content of a skill.23Available skills:4- code-review: Guidelines for reviewing pull requests5- api-docs: API documentation for our service67Parameters:8- skill: The name of the skill to retrieveWhen the agent needs guidance, it calls skill_get:
1User: "Review this pull request"23Agent: [calls skill_get(skill="code-review")]4> # Code Review Guidelines5> When reviewing code, check for:6> 1. Security vulnerabilities7> ...89Agent: "Based on our code review guidelines, here's my review..."Best Practices
Write Good Descriptions
The description is what the agent sees in the tool listing. Make it clear and specific:
Too vague:
1docsBetter:
1API documentation for the payment service, including endpoints, authentication, and error codesKeep Skills Focused
Each skill should cover one topic or capability. Instead of one massive "everything" skill:
1skills:2 - code-review: Guidelines for reviewing code3 - security-checklist: Security audit checklist4 - api-reference: API endpoint documentationUse URLs for External Docs
Point to documentation that's maintained elsewhere:
1- name: react-docs2 description: React 19 documentation and best practices3 url: https://raw.githubusercontent.com/your-org/docs/main/react-guide.mdSkill Content Format
Skills support plain text or markdown. For URL-based skills, the system automatically strips YAML frontmatter:
1---2title: My Skill3version: 1.04---56# Actual Content Starts Here78This is what the agent sees.Use Cases
| Skill | Description |
|---|---|
| Code Review | Guidelines for reviewing pull requests |
| API Reference | Endpoint documentation and examples |
| Style Guide | Writing and coding style standards |
| Troubleshooting | Common issues and solutions |
| Onboarding | New user setup instructions |
| Domain Knowledge | Industry-specific terminology and concepts |
Next
Learn more about skills in the SDK:
- Internal Tools - Technical reference for
skill_get - Ad-hoc Agents - Using skills in SDK agents