firecrawl-incident-runbook
Execute FireCrawl incident response procedures with triage, mitigation, and postmortem. Use when responding to FireCrawl-related outages, investigating errors, or running post-incident reviews for FireCrawl integration failures. Trigger with phrases like "firecrawl incident", "firecrawl outage", "firecrawl down", "firecrawl on-call", "firecrawl emergency", "firecrawl broken".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill firecrawl-incident-runbook94
Does it follow best practices?
Validation for skill structure
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description with strong completeness and excellent trigger term coverage. The explicit 'Use when' clause and enumerated trigger phrases make it easy for Claude to select appropriately. The main weakness is that the specific actions (triage, mitigation, postmortem) are somewhat generic incident response terminology rather than FireCrawl-specific procedures.
Suggestions
Consider adding more specific FireCrawl actions like 'check API rate limits', 'verify webhook configurations', or 'review crawl job status' to increase specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (FireCrawl incident response) and lists some actions (triage, mitigation, postmortem), but these are somewhat generic incident response terms rather than highly specific concrete actions unique to FireCrawl. | 2 / 3 |
Completeness | Clearly answers both what (execute incident response procedures with triage, mitigation, postmortem) and when (responding to outages, investigating errors, running post-incident reviews) with explicit trigger phrases listed. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'firecrawl incident', 'firecrawl outage', 'firecrawl down', 'firecrawl on-call', 'firecrawl emergency', 'firecrawl broken' - these match real user language during incidents. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific 'FireCrawl' qualifier throughout - unlikely to conflict with generic incident response skills or other integration-specific skills. The trigger terms are all FireCrawl-prefixed. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent incident runbook that exemplifies good skill design. It provides concrete, executable commands for every scenario, uses efficient formatting (tables, decision trees, code blocks), and follows a clear workflow from triage through postmortem. The content respects Claude's intelligence while providing the specific, context-dependent information needed for incident response.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, presenting only actionable information without explaining concepts Claude already knows. Tables, decision trees, and code blocks are used effectively to maximize information density. | 3 / 3 |
Actionability | Provides fully executable bash commands, kubectl operations, and curl requests that are copy-paste ready. Each error type has specific, concrete remediation steps with exact commands. | 3 / 3 |
Workflow Clarity | Clear decision tree for triage, explicit numbered steps in the Instructions section, and well-defined severity levels with response times. The workflow includes validation checkpoints (check status → identify source → remediate → communicate → collect evidence). | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections (Quick Triage, Decision Tree, Immediate Actions by Error Type, Communication Templates, Post-Incident). References to external resources and related skills are clearly signaled at the end without deep nesting. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.