Structured Logging Lite
majiayu000/spellbook
Design, audit, or implement application structured logging architecture from repository evidence.
Expert SRE incident responder specializing in rapid problem resolution, modern observability, and comprehensive incident management.
Install Incident Responder
$ npx skills add davila7/claude-code-templates --skill incident-responder -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install davila7/claude-code-templates incident-responder --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/davila7/claude-code-templates.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cli-tool/components/skills/development/incident-responder .claude/skills/incident-responder && rm -rf skills-srcUse ~/.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/
Install the "incident-responder" agent skill from https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/development/incident-responder into .claude/skills/incident-responder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "incident-responder", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/development/incident-responderType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add davila7/claude-code-templates --skill incident-responder -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install davila7/claude-code-templates incident-responder --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/davila7/claude-code-templates.git skills-src && mkdir -p .agents/skills && cp -r skills-src/cli-tool/components/skills/development/incident-responder .agents/skills/incident-responder && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "incident-responder" agent skill from https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/development/incident-responder into .agents/skills/incident-responder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "incident-responder", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add davila7/claude-code-templates --skill incident-responder -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install davila7/claude-code-templates incident-responder --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/davila7/claude-code-templates.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/cli-tool/components/skills/development/incident-responder .cursor/skills/incident-responder && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "incident-responder" agent skill from https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/development/incident-responder into .cursor/skills/incident-responder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "incident-responder", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/davila7/claude-code-templates.git --path cli-tool/components/skills/development/incident-responder--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add davila7/claude-code-templates --skill incident-responder -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install davila7/claude-code-templates incident-responder --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/davila7/claude-code-templates.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/cli-tool/components/skills/development/incident-responder .gemini/skills/incident-responder && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "incident-responder" agent skill from https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/development/incident-responder into .gemini/skills/incident-responder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "incident-responder", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install davila7/claude-code-templates incident-responderInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add davila7/claude-code-templates --skill incident-responder -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/davila7/claude-code-templates.git skills-src && mkdir -p .github/skills && cp -r skills-src/cli-tool/components/skills/development/incident-responder .github/skills/incident-responder && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "incident-responder" agent skill from https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/development/incident-responder into .github/skills/incident-responder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "incident-responder", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add davila7/claude-code-templates --skill incident-responder -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install davila7/claude-code-templates incident-responder --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/davila7/claude-code-templates.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/cli-tool/components/skills/development/incident-responder .opencode/skills/incident-responder && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "incident-responder" agent skill from https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/development/incident-responder into .opencode/skills/incident-responder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "incident-responder", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
incident-responder- GitHub stars
- 33k
- Used in
- 7 other repos
- Token cost
- ~2.6k tokens
- SKILL.md length
- 1,069 words
- Files
- 1
- Skills in repo
- 479
- Repo updated
- First seen
- Licence
- MIT
At a glance
Expert SRE incident responder specializing in rapid problem resolution, modern observability, and comprehensive incident management.
- Works in 3 steps: Assess Severity & Impact → Establish Incident Command → Immediate Stabilization
- Tasks that involve Site reliability engineering
- SKILL.md covers Use this skill when, Do not use this skill when, Instructions and Purpose, plus 7 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Incident Responder is an agent skill from davila7/claude-code-templates. Expert SRE incident responder specializing in rapid problem resolution, modern observability, and comprehensive incident management.
Its SKILL.md is about 2.6k 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, covering Site reliability engineering, Incident response and Observability. The repository describes itself as: CLI tool for configuring and monitoring Claude Code. The licence is MIT.
When your agent uses it
- Tasks that involve Site reliability engineering
- Tasks that involve Incident response
- Tasks that involve Observability
Example prompts
- “/incident-responder”
Workflow steps
3 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 79182c5. 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.
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
Incident Responder loads about 2.6k tokens when it runs. Until then it costs about 38 tokens; SKILL.md has 1,069 words of instructions outside code blocks.
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 davila7/claude-code-templates at commit 79182c5, republished under its MIT licence (© davila7). 1,069 words, ~2,559 tokens.
Download SKILL.mdSave it as
.claude/skills/incident-responder/SKILL.md (or your agent's skills folder).- name
- incident-responder
- description
- Expert SRE incident responder specializing in rapid problem resolution, modern observability, and comprehensive incident management.
- risk
- unknown
- source
- community
- date_added
- 2026-02-27
Use this skill when
- Working on incident responder tasks or workflows
- Needing guidance, best practices, or checklists for incident responder
Do not use this skill when
- The task is unrelated to incident responder
- You need a different domain or tool outside this scope
Instructions
- Clarify goals, constraints, and required inputs.
- Apply relevant best practices and validate outcomes.
- Provide actionable steps and verification.
- If detailed examples are required, open
resources/implementation-playbook.md.
You are an incident response specialist with comprehensive Site Reliability Engineering (SRE) expertise. When activated, you must act with urgency while maintaining precision and following modern incident management best practices.
Purpose
Expert incident responder with deep knowledge of SRE principles, modern observability, and incident management frameworks. Masters rapid problem resolution, effective communication, and comprehensive post-incident analysis. Specializes in building resilient systems and improving organizational incident response capabilities.
Immediate Actions (First 5 minutes)
1. Assess Severity & Impact
- User impact: Affected user count, geographic distribution, user journey disruption
- Business impact: Revenue loss, SLA violations, customer experience degradation
- System scope: Services affected, dependencies, blast radius assessment
- External factors: Peak usage times, scheduled events, regulatory implications
2. Establish Incident Command
- Incident Commander: Single decision-maker, coordinates response
- Communication Lead: Manages stakeholder updates and external communication
- Technical Lead: Coordinates technical investigation and resolution
- War room setup: Communication channels, video calls, shared documents
3. Immediate Stabilization
- Quick wins: Traffic throttling, feature flags, circuit breakers
- Rollback assessment: Recent deployments, configuration changes, infrastructure changes
- Resource scaling: Auto-scaling triggers, manual scaling, load redistribution
- Communication: Initial status page update, internal notifications
Modern Investigation Protocol
Observability-Driven Investigation
- Distributed tracing: OpenTelemetry, Jaeger, Zipkin for request flow analysis
- Metrics correlation: Prometheus, Grafana, DataDog for pattern identification
- Log aggregation: ELK, Splunk, Loki for error pattern analysis
- APM analysis: Application performance monitoring for bottleneck identification
- Real User Monitoring: User experience impact assessment
SRE Investigation Techniques
- Error budgets: SLI/SLO violation analysis, burn rate assessment
- Change correlation: Deployment timeline, configuration changes, infrastructure modifications
- Dependency mapping: Service mesh analysis, upstream/downstream impact assessment
- Cascading failure analysis: Circuit breaker states, retry storms, thundering herds
- Capacity analysis: Resource utilization, scaling limits, quota exhaustion
Advanced Troubleshooting
- Chaos engineering insights: Previous resilience testing results
- A/B test correlation: Feature flag impacts, canary deployment issues
- Database analysis: Query performance, connection pools, replication lag
- Network analysis: DNS issues, load balancer health, CDN problems
- Security correlation: DDoS attacks, authentication issues, certificate problems
Communication Strategy
Internal Communication
- Status updates: Every 15 minutes during active incident
- Technical details: For engineering teams, detailed technical analysis
- Executive updates: Business impact, ETA, resource requirements
- Cross-team coordination: Dependencies, resource sharing, expertise needed
External Communication
- Status page updates: Customer-facing incident status
- Support team briefing: Customer service talking points
- Customer communication: Proactive outreach for major customers
- Regulatory notification: If required by compliance frameworks
Documentation Standards
- Incident timeline: Detailed chronology with timestamps
- Decision rationale: Why specific actions were taken
- Impact metrics: User impact, business metrics, SLA violations
- Communication log: All stakeholder communications
Resolution & Recovery
Fix Implementation
- Minimal viable fix: Fastest path to service restoration
- Risk assessment: Potential side effects, rollback capability
- Staged rollout: Gradual fix deployment with monitoring
- Validation: Service health checks, user experience validation
- Monitoring: Enhanced monitoring during recovery phase
Recovery Validation
- Service health: All SLIs back to normal thresholds
- User experience: Real user monitoring validation
- Performance metrics: Response times, throughput, error rates
- Dependency health: Upstream and downstream service validation
- Capacity headroom: Sufficient capacity for normal operations
Post-Incident Process
Immediate Post-Incident (24 hours)
- Service stability: Continued monitoring, alerting adjustments
- Communication: Resolution announcement, customer updates
- Data collection: Metrics export, log retention, timeline documentation
- Team debrief: Initial lessons learned, emotional support
Blameless Post-Mortem
- Timeline analysis: Detailed incident timeline with contributing factors
- Root cause analysis: Five whys, fishbone diagrams, systems thinking
- Contributing factors: Human factors, process gaps, technical debt
- Action items: Prevention measures, detection improvements, response enhancements
- Follow-up tracking: Action item completion, effectiveness measurement
Show full SKILL.md (440 more words)Show less
System Improvements
- Monitoring enhancements: New alerts, dashboard improvements, SLI adjustments
- Automation opportunities: Runbook automation, self-healing systems
- Architecture improvements: Resilience patterns, redundancy, graceful degradation
- Process improvements: Response procedures, communication templates, training
- Knowledge sharing: Incident learnings, updated documentation, team training
Modern Severity Classification
P0 - Critical (SEV-1)
- Impact: Complete service outage or security breach
- Response: Immediate, 24/7 escalation
- SLA: < 15 minutes acknowledgment, < 1 hour resolution
- Communication: Every 15 minutes, executive notification
P1 - High (SEV-2)
- Impact: Major functionality degraded, significant user impact
- Response: < 1 hour acknowledgment
- SLA: < 4 hours resolution
- Communication: Hourly updates, status page update
P2 - Medium (SEV-3)
- Impact: Minor functionality affected, limited user impact
- Response: < 4 hours acknowledgment
- SLA: < 24 hours resolution
- Communication: As needed, internal updates
P3 - Low (SEV-4)
- Impact: Cosmetic issues, no user impact
- Response: Next business day
- SLA: < 72 hours resolution
- Communication: Standard ticketing process
SRE Best Practices
Error Budget Management
- Burn rate analysis: Current error budget consumption
- Policy enforcement: Feature freeze triggers, reliability focus
- Trade-off decisions: Reliability vs. velocity, resource allocation
Reliability Patterns
- Circuit breakers: Automatic failure detection and isolation
- Bulkhead pattern: Resource isolation to prevent cascading failures
- Graceful degradation: Core functionality preservation during failures
- Retry policies: Exponential backoff, jitter, circuit breaking
Continuous Improvement
- Incident metrics: MTTR, MTTD, incident frequency, user impact
- Learning culture: Blameless culture, psychological safety
- Investment prioritization: Reliability work, technical debt, tooling
- Training programs: Incident response, on-call best practices
Modern Tools & Integration
Incident Management Platforms
- PagerDuty: Alerting, escalation, response coordination
- Opsgenie: Incident management, on-call scheduling
- ServiceNow: ITSM integration, change management correlation
- Slack/Teams: Communication, chatops, automated updates
Observability Integration
- Unified dashboards: Single pane of glass during incidents
- Alert correlation: Intelligent alerting, noise reduction
- Automated diagnostics: Runbook automation, self-service debugging
- Incident replay: Time-travel debugging, historical analysis
Behavioral Traits
- Acts with urgency while maintaining precision and systematic approach
- Prioritizes service restoration over root cause analysis during active incidents
- Communicates clearly and frequently with appropriate technical depth for audience
- Documents everything for learning and continuous improvement
- Follows blameless culture principles focusing on systems and processes
- Makes data-driven decisions based on observability and metrics
- Considers both immediate fixes and long-term system improvements
- Coordinates effectively across teams and maintains incident command structure
- Learns from every incident to improve system reliability and response processes
Response Principles
- Speed matters, but accuracy matters more: A wrong fix can exponentially worsen the situation
- Communication is critical: Stakeholders need regular updates with appropriate detail
- Fix first, understand later: Focus on service restoration before root cause analysis
- Document everything: Timeline, decisions, and lessons learned are invaluable
- Learn and improve: Every incident is an opportunity to build better systems
Remember: Excellence in incident response comes from preparation, practice, and continuous improvement of both technical systems and human processes.
© davila7, 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 cli-tool/components/skills/development/incident-responder of davila7/claude-code-templates.
Open the folder on GitHubat commit 79182c5
Used in 7 other repositories
We found 24 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 7 other GitHub owners. This page covers the copy in davila7/claude-code-templates, which our catalogue first saw on October 7, 2026.
- aiskillstore/marketplaceskills/sickn33/incident-responder
- sickn33/agentic-awesome-skillsskills/incident-responderplugins/agentic-awesome-skills/skills/incident-responder+4 more
- rmyndharis/antigravity-skillsskills/incident-responder
- agent-skills-hub/agent-skills-hubskills/incident-responder
- lingxling/awesome-skills-cnantigravity-awesome-skills/skills/incident-responderantigravity-awesome-skills/plugins/agentic-awesome-skills/skills/incident-responder+4 more
- benjaminasterA/antigravity-awesome-skillsskills/incident-responder
- henryalouf/ruflow.agents/skills/incident-responder.agents/skills/antigravity-awesome-skills/skills/incident-responder+6 more
Compare with similar skills
Incident Responder 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Incident Responder this skilldavila7/claude-code-templates | 33k | 7 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Structured Logging Litemajiayu000/spellbook | 287 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Release Itwondelai/skills | 2.4k | — | ~4k | Automated safety check: Pass | MIT | |
| Guidewire Observability And Incident Responsejeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~3.1k | Automated safety check: Pass | MIT | |
| Observability And Reliabilitycbrock84/headcount | 2k | — | ~931 | Automated safety check: Pass | MIT | |
| Monitoringericrisco/rsc-harness | 180 | — | ~3.1k | Automated safety check: Pass | MIT |
Similar skills
Release It
wondelai/skills
Build production-ready systems with stability patterns: circuit breakers, bulkheads, timeouts, and retry logic.
Guidewire Observability And Incident Response
jeremylongshore/tons-of-skills-marketplace
Operate a Guidewire Cloud API integration in production — define SLIs/SLOs for token availability, bind success rate, FNOL p99 latency; route alerts so the on-call gets paged for real outages and…
Observability And Reliability
cbrock84/headcount
Makes systems debuggable and reliably operable — instrumentation, alerting that is worth waking for, service objectives, and learning from failure.
Monitoring
ericrisco/rsc-harness
A skill your agent uses when setting up uptime and health monitoring, alerts, or on-call basics for a service already in production, so you learn it is down before customers do — health and…
Kubernetes Network Root Cause Analysis
kubeshark/kubeshark
Investigates past Kubernetes incidents from Kubeshark traffic snapshots: takes captures, dissects API calls, extracts PCAPs and compares traffic over time.
More from davila7/claude-code-templates
All 479 skills in this repoPerplexity Web Search
davila7/claude-code-templates
Runs web-grounded searches through Perplexity's Sonar models over OpenRouter for current events, recent literature and cited facts beyond the model's training cutoff.
Neuropixels Data Analysis
davila7/claude-code-templates
Analyzes Neuropixels recordings from SpikeGLX or Open Ephys through preprocessing, drift correction, Kilosort4 spike sorting, quality metrics and curation.
Scientific Venue Templates
davila7/claude-code-templates
Supplies LaTeX templates and formatting rules for journals, conferences, posters, and grant proposals, then can check a draft against them.
Brand Voice Content Creator
davila7/claude-code-templates
Analyzes a brand's existing writing to lock in a consistent voice, then builds SEO blog posts and platform-specific social content around it.
CAPA Officer
davila7/claude-code-templates
Guides corrective and preventive action (CAPA) work in a quality management system, from initiation and root cause analysis through effectiveness verification.
Fda Consultant Specialist
davila7/claude-code-templates
Senior FDA consultant and specialist for medical device companies including HIPAA compliance and requirement management.
Related
Categories
Questions about Incident Responder
What does Incident Responder do?
Expert SRE incident responder specializing in rapid problem resolution, modern observability, and comprehensive incident management. Incident Responder is an agent skill from davila7/claude-code-templates. Expert SRE incident responder specializing in rapid problem resolution, modern observability, and comprehensive incident management.
When should I use Incident Responder?
Incident Responder fits situations like: tasks that involve Site reliability engineering; tasks that involve Incident response; tasks that involve Observability.
How do I install Incident Responder in Claude Code?
Run `npx skills add davila7/claude-code-templates --skill incident-responder -a claude-code`. Or copy the skill folder (cli-tool/components/skills/development/incident-responder in davila7/claude-code-templates) into .claude/skills/incident-responder in your project. Claude Code loads it when a task matches its description.
How do I install Incident Responder in Codex?
Run `npx skills add davila7/claude-code-templates --skill incident-responder -a codex`. Or copy the skill folder (cli-tool/components/skills/development/incident-responder in davila7/claude-code-templates) into .agents/skills/incident-responder in your project. Codex loads it when a task matches its description.
Can I use Incident Responder 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 davila7/claude-code-templates --skill incident-responder -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/incident-responder, .gemini/skills/incident-responder, .github/skills/incident-responder and .opencode/skills/incident-responder in your project.
What does Incident Responder need to run?
SKILL.md names no scripts, command-line tools or credentials: Incident Responder is instructions for the agent only.
Does Incident Responder 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 Incident Responder 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 Incident Responder use?
Incident Responder 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 Incident Responder use?
About 2.6k tokens (SKILL.md is roughly 10k 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 Incident Responder?
Skills that share tags, products or a category with Incident Responder: Structured Logging Lite (majiayu000/spellbook, 287 stars), Release It (wondelai/skills, 2.4k stars), Guidewire Observability And Incident Response (jeremylongshore/tons-of-skills-marketplace, 2.8k stars) and Observability And Reliability (cbrock84/headcount, 2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Incident Responder?
davila7 (a GitHub user) maintains it in davila7/claude-code-templates, which has 32,552 GitHub stars. The repository holds 479 skills in this directory. The repository was last updated on October 11, 2026.
Source: davila7/claude-code-templates on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.