Build Atomic Agents
Builds a typed AtomicAgent with its schemas, prompt, provider client and hooks.
Install
npx skills add Eigenwise/atomic-agents --skill create-atomic-agent -g -a claude-code -y- Repository
- Eigenwise/atomic-agents6.3k
- Category
- AI and agents
- Updated
- 6d ago
- License
- MIT
- Context cost
- Mediumabout 1,804 tokens
- Runs scripts
- No, instructions only
What it does
Build and wire an `AtomicAgent[InSchema, OutSchema]`, schemas, `AgentConfig`, `SystemPromptGenerator`, provider client, history, hooks, optional context providers. Use when the user asks to "create an agent", "add another agent", "build an `AtomicAgent`", "wire up an agent", "make a planner/router/extractor agent", or runs `/atomic-agents:create-atomic-agent`.
Create an Atomic Agent
An agent is an LLM-backed transformer from one BaseIOSchema to another. Building one means: design the schemas, write the system prompt, wire the provider client, build the AgentConfig, instantiate AtomicAgent[In, Out].
For deep material (streaming, token counting, hooks, multi-agent memory), the authority is ../framework/references/agents.md plus providers.md, prompts.md, and memory.md. This skill is the action-oriented path: clarify → write → run.
When this fires vs the umbrella framework skill
- This skill: the user is creating or wiring a specific agent, "add a planner agent", "build a Q&A agent", "make a router that classifies tickets".
frameworkskill: questions about Atomic Agents in general, or the user is doing something other than authoring an agent.
Phase 1, Clarify
Bundle into one message:
- What should the agent do? One sentence. Becomes the persona /
backgroundline. - Inputs and outputs. Use
BasicChatInputSchema/BasicChatOutputSchemafor free-form chat. Use a custom pair for anything structured (extraction, classification, planning, routing). When custom, branch to thecreate-atomic-schemaskill for the schema authoring. - Provider. OpenAI / Anthropic / Groq / Ollama / Gemini / OpenRouter / MiniMax. Default: whatever the project already uses; otherwise OpenAI.
- Conversational? Yes → wire a
ChatHistory. No (single-shot transformer) → omit it for stateless behavior. - Context providers. Anything to inject into the prompt at runtime (current time, user identity, retrieved docs)? If yes, plan to also use the
create-atomic-context-providerskill afterwards.
Skip anything already settled in context.
Phase 2, Plan
State the plan in one short block:
