◈
Capabilities
capability.yaml
Bundle tools + skills + policies + tests into versioned compositions.
Capabilities are versioned compositions intended to create an operational specialist (e.g., "AcmeCRM Specialist"). They reference tools, skills, and policies by path, declare required eval suites, and specify the artefact types they emit. A capability represents a functional domain, not a single action.
Schema
capability.yamlyaml
# capability.yaml — Frontend Development
name: frontend-development
version: "1.2"
description: "Full frontend development capability with React, testing, and deployment"
skills:
- react-optimization
- component-architecture
- accessibility-audit
- performance-profiling
tools:
- run-tests
- deploy-preview
- lighthouse-audit
- bundle-analyzer
defaults:
framework: react
test_runner: vitest
style_system: tailwind
build_tool: vite
constraints:
- "All components must pass accessibility checks"
- "Bundle size must not increase by more than 5%"
- "Test coverage must stay above 80%"
requires:
- node >= 18
- pnpm >= 8Usage
# Capabilities compose into profiles
profiles:
frontend-engineer:
capabilities:
- frontend-development
- code-review
- documentationBest Practices
- ✓Name capabilities after functional domains, not technologies
- ✓Include sensible defaults that can be overridden by profiles
- ✓Define constraints that apply to all skills within the capability
- ✓Declare runtime requirements explicitly
- ✓Keep capabilities focused — a capability should represent one role area
Anti-Patterns
- ✗Enormous capabilities that try to cover everything
- ✗Capabilities with conflicting skill requirements
- ✗Missing version numbers — breaks reproducibility
- ✗No constraints — agents operate without guardrails