firecrawl-prod-checklist
Execute Firecrawl production deployment checklist and rollback procedures. Use when deploying Firecrawl integrations to production, preparing for launch, or implementing go-live procedures. Trigger with phrases like "firecrawl production", "deploy firecrawl", "firecrawl go-live", "firecrawl launch checklist".
85
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
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-structured skill description with strong completeness and distinctiveness. It clearly identifies when to use the skill and provides explicit trigger phrases. The main weakness is that the specific capabilities could be more granular—listing concrete deployment steps rather than just 'checklist and rollback procedures'.
Suggestions
Add more specific concrete actions, e.g., 'Validates API keys, checks rate limits, runs smoke tests, configures production endpoints, and manages rollback procedures for Firecrawl deployments.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Firecrawl production deployment) and mentions some actions ('deployment checklist', 'rollback procedures'), but doesn't list specific concrete actions like 'configure environment variables, run smoke tests, verify API endpoints'. The actions remain somewhat high-level. | 2 / 3 |
Completeness | Clearly answers both 'what' (execute deployment checklist and rollback procedures) and 'when' (deploying to production, preparing for launch, go-live procedures) with explicit trigger phrases listed. | 3 / 3 |
Trigger Term Quality | Includes explicit natural trigger phrases like 'firecrawl production', 'deploy firecrawl', 'firecrawl go-live', 'firecrawl launch checklist' which are terms users would naturally say. Also includes variations like 'launch', 'go-live', and 'deploy'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to Firecrawl production deployment, which is a clear niche. The combination of 'Firecrawl' + 'production deployment' + 'rollback' makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, highly actionable production deployment skill with executable code, clear workflows, and comprehensive checklists. Its main weakness is that it's somewhat long for a SKILL.md — the detailed TypeScript implementations could be offloaded to bundle files to improve progressive disclosure and conciseness. The alerting rules table and rollback procedure are particularly well done.
Suggestions
Extract the TypeScript health check and production crawl wrapper into separate bundle files (e.g., examples/health-check.ts, examples/production-crawl.ts) and reference them from the main skill to improve conciseness and progressive disclosure.
Trim the checklist section slightly — some items like 'No hardcoded URLs in production code' are general best practices Claude already knows, not Firecrawl-specific guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with good use of checklists and code examples, but some sections like the health check endpoint and crawl wrapper are somewhat verbose for what they convey. The checklist items are well-structured but the overall document is lengthy (~150 lines) and could be tightened in places. | 2 / 3 |
Actionability | Excellent actionability with fully executable bash commands, TypeScript code examples, and concrete curl commands for verification. The production crawl wrapper, health check, and rollback procedures are all copy-paste ready with specific parameters and error handling. | 3 / 3 |
Workflow Clarity | Clear sequential steps (verify connectivity → health check → production wrapper → rollback) with explicit validation at each stage. The rollback procedure includes verification, the crawl wrapper has timeout/deadline handling, and the checklist format provides clear pre-deployment validation gates. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and a logical flow from checklist to implementation to rollback. However, the detailed code examples (health check, crawl wrapper) could be split into separate reference files to keep the main skill leaner. The reference to 'firecrawl-upgrade-migration' is good but there are no bundle files to support it. | 2 / 3 |
Total | 10 / 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
3a2d27d
- 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.