- Home
- Skills
- Outfitter Dev
- Agents
- Claude Agents
claude-agents_skill
- TypeScript
25
GitHub Stars
2
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill outfitter-dev/agents --skill claude-agents- EXAMPLES.md49.0 KB
- SKILL.md10.7 KB
Overview
This skill guides creation and configuration of agents and subagents, and helps author agent frontmatter and Task tool entries. It clarifies when to choose an agent vs a reusable capability and provides patterns for composing layered agent + capability setups. Use it to ensure agents are specialized, isolated, and clearly configured.
How this skill works
The skill inspects intents such as "create agent", "agent.md", "subagent", "Task tool", and frontmatter fields like subagent_type. It recommends structure, parameter usage, and handoff patterns so agents remain narrow and conversation-scoped while capabilities remain broadly available. It also shows how to combine agents with reusable capabilities for layered workflows.
When to use it
- When you need a narrow, specialized role that runs in its own conversation thread
- When authoring agent frontmatter or configuring subagents and their parameters
- When deciding between a separate agent and a reusable capability
- When creating a Task tool entry or setting subagent_type fields
- When you need clear handoff points between review, implement, and test roles
Best practices
- Keep agents narrowly scoped to avoid polluting the main conversation context
- Use subagent_type in Task definitions to select the correct specialized agent
- Model broad capabilities as reusable skills that Claude can call autonomously
- Design clear interfaces and handoffs between agents and capabilities
- Bundle scripts or templates with capabilities, not with narrow agents
Example use cases
- Create a security-reviewer agent for isolated vulnerability analysis and handoff
- Define a code-quality capability used across many agent types for consistent reviews
- Configure a subagent for automated testing triggered by a Task tool entry
- Write agent frontmatter specifying subagent_type and parameters for a QA workflow
- Combine a general code-review capability with a specialized performance-tuner agent
FAQ
Create an agent for narrow, role-specific tasks that require their own conversation and explicit invocation. Use a capability when the behavior should be available broadly across conversations.
How do I keep agents from duplicating capability logic?
Extract shared techniques and templates into reusable capabilities, then have agents call or reference those capabilities for consistent behavior and fewer duplicates.