Agent skill

Ops Fires

by davepoon in davepoon/buildwithclaude

Production incidents dashboard. An agent skill from davepoon/buildwithclaude.

MITAuto-check: notesTesting & QA

Install Ops Fires

skills CLI
$ npx skills add davepoon/buildwithclaude --skill ops-fires -a claude-code

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

GitHub CLI
$ gh skill install davepoon/buildwithclaude ops-fires --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/davepoon/buildwithclaude.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/claude-ops/skills/ops-fires .claude/skills/ops-fires && 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
ops-fires
GitHub stars
3.6k
Token cost
~1.8k tokens
SKILL.md length
599 words
Files
1
Skills in repo
246
Repo updated
First seen
Licence
MIT

At a glance

Production incidents dashboard. An agent skill from davepoon/buildwithclaude.

  • Works in 3 steps: Daemon health: Read… → Secrets: AWS credentials are required… → Preferences: Read…
  • Tasks that involve Failing and flaky tests
  • SKILL.md covers Runtime Context, CLI/API Reference, Agent Teams support and Pre-gathered infrastructure data, plus 6 more sections
  • Calls aws, gh and curl; reaches sentry.io and health.aws.amazon.com; needs SENTRY_AUTH_TOKEN and AWS_ACCESS_KEY_ID

What it does

Ops Fires is an agent skill from davepoon/buildwithclaude. Production incidents dashboard. Reads ECS health, Sentry errors, CI failures. Offers to dispatch fix agents for active fires.

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 Testing & QA, covering Failing and flaky tests. It works with Sentry and Amazon Web Services. The repository describes itself as: A single hub to find Claude Skills, Agents, Commands, Hooks, Plugins, and Marketplace collections to extend Claude Code, Claude Desktop, Agent SDK and OpenClaw. The licence is MIT.

When your agent uses it

  • Tasks that involve Failing and flaky tests

Example prompts

  • “/ops-fires”

Requirements

  • A credential in SENTRY_AUTH_TOKEN
  • Pre-approved tools (allowed-tools): Bash, Read, Grep, Glob, Skill, Agent, AskUserQuestion, TeamCreate, SendMessage, TaskCreate, TaskUpdate, Monitor, WebFetch, WebSearch, mcp__sentry__search_issues, mcp__sentry__get_issue_details

Workflow steps

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

  1. Daemon health: Read ${CLAUDE_PLUGIN_DATA_DIR:-$HOME/.claude/plugins/data/ops-ops-marketplace}/daemon-health.json
  2. Secrets: AWS credentials are required for ECS/CloudWatch queries.
  3. Preferences: Read ${CLAUDE_PLUGIN_DATA_DIR}/preferences.json for secrets_manager config to know which vault to query.

What it can do on your machine

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

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash
    • Read
    • Grep
    • Glob
    • Skill
    • Agent
    • AskUserQuestion
    • TeamCreate
    • SendMessage
    • TaskCreate

    …and 6 more on the same allowed-tools line.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • aws
    • gh
    • curl

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

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • sentry.io
    • health.aws.amazon.com

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

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • SENTRY_AUTH_TOKEN
    • AWS_ACCESS_KEY_ID

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

Context cost

Ops Fires loads about 1.8k tokens when it runs. Until then it costs about 34 tokens; SKILL.md has 599 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~34
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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Bash, Read, Grep, Glob, Skill, Agent, AskUserQuestion, TeamCreate, SendMessage, TaskCreate, TaskUpda

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 davepoon/buildwithclaude at commit 10bfc43, republished under its MIT licence (© davepoon). 599 words, ~1,819 tokens.

Download SKILL.mdSave it as .claude/skills/ops-fires/SKILL.md (or your agent's skills folder).
name
ops-fires
description
Production incidents dashboard. Reads ECS health, Sentry errors, CI failures. Offers to dispatch fix agents for active fires.
allowed-tools
Bash, Read, Grep, Glob, Skill, Agent, AskUserQuestion, TeamCreate, SendMessage, TaskCreate, TaskUpdate, Monitor, WebFetch, WebSearch, mcp__sentry__search_issues, mcp__sentry__get_issue_details
argument-hint
[project-alias|all]
effort
medium
maxTurns
30

OPS ► FIRES

Runtime Context

Before executing, load available context:

  1. Daemon health: Read ${CLAUDE_PLUGIN_DATA_DIR:-$HOME/.claude/plugins/data/ops-ops-marketplace}/daemon-health.json

    • Check infra-monitor service status — if not running, pre-gathered infra data may be stale
    • If action_needed is not null → surface it immediately as a potential fire
  2. Secrets: AWS credentials are required for ECS/CloudWatch queries.

    Secret Resolution
    • First: check $AWS_ACCESS_KEY_ID / $AWS_PROFILE env vars
    • Then: doppler secrets get AWS_ACCESS_KEY_ID --plain (if doppler configured in prefs)
    • Then: use password_manager_config.query_cmd from preferences
    • Sentry token: $SENTRY_AUTH_TOKEN → Doppler SENTRY_AUTH_TOKEN → vault
  3. Preferences: Read ${CLAUDE_PLUGIN_DATA_DIR}/preferences.json for secrets_manager config to know which vault to query.

CLI/API Reference

aws CLI
CommandUsageOutput
aws ecs list-services --cluster <name> --query 'serviceArns'ECS servicesARN list
aws ecs describe-services --cluster <name> --services <arn> --query 'services[0].{status:status,running:runningCount,desired:desiredCount}'Service healthJSON
aws logs tail /ecs/<service> --since 1h --format shortECS logsLog lines (use with Monitor for live)
gh CLI (GitHub)
CommandUsageOutput
gh run list --limit 20 --json status,conclusion,name,headBranch,createdAtRecent CI runsJSON array
gh run view <id> --repo <repo> --log-failedFailed CI logsLog output
sentry-cli / Sentry API
CommandUsageOutput
sentry-cli issues list --project <slug> --status unresolvedUnresolved issuesIssue list
curl -H "Authorization: Bearer $SENTRY_AUTH_TOKEN" "https://sentry.io/api/0/projects/<org>/<proj>/issues/?query=is:unresolved"API fallback when MCP unavailableJSON array

Agent Teams support

If CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 is set, use Agent Teams when dispatching multiple fix agents simultaneously. This enables:

  • Fix agents share findings (e.g., API agent discovers DB is the root cause → infra agent pivots to DB fix)
  • You can prioritize: "CRITICAL ECS issue first, then CI failures"
  • Real-time progress: agents report as they find root causes, you can merge fixes in optimal order

Team setup (only when flag is enabled, dispatch phase):

TeamCreate("fire-fixers")
Agent(team_name="fire-fixers", name="fix-[service]", ...)

If the flag is NOT set, use standard parallel subagents.

Pre-gathered infrastructure data

${CLAUDE_PLUGIN_ROOT}/bin/ops-infra 2>/dev/null || echo '{"clusters":[],"error":"infra check failed"}'

CI failures (last 24h)

${CLAUDE_PLUGIN_ROOT}/bin/ops-ci 2>/dev/null || echo '[]'

External projects health

${CLAUDE_PLUGIN_ROOT}/bin/ops-external 2>/dev/null || echo '[]'

Your task

Analyze the pre-gathered data — including external projects. Then run parallel checks:

  1. ECS health — parse infra data for unhealthy services, stopped tasks, failed deployments.
  2. Sentry — if Sentry MCP is connected, query recent unresolved errors. Otherwise note it's unavailable.
  3. CI — parse CI data for failing pipelines, broken main/dev branches.
  4. GitHub Actions — gh run list --limit 20 --json status,conclusion,name,headBranch,createdAt 2>/dev/null
  5. External projects — parse ops-external data. Flag auth_expired as HIGH (credential rotation needed), unreachable/degraded as MEDIUM, not_configured as LOW.

Classify each issue by severity:

SeverityCriteria
CRITICALService down, DB unreachable, auth broken
HIGHElevated error rate, deploy stuck, CI main broken
MEDIUMNon-critical service degraded, flaky tests
LOWWarning-level, non-urgent

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

Output format

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 OPS ► FIRES DASHBOARD — [timestamp]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

CRITICAL
[service] — [issue] — [since]

HIGH
[service] — [issue] — [since]

MEDIUM
[service] — [issue] — [since]

ECS HEALTH
[cluster] [service] [desired/running] [status]

CI STATUS
[repo] [branch] [workflow] [status] [last run]

SENTRY (top errors, 24h)
[error] [count] [first seen] [project]

EXTERNAL PROJECTS
[alias] [source] [status] [details — e.g. auth_expired, unreachable]

──────────────────────────────────────────────────────

Use batched AskUserQuestion calls (max 4 options each). Only show relevant actions (e.g., skip dispatch options if no issues found):

AskUserQuestion call 1:

  [Dispatch fix agent for [top critical issue]]
  [Dispatch fix agent for [second issue]]
  [View logs for [service]]
  [More...]

AskUserQuestion call 2 (only if "More..."):

  [Open Sentry dashboard]
  [Open GitHub Actions]
  [All clear — nothing to do]

If no fires: show "ALL SYSTEMS OPERATIONAL" with last-checked timestamps.


Dispatch fix agent

When user selects to fix an issue, use AskUserQuestion to confirm the scope before dispatching:

Dispatch fix agent for: [issue title]
  Severity: [CRITICAL/HIGH/MEDIUM]
  Repo: [repo]
  Error: [brief description]
  
  The agent will:
  - Investigate root cause in [repo]
  - Create feature branch with fix
  - Open PR for review

  [Dispatch agent]  [Show me the logs first]  [Skip — I'll fix manually]

On confirmation, spawn an Agent with:

  • The error details and logs
  • Access to the relevant repo
  • Instruction to create a feature branch, fix, and open a PR
  • Report back when done or blocked

Use the agents/infra-monitor.md agent definition for infra issues.

If $ARGUMENTS contains a project alias, filter to that project's services only.


Native tool usage

Monitor — live service health

Use Monitor to stream ECS task logs or GitHub Actions runs when investigating fires:

Monitor(command: "aws logs tail /ecs/<service> --follow --since 5m")
Tasks — incident tracking

Use TaskCreate for each active fire. Update with TaskUpdate as fires are investigated/fixed/escalated.

WebFetch — status pages

When diagnosing fires, use WebFetch to check AWS status page (https://health.aws.amazon.com/health/status), Vercel status, or third-party API status pages.

WebSearch — known outage patterns

Use WebSearch to find if the error pattern matches a known AWS/infrastructure issue (e.g., "ECS task stopped CannotPullContainerError" → known ECR throttling).

© davepoon, MIT. 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/claude-ops/skills/ops-fires of davepoon/buildwithclaude.

Open the folder on GitHubat commit 10bfc43

Compare with similar skills

Ops Fires 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.

Ops Fires compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Ops Fires this skilldavepoon/buildwithclaude3.6k—~1.8kAutomated safety check: NotesMIT
Test Guidelinesgetsentry/sentry-react-native1.8k—~1.3kAutomated safety check: PassMIT
Test Guidelinesgetsentry/sentry-dart873—~3.1kAutomated safety check: PassMIT
Diagnosing Bugsgetsentry/sentry-react-native1.8k—~1.4kAutomated safety check: PassMIT
Diagnosing Bugsgetsentry/sentry-dart873—~1.7kAutomated safety check: PassMIT
Cell Architecturegetsentry/sentry45k—~4.6kAutomated safety check: PassCustom licence

Similar skills

  • Test Guidelines

    getsentry/sentry-react-native

    Official

    Enforce Sentry React Native SDK test conventions for naming, structure, mocking, and fixtures with Jest.

    1.8k GitHub stars~1.3k tokensUpdated today
    Testing & QAAuto-check passed
  • Test Guidelines

    getsentry/sentry-dart

    Official

    Enforce Sentry Dart/Flutter SDK test conventions for naming, structure, and fixtures.

    873 GitHub stars~3.1k tokensUpdated today
    Testing & QAAuto-check passed
  • Diagnosing Bugs

    getsentry/sentry-react-native

    Official

    A discipline for hard bugs, flaky tests, CI hangs, native crashes, and performance regressions in this SDK.

    1.8k GitHub stars~1.4k tokensUpdated today
    Testing & QAAuto-check passed
  • Diagnosing Bugs

    getsentry/sentry-dart

    Official

    A discipline for hard bugs, flaky tests, CI hangs, and performance regressions in this SDK.

    873 GitHub stars~1.7k tokensUpdated today
    Testing & QAAuto-check passed
  • Cell Architecture

    getsentry/sentry

    Official

    Reference and active migration guide for Sentry's cell architecture.

    45k GitHub stars~4.6k tokensUpdated today
    Backend & APIsAuto-check passed
  • Pester Failure Analysis

    PowerShell/PowerShell

    Investigates failing Pester tests in PowerShell CI jobs by following a six-step workflow from pull request status to documented fix recommendations.

    56k GitHub stars~5.1k tokensUpdated yesterday
    Testing & QAAuto-check passed

More from davepoon/buildwithclaude

All 246 skills in this repo
  • Qwen Vision

    davepoon/buildwithclaude

    A skill your agent uses when the user asks to "analyze video", "watch this video", "what happens in this video", "describe this clip", "review this footage", "classify these videos", "compare…

    3.6k GitHub starsUsed in 1 repo~1.2k tokens
    Auto-check passed
  • Hard Predict Future

    davepoon/buildwithclaude

    Activate this agent for any future-oriented question that requires deep quantitative analysis, historical precedents, and structured scenario planning.

    3.6k GitHub starsUsed in 1 repo~4.2k tokens
    Auto-check passed
  • iOS Hig Design Guide

    davepoon/buildwithclaude

    Build, update, and apply iOS design specifications using Apple Human Interface Guidelines (HIG) source data.

    3.6k GitHub stars~735 tokensUpdated yesterday
    Auto-check passed
  • Video Downloader

    davepoon/buildwithclaude

    Download YouTube videos with customizable quality and format options.

    3.6k GitHub starsUsed in 1 repo~871 tokens
    Auto-check passed
  • Atlas Cloud Media

    davepoon/buildwithclaude

    Discover Atlas Cloud image and video models, inspect their live schemas, and submit one confirmed media generation request with bounded GET polling.

    3.6k GitHub stars~852 tokensUpdated yesterday
    Auto-check passed
  • Slack Gif Creator

    davepoon/buildwithclaude

    Toolkit for creating animated GIFs optimized for Slack, with validators for size constraints and composable animation primitives.

    3.6k GitHub starsUsed in 12 repos~4.3k tokens
    Auto-check passed

Categories

Questions about Ops Fires

What does Ops Fires do?

Production incidents dashboard. An agent skill from davepoon/buildwithclaude. Ops Fires is an agent skill from davepoon/buildwithclaude. Production incidents dashboard.

When should I use Ops Fires?

Ops Fires fits situations like: tasks that involve Failing and flaky tests.

How do I install Ops Fires in Claude Code?

Run `npx skills add davepoon/buildwithclaude --skill ops-fires -a claude-code`. Or copy the skill folder (plugins/claude-ops/skills/ops-fires in davepoon/buildwithclaude) into .claude/skills/ops-fires in your project. Claude Code loads it when a task matches its description.

How do I install Ops Fires in Codex?

Run `npx skills add davepoon/buildwithclaude --skill ops-fires -a codex`. Or copy the skill folder (plugins/claude-ops/skills/ops-fires in davepoon/buildwithclaude) into .agents/skills/ops-fires in your project. Codex loads it when a task matches its description.

Can I use Ops Fires 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 davepoon/buildwithclaude --skill ops-fires -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ops-fires, .gemini/skills/ops-fires, .github/skills/ops-fires and .opencode/skills/ops-fires in your project.

What does Ops Fires need to run?

Going by SKILL.md and its folder, Ops Fires needs the command-line tools its instructions call (aws, gh and curl) and credentials named SENTRY_AUTH_TOKEN and AWS_ACCESS_KEY_ID. Our summary lists: A credential in SENTRY_AUTH_TOKEN. Its frontmatter pre-approves these tools: Bash, Read, Grep, Glob, Skill, Agent, AskUserQuestion, TeamCreate, SendMessage, TaskCreate, TaskUpdate, Monitor, WebFetch, WebSearch, mcp__sentry__search_issues, mcp__sentry__get_issue_details.

Does Ops Fires access the network?

SKILL.md names 2 domains. In commands or code: sentry.io and health.aws.amazon.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is Ops Fires safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Ops Fires use?

Ops Fires is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Ops Fires use?

About 1.8k tokens (SKILL.md is roughly 7.3k 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 Ops Fires?

Skills that share tags, products or a category with Ops Fires: Test Guidelines (getsentry/sentry-react-native, 1.8k stars), Test Guidelines (getsentry/sentry-dart, 873 stars), Diagnosing Bugs (getsentry/sentry-react-native, 1.8k stars) and Diagnosing Bugs (getsentry/sentry-dart, 873 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ops Fires?

davepoon (a GitHub user) maintains it in davepoon/buildwithclaude, which has 3,601 GitHub stars. The repository holds 246 skills in this directory. The repository was last updated on October 6, 2026.

Source: davepoon/buildwithclaude on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.