firecrawl-incident-runbook
Execute Firecrawl incident response procedures with triage, mitigation, and postmortem. Use when responding to Firecrawl-related outages, investigating scrape/crawl failures, or running post-incident reviews for Firecrawl integration issues. Trigger with phrases like "firecrawl incident", "firecrawl outage", "firecrawl down", "firecrawl on-call", "firecrawl emergency", "firecrawl broken".
95
96%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%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 strong skill description that clearly defines its scope (Firecrawl incident response), lists concrete actions (triage, mitigation, postmortem, investigating failures), and provides explicit trigger guidance with natural user phrases. It uses proper third-person voice and would be easily distinguishable from other skills in a large collection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: triage, mitigation, postmortem, investigating scrape/crawl failures, and running post-incident reviews. These are distinct, actionable procedures. | 3 / 3 |
Completeness | Clearly answers both 'what' (execute incident response procedures with triage, mitigation, and postmortem) and 'when' (explicit 'Use when' clause covering outages, scrape/crawl failures, and post-incident reviews, plus explicit trigger phrases). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'firecrawl incident', 'firecrawl outage', 'firecrawl down', 'firecrawl on-call', 'firecrawl emergency', 'firecrawl broken'. These are phrases users would naturally say when experiencing issues. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific 'Firecrawl' domain combined with incident response procedures. The trigger terms are all Firecrawl-prefixed, making conflicts with other skills very unlikely. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality incident runbook that is concise, actionable, and well-structured. The decision tree is an excellent pattern for triage, and the executable scripts cover all major failure modes. The only notable weakness is that the content is somewhat long for a single SKILL.md and could benefit from splitting the postmortem/communication templates into separate referenced files.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section earns its place — severity table is compact, decision tree is efficient, code examples are minimal but complete. No unnecessary explanations of what Firecrawl is or how APIs work. | 3 / 3 |
Actionability | Provides fully executable bash scripts and TypeScript code for each error scenario. The triage script, fallback patterns, and evidence collection commands are all copy-paste ready with concrete endpoints and headers. | 3 / 3 |
Workflow Clarity | Clear sequence: Quick Triage → Decision Tree → Immediate Actions → Communication → Post-Incident. The decision tree provides explicit branching logic, and the triage section is explicitly labeled 'Run First'. The postmortem template includes timeline and action items as verification checkpoints. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections and a logical flow, but the skill is fairly long and some content (like the full postmortem template or communication templates) could be split into referenced files. The single reference to 'firecrawl-data-handling' at the end is good but minimal. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
4dee593
- 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.