New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Coordinating Multi Space Devops Agent

by aws in aws/agent-toolkit-for-aws

Coordinate the AWS DevOps Agent across multiple AgentSpaces from one Claude Code session — route questions to the right space (prod vs staging vs knowledge), query several spaces in parallel and…

OfficialApache-2.0Auto-check passedDevOps & Cloud

Install Coordinating Multi Space Devops Agent

skills CLI
$ npx skills add aws/agent-toolkit-for-aws --skill coordinating-multi-space-devops-agent -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install aws/agent-toolkit-for-aws coordinating-multi-space-devops-agent --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/aws-agents-for-devsecops/skills/coordinating-multi-space-devops-agent .claude/skills/coordinating-multi-space-devops-agent && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
coordinating-multi-space-devops-agent
GitHub stars
2.8k
Token cost
~1.8k tokens
SKILL.md length
663 words
Files
1
Skills in repo
138
Repo updated
First seen
Licence
Apache-2.0

At a glance

Coordinate the AWS DevOps Agent across multiple AgentSpaces from one Claude Code session — route questions to the right space (prod vs staging vs knowledge), query several spaces in parallel and…

  • Works in 3 steps: aws_devops_agent__list_agent_spaces() →… → For each space:… → Offer to write the routing guide to the…
  • The user has more than one AgentSpace configured
  • SKILL.md covers Pre-flight, Prerequisite: SigV4 auth…, Discovering spaces and Per-session routing memory, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Coordinating Multi Space Devops Agent is an agent skill from aws/agent-toolkit-for-aws, published by the product's own GitHub organization. Coordinate the AWS DevOps Agent across multiple AgentSpaces from one Claude Code session — route questions to the right space (prod vs staging vs knowledge), query several spaces in parallel and synthesize, or compare findings across accounts. Use whenever the user has more than one AgentSpace configured, mentions multiple AWS accounts, or asks something like "check both prod and staging", "compare across accounts", or "ask the knowledge space".

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud. It works with Amazon Web Services. The repository describes itself as: Official, AWS-supported MCP servers, skills, and plugins to help AI agents build on AWS. The licence is Apache-2.0.

When your agent uses it

  • The user has more than one AgentSpace configured
  • Mentions multiple AWS accounts
  • Asks something like check both prod and staging
  • Compare across accounts

Example prompts

  • “check both prod and staging”
  • “compare across accounts”
  • “ask the knowledge space”
  • “/coordinating-multi-space-devops-agent”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. aws_devops_agent__list_agent_spaces() → get all spaces.
  2. For each space: aws_devops_agent__chat(message="Summarize the AWS accounts, services, and runbooks you have access to."…
  3. Offer to write the routing guide to the project (e.g. .claude/aws-agents-for-devsecops.md, AGENTS.md, or per-project notes) so future…

What it can do on your machine

Read from SKILL.md and the folder at commit 188af2f. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Coordinating Multi Space Devops Agent loads about 1.8k tokens when it runs. Until then it costs about 122 tokens; SKILL.md has 663 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~122
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from aws/agent-toolkit-for-aws at commit 188af2f, republished under its Apache-2.0 licence (© aws). 663 words, ~1,761 tokens.

Download SKILL.mdSave it as .claude/skills/coordinating-multi-space-devops-agent/SKILL.md (or your agent's skills folder).
name
coordinating-multi-space-devops-agent
description
Coordinate the AWS DevOps Agent across multiple AgentSpaces from one Claude Code session — route questions to the right space (prod vs staging vs knowledge), query several spaces in parallel and synthesize, or compare findings across accounts. Use whenever the user has more than one AgentSpace configured, mentions multiple AWS accounts, or asks something like "check both prod and staging", "compare across accounts", or "ask the knowledge space".

Querying multiple AgentSpaces

Pre-flight

If aws_devops_agent__list_agent_spaces is not in your available tools, the remote MCP server is not connected. Tell the user to ask "help me set up the AWS DevOps Agent" so the setup-devops-agent skill auto-loads.

Prerequisite: SigV4 auth required

Multi-space routing requires SigV4 authentication — Bearer tokens are scoped to a single AgentSpace and cannot route to other spaces.

Many real teams run more than one AgentSpace — typically a production space, a staging space, and a dedicated "knowledge" space that holds runbooks shared across accounts. Each space has its own set of associated AWS accounts, runbooks, and history.

This skill is the routing brain. Use it when the user has multiple spaces configured, or when a question genuinely spans accounts.

Discovering spaces

aws_devops_agent__list_agent_spaces()
→ {"agentSpaces": [{"agentSpaceId": "as-abc123", "name": "prod"}, ...]}

If only one space is returned, this skill doesn't apply — use chatting-with-aws-devops-agent or investigating-incidents-with-aws-devops-agent directly (no agent_space_id needed).

If more than one is returned, decide whether the user's question is:

Question shapeStrategy
Scoped to one environment ("prod is broken")Single space — pick the matching one
Spans environments ("compare prod vs staging")Parallel — query each, synthesize
Generic knowledge ("what runbooks do we have for ECS?")Route to the knowledge space if one is named that way
Ambiguous ("our service is slow")Ask the user which environment, don't guess

Per-session routing memory

If the user has a routing guide stored locally (e.g. .claude/aws-agents-for-devsecops.md, AGENTS.md, or per-project notes), read it once at the start of the session and use it as the routing table for the rest of the conversation. Format expected:

markdown
| Space | AWS Profile | Agent Space ID | Purpose |
|-------|-------------|----------------|---------|
| prod  | acme-prod   | as-abc123      | Production incidents, customer-facing services |
| stage | acme-stage  | as-def456      | Pre-prod validation, integration testing |
| kb    | acme-shared | as-ghi789      | Shared runbooks, cross-account knowledge |

If no guide exists, run discovery:

  1. aws_devops_agent__list_agent_spaces() → get all spaces.
  2. For each space: aws_devops_agent__chat(message="Summarize the AWS accounts, services, and runbooks you have access to.", agent_space_id="<SPACE_ID>") → get a one-paragraph summary.
  3. Offer to write the routing guide to the project (e.g. .claude/aws-agents-for-devsecops.md, AGENTS.md, or per-project notes) so future sessions skip discovery.

Pattern A — Parallel queries, one synthesized answer

Use when the user wants a comparison: "compare prod and staging error rates", "is this issue happening in both accounts?", "audit costs across all our environments".

# 1. Query each space in parallel with environment-specific context
aws_devops_agent__chat(message="<question> | env=prod | <prod IaC context>", agent_space_id="PROD_ID")
→ {"executionId": "...", "answer": "..."}

aws_devops_agent__chat(message="<question> | env=stage | <stage IaC context>", agent_space_id="STAGE_ID")
→ {"executionId": "...", "answer": "..."}

# 2. Synthesize locally — present a side-by-side summary, not two separate dumps

Don't just paste both responses. Read both, identify what's the same vs. different, and tell the user the delta — that's the value.

Pattern B — Knowledge lookup, then per-space action

Use when one space holds runbooks/knowledge that informs work in another space.

# 1. Ask the knowledge space first
aws_devops_agent__chat(
    message="What's our standard runbook for ECS 503 errors?",
    agent_space_id="KB_ID"
)
→ {"answer": "<runbook text>"}

# 2. Apply that runbook in the target environment
aws_devops_agent__investigate(
    title="ECS 503 errors on checkout-service. [Runbook from knowledge space] <runbook text> [Local context] ...",
    agent_space_id="PROD_ID",
    priority="HIGH"
)

The DevOps Agent doesn't share state between spaces — you bridge it by quoting the knowledge space's response into the investigation's title.

Show full SKILL.md (263 more words)Show less

Pattern C — Targeted single-space query

Use when the user explicitly names a space or environment.

# Pick the matching agentSpaceId from your routing memory, pass it on the call
aws_devops_agent__chat(message="<question>", agent_space_id="<matched_space_id>")

If the routing is ambiguous and the user doesn't say, ask once — better than firing into the wrong account.

Pattern D — Investigations don't share state

Investigations are per-space. If an issue spans accounts, you may need two investigations:

aws_devops_agent__investigate(title="Latency spike — prod side", agent_space_id="PROD_ID", priority="HIGH")
aws_devops_agent__investigate(title="Latency spike — stage side", agent_space_id="STAGE_ID", priority="HIGH")

Track both taskIds. Poll both. Surface findings together.

This is rare — usually one space owns the problem. Don't fan out by default.

What NOT to do

  • Don't blast every space with every question. It's slow, expensive, and the user has to read 3× as much output.
  • Don't fan out without verifying scope. If a space's description or recorded coverage doesn't mention the relevant service, skip it — sending a question into a scope-mismatched space typically hangs rather than returning "I don't know."
  • Don't fire investigations in parallel by default. They take 5–8 minutes each. Pick the one space that owns the incident.
  • Don't silently switch spaces mid-conversation. If a follow-up needs a different space, tell the user: "Switching to the knowledge space to look up the runbook."

Timeout guidance

The chat tool buffers the full response server-side before returning. Complex cross-account queries can take 30-90s per space. If a space doesn't respond within 90s, it's likely a scope mismatch — surface a message like "Space X did not respond within 90s — skipping (likely scope mismatch)" and move on rather than hanging.

See also

  • examples/multi-space-walkthrough.md for a fully worked scenario (prod incident with staging comparison and knowledge-space runbook lookup).
  • The setup-devops-agent skill for first-time configuration of multiple AgentSpaces, AWS profiles, and shell wrappers.

© aws, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in plugins/aws-agents-for-devsecops/skills/coordinating-multi-space-devops-agent of aws/agent-toolkit-for-aws.

Open the folder on GitHubat commit 188af2f

Compare with similar skills

Coordinating Multi Space Devops Agent next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Coordinating Multi Space Devops Agent compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Coordinating Multi Space Devops Agent this skillaws/agent-toolkit-for-aws2.8k—~1.8kAutomated safety check: PassApache-2.0
Cloud Cost Optimizationwshobson/agents40k14 repos~1.7kAutomated safety check: PassMIT
Review Docshashicorp/terraform-provider-aws11k—~1.3kAutomated safety check: PassMPL-2.0
AWS Cdk Developmentzxkane/aws-skills3672 repos~2.5kAutomated safety check: PassMIT
Senior DevOps Toolkitmaslennikov-ig/claude-code-orchestrator-kit2606 repos~1.1kAutomated safety check: NotesCustom licence
Terravision Cloud Diagramspatrickchugh/terravision1.6k—~5.6kAutomated safety check: NotesAGPL-3.0-only

Similar skills

  • Cloud Cost Optimization

    wshobson/agents

    Cuts cloud spend across AWS, Azure, GCP and OCI with cost tagging, rightsizing, commitment and spot pricing models, and architecture changes.

    40k GitHub starsUsed in 14 repos~1.7k tokens
    DevOps & CloudAuto-check passed

  • Review Docs

    hashicorp/terraform-provider-aws

    Official

    Review a Terraform AWS Provider PR's end-user documentation (website/docs//.markdown): whether docs are needed, description openings, argument/attribute style, section structure, tags wording, code…

    11k GitHub stars~1.3k tokensUpdated today
    DevOps & CloudAuto-check passed

  • AWS Cdk Development

    zxkane/aws-skills

    AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript/Python.

    367 GitHub starsUsed in 2 repos~2.5k tokens
    DevOps & CloudAuto-check passed

  • Senior DevOps Toolkit

    maslennikov-ig/claude-code-orchestrator-kit

    Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…

    260 GitHub starsUsed in 6 repos~1.1k tokens
    DevOps & CloudAuto-check: notes

  • Terravision Cloud Diagrams

    patrickchugh/terravision

    Draw cloud architecture diagrams for AWS, Azure or GCP with the official provider icon sets, using TerraVision.

    1.6k GitHub stars~5.6k tokensUpdated yesterday
    DevOps & CloudAuto-check: notes

  • Thesvg

    glincker/thesvg

    Fetch brand SVG logos and cloud architecture icons (AWS, Azure, GCP) from theSVG.

    2.8k GitHub stars~1.5k tokensUpdated today
    DevOps & CloudAuto-check passed

More from aws/agent-toolkit-for-aws

All 138 skills in this repo

  • Agent Advisor

    aws/agent-toolkit-for-aws

    Official

    Entry point for AI-agent work on AWS: pick a runtime, plan a migration for existing workloads, and build an executable POC — one phased flow.

    2.8k GitHub stars~4.9k tokensUpdated today
    Auto-check passed

  • Agents Build

    aws/agent-toolkit-for-aws

    Official

    A skill your agent uses to extend an existing agent project with memory, app integration, VPC, multi-agent, migration, model, browser, code interpreter, payments, or resource removal.

    2.8k GitHub stars~2.3k tokensUpdated today
    Auto-check: notes

  • Launch With AWS

    aws/agent-toolkit-for-aws

    Official

    Migrates vibe-coded web applications to AWS. An agent skill from aws/agent-toolkit-for-aws.

    2.8k GitHub stars~3.2k tokensUpdated today
    Auto-check passed

  • Processing S3 Uploads With Step Functions

    aws/agent-toolkit-for-aws

    Official

    Deploy an event-driven workflow that routes S3 uploads to either Lambda or Fargate via Step Functions based on file size.

    2.8k GitHub stars~4k tokensUpdated today
    Auto-check passed

  • AWS Marketplace Metering

    aws/agent-toolkit-for-aws

    Official

    Deploys, queries, and debugs AWS Marketplace usage-based (PAYG) metering — the pipeline (ResolveCustomer, BatchMeterUsage, EventBridge via SAM) and querying/debugging metering records, statuses…

    2.8k GitHub stars~18k tokensUpdated today
    Auto-check passed

  • Agents Pay

    aws/agent-toolkit-for-aws

    Official

    A skill your agent uses when THIS agent needs to pay for x402-protected content at runtime: hitting a paywall mid-task, settling it via AgentCore Payments, and applying operator-defined spend limits.

    2.8k GitHub stars~6.5k tokensUpdated today
    Auto-check: notes

Works with

Categories

Questions about Coordinating Multi Space Devops Agent

What does Coordinating Multi Space Devops Agent do?

Coordinate the AWS DevOps Agent across multiple AgentSpaces from one Claude Code session — route questions to the right space (prod vs staging vs knowledge), query several spaces in parallel and…. Coordinating Multi Space Devops Agent is an agent skill from aws/agent-toolkit-for-aws, published by the product's own GitHub organization. Coordinate the AWS DevOps Agent across multiple AgentSpaces from one Claude Code session — route questions to the right space (prod vs staging vs knowledge), query several spaces in parallel and synthesize, or compare findings across accounts.

When should I use Coordinating Multi Space Devops Agent?

Coordinating Multi Space Devops Agent fits situations like: the user has more than one AgentSpace configured; mentions multiple AWS accounts; asks something like check both prod and staging; compare across accounts.

How do I install Coordinating Multi Space Devops Agent in Claude Code?

Run `npx skills add aws/agent-toolkit-for-aws --skill coordinating-multi-space-devops-agent -a claude-code`. Or copy the skill folder (plugins/aws-agents-for-devsecops/skills/coordinating-multi-space-devops-agent in aws/agent-toolkit-for-aws) into .claude/skills/coordinating-multi-space-devops-agent in your project. Claude Code loads it when a task matches its description.

How do I install Coordinating Multi Space Devops Agent in Codex?

Run `npx skills add aws/agent-toolkit-for-aws --skill coordinating-multi-space-devops-agent -a codex`. Or copy the skill folder (plugins/aws-agents-for-devsecops/skills/coordinating-multi-space-devops-agent in aws/agent-toolkit-for-aws) into .agents/skills/coordinating-multi-space-devops-agent in your project. Codex loads it when a task matches its description.

Can I use Coordinating Multi Space Devops Agent in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add aws/agent-toolkit-for-aws --skill coordinating-multi-space-devops-agent -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/coordinating-multi-space-devops-agent, .gemini/skills/coordinating-multi-space-devops-agent, .github/skills/coordinating-multi-space-devops-agent and .opencode/skills/coordinating-multi-space-devops-agent in your project.

What does Coordinating Multi Space Devops Agent need to run?

SKILL.md names no scripts, command-line tools or credentials: Coordinating Multi Space Devops Agent is instructions for the agent only.

Does Coordinating Multi Space Devops Agent access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Coordinating Multi Space Devops Agent safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Coordinating Multi Space Devops Agent use?

Coordinating Multi Space Devops Agent is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Coordinating Multi Space Devops Agent use?

About 1.8k tokens (SKILL.md is roughly 7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Coordinating Multi Space Devops Agent?

Skills that share tags, products or a category with Coordinating Multi Space Devops Agent: Cloud Cost Optimization (wshobson/agents, 40k stars), Review Docs (hashicorp/terraform-provider-aws, 11k stars), AWS Cdk Development (zxkane/aws-skills, 367 stars) and Senior DevOps Toolkit (maslennikov-ig/claude-code-orchestrator-kit, 260 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Coordinating Multi Space Devops Agent?

aws (a GitHub organization, an official publisher) maintains it in aws/agent-toolkit-for-aws, which has 2,825 GitHub stars. The repository holds 138 skills in this directory. The repository was last updated on October 7, 2026.

Source: aws/agent-toolkit-for-aws on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.