| title | Agent Skills in the SDK |
|---|---|
| source | https://code.claude.com/docs/en/agent-sdk/skills |
| category | code |
| generated | true |
Fetch the complete documentation index at: https://code.claude.com/docs/llms.txt Use this file to discover all available pages before exploring further.
Extend Claude with specialized capabilities using Agent Skills in the Claude Agent SDK
Agent Skills extend Claude with specialized capabilities that Claude autonomously invokes when relevant. Skills are packaged as SKILL.md files containing instructions, descriptions, and optional supporting resources.
For comprehensive information about Skills, including benefits, architecture, and authoring guidelines, see the Agent Skills overview.
When using the Claude Agent SDK, Skills are:
- Defined as filesystem artifacts: Created as
SKILL.mdfiles in specific directories (.claude/skills/) - Loaded from filesystem: Skills are loaded from filesystem locations governed by
settingSources(TypeScript) orsetting_sources(Python) - Automatically discovered: Once filesystem settings are loaded, Skill metadata is discovered at startup from user and project directories; full content loaded when triggered
- Model-invoked: Claude autonomously chooses when to use them based on context
- Filtered via the
skillsoption: Discovered skills are enabled by default. Pass a list of skill names,"all", or[]to control which are available in the session
Unlike subagents (which can be defined programmatically), Skills must be created as filesystem artifacts. The SDK does not provide a programmatic API for registering Skills.
Skills are discovered through the filesystem setting sources. With default `query()` options, the SDK loads user and project sources, so skills in `~/.claude/skills/`, `/.claude/skills/`, and `.claude/skills/` in any parent directory of `` up to the repository root are available. If you set `settingSources` explicitly, include `'user'` or `'project'` to keep skill discovery, or use the [`plugins` option](./code-agent-sdk/plugins.md) to load skills from a specific path.Set the skills option on query() to control which Skills are available to the session. When omitted, discovered Skills are enabled and the Skill tool is available, matching CLI behavior. Pass "all" to enable every discovered Skill, a list of Skill names to enable only those, or [] to disable all. When you set skills, the SDK enables the Skill tool automatically, so you do not need to list it in allowedTools.
Once configured, Claude automatically discovers Skills from the filesystem and invokes them when relevant to the user's request.
```python Python theme={null} import asyncio from claude_agent_sdk import query, ClaudeAgentOptionsasync def main(): options = ClaudeAgentOptions( cwd="/path/to/project", # Project with .claude/skills/ setting_sources=["user", "project"], # Load Skills from filesystem skills="all", # Enable every discovered Skill allowed_tools=["Read", "Write", "Bash"], )
async for message in query(
prompt="Help me process this PDF document", options=options
):
print(message)
asyncio.run(main())
```typescript TypeScript theme={null}
import { query } from "@anthropic-ai/claude-agent-sdk";
for await (const message of query({
prompt: "Help me process this PDF document",
options: {
cwd: "/path/to/project", // Project with .claude/skills/
settingSources: ["user", "project"], // Load Skills from filesystem
skills: "all", // Enable every discovered Skill
allowedTools: ["Read", "Write", "Bash"]
}
})) {
console.log(message);
}
To enable only specific Skills, pass their names. Names match the name field in SKILL.md or the Skill's directory name. Use plugin:skill for plugin-provided Skills.
const options = { skills: ["pdf", "docx"] };The skills option is a context filter, not a sandbox. Unlisted Skills are hidden from the model and rejected by the Skill tool, but their files remain on disk and are reachable through Read and Bash.
Skills are loaded from filesystem directories based on your settingSources/setting_sources configuration:
- Project Skills (
.claude/skills/): Shared with your team via git - loaded whensetting_sourcesincludes"project" - User Skills (
~/.claude/skills/): Personal Skills across all projects - loaded whensetting_sourcesincludes"user" - Plugin Skills: Bundled with installed Claude Code plugins
Skills are defined as directories containing a SKILL.md file with YAML frontmatter and Markdown content. The description field determines when Claude invokes your Skill.
Example directory structure:
.claude/skills/processing-pdfs/
└── SKILL.mdFor complete guidance on creating Skills, including SKILL.md structure, multi-file Skills, and examples, see:
- Agent Skills in Claude Code: Complete guide with examples
- Agent Skills Best Practices: Authoring guidelines and naming conventions
When using the SDK, control tool access through the main allowedTools option in your query configuration.
To control tool access for Skills in SDK applications, use allowedTools to pre-approve specific tools. Without a canUseTool callback, anything not in the list is denied:
async for message in query(prompt="Analyze the codebase structure", options=options): print(message)
```typescript TypeScript theme={null}
for await (const message of query({
prompt: "Analyze the codebase structure",
options: {
settingSources: ["user", "project"], // Load Skills from filesystem
skills: "all",
allowedTools: ["Read", "Grep", "Glob"],
permissionMode: "dontAsk" // Deny anything not in allowedTools
}
})) {
console.log(message);
}
To see which Skills are available in your SDK application, simply ask Claude:
```python Python theme={null} options = ClaudeAgentOptions( setting_sources=["user", "project"], # Load Skills from filesystem skills="all", )async for message in query(prompt="What Skills are available?", options=options): print(message)
```typescript TypeScript theme={null}
for await (const message of query({
prompt: "What Skills are available?",
options: {
settingSources: ["user", "project"], // Load Skills from filesystem
skills: "all"
}
})) {
console.log(message);
}
Claude will list the available Skills based on your current working directory and installed plugins.
Test Skills by asking questions that match their descriptions:
```python Python theme={null} options = ClaudeAgentOptions( cwd="/path/to/project", setting_sources=["user", "project"], # Load Skills from filesystem skills="all", allowed_tools=["Read", "Bash"], )async for message in query(prompt="Extract text from invoice.pdf", options=options): print(message)
```typescript TypeScript theme={null}
for await (const message of query({
prompt: "Extract text from invoice.pdf",
options: {
cwd: "/path/to/project",
settingSources: ["user", "project"], // Load Skills from filesystem
skills: "all",
allowedTools: ["Read", "Bash"]
}
})) {
console.log(message);
}
Claude automatically invokes the relevant Skill if the description matches your request.
Check settingSources configuration: Skills are discovered through the user and project setting sources. If you set settingSources/setting_sources explicitly and omit those sources, skills are not loaded:
options = ClaudeAgentOptions( setting_sources=["user", "project"], skills="all", )
```typescript TypeScript theme={null}
// Skills not loaded: settingSources excludes user and project
const options = {
settingSources: [],
skills: "all"
};
// Skills loaded: user and project sources included
const options = {
settingSources: ["user", "project"],
skills: "all"
};
For more details on settingSources/setting_sources, see the TypeScript SDK reference or Python SDK reference.
Check working directory: The SDK loads Skills from .claude/skills/ in the cwd option and in every parent directory up to the repository root. Ensure cwd points at or below the directory containing .claude/skills/, within the same repository:
// Ensure your cwd points to the directory containing .claude/skills/
const options = {
cwd: "/path/to/project", // .claude/skills/ here or in a parent directory
settingSources: ["user", "project"], // Loads skills from these sources
skills: "all"
};See the "Using Skills with the SDK" section above for the complete pattern.
Verify filesystem location:
# Check project Skills
ls .claude/skills/*/SKILL.md
# Check personal Skills
ls ~/.claude/skills/*/SKILL.mdCheck the skills option: If you passed a skills list, confirm the skill's name is included. Passing [] disables all skills.
Check the description: Ensure it's specific and includes relevant keywords. See Agent Skills Best Practices for guidance on writing effective descriptions.
For general Skills troubleshooting (YAML syntax, debugging, etc.), see the Claude Code Skills troubleshooting section.
- Agent Skills in Claude Code: Complete Skills guide with creation, examples, and troubleshooting
- Agent Skills Overview: Conceptual overview, benefits, and architecture
- Agent Skills Best Practices: Authoring guidelines for effective Skills
- Agent Skills Cookbook: Example Skills and templates
- Subagents in the SDK: Similar filesystem-based agents with programmatic options
- Slash Commands in the SDK: User-invoked commands
- SDK Overview: General SDK concepts
- TypeScript SDK Reference: Complete API documentation
- Python SDK Reference: Complete API documentation