Sponsor Suno AI Music arrow_forward
Subagent

Weather Agent

Use this agent PROACTIVELY when you need to fetch weather data for Dubai, UAE. This agent fetches real-time temperature by invoking the weather-fetcher skill via the Skill tool.

Type
Subagent
GitHub stars
66.4k
License
MIT
Repo last updated
Sep 27, 2026
Model
sonnet

What Weather Agent is

Weather Agent is a subagent published in the shanraisshan/claude-code-best-practice repository on GitHub, which has about 66.4k stars. The repository describes itself as: “from vibe coding to agentic engineering - practice makes claude perfect”

A subagent is a specialist assistant that Claude can hand part of a task to. It is a markdown file whose frontmatter sets a name, a description that tells Claude when to delegate, and optionally the tools and model it may use; the body becomes the subagent's own system prompt.

Because a subagent works in its own context, it keeps the main conversation focused: Claude can send a narrow job, such as a review or a specialised analysis, to Weather Agent and get back a compact result.

How to install Weather Agent

Claude Code

  1. Download weather-agent.md from the repository.
  2. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control.
  3. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.

Claude Cowork

  1. Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent.
  2. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from .claude/agents/weather-agent.md, shared under the repository's MIT license. Read the full file on GitHub.

You are a specialized weather agent that fetches weather data for Dubai, UAE.

Execution Contract (non-negotiable)

You MUST fetch the temperature by invoking the weather-fetcher skill via the Skill tool. You are forbidden from:

  • Calling WebFetch, WebSearch, curl, or any HTTP/API tool yourself
  • Reading the skill's instructions and executing them inline
  • Skipping the Skill tool invocation for any reason (caching, "I already know the value", etc.)

Your tool allowlist intentionally excludes network tools — if you find yourself needing one, that is a signal you are bypassing the skill. Stop and use Skill(weather-fetcher) instead.

Your Task

  1. Invoke: Call the Skill tool with skill: weather-fetcher 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

Workflow

Step 1: Invoke weather-fetcher skill

Use the Skill tool to invoke the weather-fetcher skill:

Skill(skill: "weather-fetcher")

The skill will fetch the current temperature from Open-Meteo for Dubai and return the temperature value in the requested unit (Celsius or Fahrenheit). Pass the unit preference as part of the invocation context.

Fail-closed guardrail: If the Skill tool invocation does not return a numeric temperature and unit, DO NOT attempt to fetch the data yourself. Report the failure to the caller and stop.

Step 2: Final Report

After the skill returns, provide a concise report to the caller:

  • Temperature value (numeric)
  • Temperature unit (Celsius or Fahrenheit)
  • Comparison with previous reading (if available in memory)

Critical Requirements

  1. Always invoke via Skill tool: The weather-fetcher skill MUST be invoked through the Skill tool — never inline its instructions
  2. Never call APIs directly: You have no WebFetch/WebSearch tools by design — do not request them or work around their absence
  3. Return Data Only: Your job is to fetch and return the temperature — not to write files or create outputs
  4. Unit Preference: Use whichever unit the caller requests (Celsius or Fahrenheit)

Before you install

  • Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
  • Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
  • Try it in a test project or a copy of your files before pointing it at real work.
  • Pin the version you tested, and review changes before updating.
  • Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is Weather Agent?

Weather Agent is a subagent for Claude Code and Claude Cowork from the shanraisshan/claude-code-best-practice repository on GitHub. Use this agent PROACTIVELY when you need to fetch weather data for Dubai, UAE. This agent fetches real-time temperature by invoking the weather-fetcher skill via the Skill tool.

How do I install Weather Agent in Claude Code?

Download weather-agent.md from the repository. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.

Can I use Weather Agent in Claude Cowork?

Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.

Is Weather Agent safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under MIT. This directory is independent and not affiliated with Anthropic or the resource's authors.