Per-Node Skills
DAG workflow nodes support a skills field that preloads named skills into the
node’s agent context. Each node gets specialized procedural knowledge — code review
patterns, Remotion best practices, testing conventions — without polluting other nodes.
Claude only — Codex nodes will warn and ignore the skills field.
Quick Start
Section titled “Quick Start”- Install a skill (e.g., the official Remotion skill):
npx skills add remotion-dev/skillsThis places SKILL.md files in .claude/skills/remotion-best-practices/.
- Reference it in your workflow:
name: generate-videodescription: Generate a Remotion videonodes: - id: generate prompt: "Create an animated countdown video" skills: - remotion-best-practicesThat’s it. The skill’s content is injected into the agent’s context when the node runs. The agent can reference the skill’s knowledge (animation patterns, API usage, gotchas) without the user having to paste instructions into the prompt.
How It Works
Section titled “How It Works”When a node has skills: [name, ...], the executor wraps it in an
AgentDefinition — the
Claude Agent SDK mechanism for scoping skills to subagents.
YAML: skills: [remotion-best-practices] ↓Executor builds AgentDefinition: { description: "DAG node 'generate'", prompt: "You have preloaded skills: remotion-best-practices...", skills: ["remotion-best-practices"], tools: [...nodeTools, "Skill"] } ↓SDK loads skill content into agent context at startup ↓Agent executes with full skill knowledge availableThe Skill tool is automatically added to allowedTools so the agent can invoke
skills. You don’t need to add it manually.
Installing Skills
Section titled “Installing Skills”Skills must be installed on the filesystem before they can be referenced.
From skills.sh (marketplace)
Section titled “From skills.sh (marketplace)”# Install to current projectnpx skills add remotion-dev/skills
# Install globally (all projects)npx skills add remotion-dev/skills -g
# Install a specific skill from a multi-skill reponpx skills add anthropics/skills --skill skill-creator
# Search for skillsnpx skills find "database"From GitHub
Section titled “From GitHub”# Public reponpx skills add owner/repo
# Specific path in reponpx skills add owner/repo/path/to/skill
# Private repo (uses SSH keys or GITHUB_TOKEN)npx skills add git@github.com:org/private-skills.gitManual
Section titled “Manual”Create a directory in .claude/skills/ with a SKILL.md file:
.claude/skills/my-skill/└── SKILL.mdSKILL.md format:
---name: my-skilldescription: What this skill does and when to use it---
# Instructions
Step-by-step content here. The agent loads this when the skill activates.Skill Discovery
Section titled “Skill Discovery”Skills are discovered from these locations (via settingSources: ['project']
set in ClaudeClient):
| Location | Scope |
|---|---|
.claude/skills/ (in cwd) | Project-level |
~/.claude/skills/ | User-level (all projects) |
Skills installed via npx skills add land in .claude/skills/ by default.
Use -g for global installation to ~/.claude/skills/.
Scoping: Installed vs Active
Section titled “Scoping: Installed vs Active”Installed = the skill exists on disk. It’s discoverable by the Claude subprocess.
Active = listed in skills: on a specific DAG node. Only THAT node gets the
skill content injected into its context.
nodes: - id: classify prompt: "Classify this task" # No skills — fast, cheap, no extra context
- id: implement prompt: "Write the code" skills: [code-conventions, testing-patterns] # Gets both skills injected — deeper domain knowledge
- id: review prompt: "Review the code" skills: [code-review] # Gets a different skill — review-focused expertiseAll three skills are installed on disk. But each node only loads what it needs. This follows the Stripe Minions principle: “agents perform best when given a smaller box with a tastefully curated set of tools.”
Popular Skills
Section titled “Popular Skills”| Skill | Install | What It Teaches |
|---|---|---|
remotion-best-practices | npx skills add remotion-dev/skills | Remotion animation patterns, API usage, gotchas (35 rules) |
skill-creator | npx skills add anthropics/skills | How to create new SKILL.md files |
| Community skills | Browse skills.sh | Search 500K+ skills for any domain |
Multiple Skills Per Node
Section titled “Multiple Skills Per Node”A node can have multiple skills. All are injected:
- id: implement prompt: "Build the feature" skills: - code-conventions - testing-patterns - api-designKeep it concise — each skill’s full content is injected into context at startup (not progressive disclosure). The agentskills.io spec recommends keeping SKILL.md under 500 lines / 5000 tokens.
Combining Skills with MCP
Section titled “Combining Skills with MCP”Skills and MCP compose naturally on the same node:
- id: create-pr prompt: "Create a PR with the changes" skills: - pr-conventions # Teaches HOW to write good PRs mcp: .archon/mcp/github.json # Provides the GitHub toolsSkills teach the process. MCP provides the capability. Together they produce better results than either alone.
Codex Compatibility
Section titled “Codex Compatibility”Codex nodes with skills log a warning and continue without the skills:
Warning: Node 'review' has skills set but uses Codex — per-node skillsare not supported for Codex.To use skills, ensure the node uses Claude (the default provider, or set
provider: claude explicitly).
Limitations
Section titled “Limitations”- Pre-installation required — skills must exist on disk before the workflow runs. There is no on-demand fetching (yet).
- Claude only — the SDK’s
AgentDefinition.skillsfield is Claude-specific. - Full injection — skill content is fully injected at startup, not progressively disclosed. Keep skills concise.
- No validation — if a named skill doesn’t exist, the SDK may fail silently.
Verify skills are installed with
npx skills list.
Troubleshooting
Section titled “Troubleshooting”| Problem | Cause | Fix |
|---|---|---|
| Skill not found | Not installed | Run npx skills add <source> |
| Skill ignored | Node uses Codex provider | Set provider: claude on the node |
| Too many skills | Context budget exceeded | Reduce to 2-3 most relevant skills per node |
| Skill has no effect | Description too vague | Rewrite SKILL.md with specific, actionable instructions |
Related
Section titled “Related”- Per-Node MCP Servers —
mcp:field for external tool access - Hooks —
hooks:field for tool permission control - skills.sh — marketplace for discovering skills
- agentskills.io — the open SKILL.md standard