Shayan Rais
b06bc14c83
- moved command-skill-agent-flow.svg to orchestration-workflow/orchestration-workflow.svg - added orchestration-workflow.gif to README - updated SVG references in implementation docs - reorganized tips into Planning, Workflows, Workflows Advanced, Debugging, Utilities, Daily sections - added tip counts to section headings - added thinking mode + output style explanatory tip - moved /rename, /permissions, /sandbox tips to appropriate sections Co-Authored-By: Claude <noreply@anthropic.com>
3.2 KiB
Sub-agents Implementation
| ← Back to Claude Code Best Practice |  |
The weather agent is implemented in this repo as an example of the Command → Agent → Skill architecture pattern, demonstrating two distinct skill patterns.
Weather Agent
File: .claude/agents/weather-agent.md
---
name: weather-agent
description: Use this agent PROACTIVELY when you need to fetch weather data for
Dubai, UAE. This agent fetches real-time temperature from wttr.in API
using its preloaded weather-fetcher skill.
tools: WebFetch, Read
model: sonnet
color: green
memory: project
skills:
- weather-fetcher
---
# Weather Agent
You are a specialized weather agent that fetches weather data for Dubai,
Pakistan.
## Your Task
Execute the weather workflow by following the instructions from your preloaded
skill:
1. **Fetch**: Follow the `weather-fetcher` skill instructions to fetch the
current temperature
2. **Report**: Return the temperature value and unit to the caller
3. **Memory**: Update your agent memory with the reading details for
historical tracking
...
The agent has one preloaded skill (weather-fetcher) that provides instructions for fetching from the wttr.in API. It returns the temperature value and unit to the calling command.
$ claude
> what is the weather in dubai?
You can create an agent using the /agents command,
$ claude
> /agents
or ask Claude to create one for you — it will generate the markdown file with YAML frontmatter and body in .claude/agents/<name>.md
The weather agent is the Agent in the Command → Agent → Skill orchestration pattern. It receives the workflow from the /weather-orchestrator command and fetches temperature using its preloaded skill (weather-fetcher). The command then invokes the standalone weather-svg-creator skill to create the visual output.
| Component | Role | This Repo |
|---|---|---|
| Command | Entry point, user interaction | /weather-orchestrator |
| Agent | Fetches data with preloaded skill (agent skill) | weather-agent with weather-fetcher |
| Skill | Creates output independently (skill) | weather-svg-creator |