Agent Skills

Agent Skills are modular, reusable capability packages that extend AI agent behavior by bundling domain-specific instructions, workflows, and executable resources into filesystem-based directories. They are a core Harness-Engineering mechanism that transforms general-purpose agents into specialists without rebuilding agents from scratch.

What They Are

  • Filesystem-based modules: Each skill is a directory containing a SKILL.md file plus optional bundled resources
  • Discoverable by design: Skills register themselves in the agent’s system prompt via lightweight metadata
  • Composable: Multiple skills can coexist; agents combine them as needed per task
  • Cross-surface: Available in Claude Code, Claude.ai, the Claude API, and the Agent SDK

The Three-Level Loading Model

Skills use progressive disclosure — loading information in stages to preserve Context-Engineering efficiency:

LevelContentWhen LoadedToken Cost
1 — MetadataYAML frontmatter (name, description)Always, at startup~100 tokens per skill
2 — InstructionsSKILL.md body (workflows, best practices)When skill is triggered by a matching requestUnder 5k tokens
3 — ResourcesBundled files and scriptsOnly when explicitly referencedEffectively unlimited

At Level 3, executable scripts run via bash — their code never enters the context window, only their output does. This makes skills far more efficient than having the agent generate equivalent code on demand.

Skills vs. AGENTS.md Files

The key distinction is when context is loaded:

  • AGENTS-md-Files: Always loaded into every session; best for universal rules and project-wide conventions
  • Agent Skills: Loaded on demand, only when relevant; best for domain-specific workflows that don’t apply to every task

Use AGENTS.md for standing instructions. Use skills for specialized capabilities that should remain dormant until needed.

SKILL.md Format

Every skill requires a SKILL.md file with YAML frontmatter:

---
name: pdf-processing
description: Extract text and tables from PDF files. Use when working with PDFs.
---

The description field drives discovery — it is injected into the system prompt, and the agent uses it to decide whether to activate the skill. Descriptions must be specific and written in third person.

Security Considerations

Skills execute code and invoke tools, so a malicious skill can direct an agent to perform harmful operations. The guidance is clear: treat skills like software packages — only install from trusted sources and audit bundled files before use.

Relationship to the Broader Tooling Ecosystem

Skills sit between AGENTS-md-Files (always-on context) and AI-Plugins (third-party capability extensions). They complement Model-Context-Protocol by providing agent-native capability packaging that doesn’t require external servers.

Sources

Note

This content was drafted with assistance from AI tools for research, organization, and initial content generation. All final content has been reviewed, fact-checked, and edited by the author to ensure accuracy and alignment with the author’s intentions and perspective.