CtrlK
BlogDocsLog inGet started
Tessl Logo

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".

68

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

80%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A concise, highly actionable deployment checklist with executable code and concrete alert thresholds. Its main weaknesses are the absence of an explicit checklist-pass gate and a validate-retry feedback loop for the batch crawl, plus a dangling, non-existent reference to `firecrawl-upgrade-migration`.

Suggestions

Add an explicit go-live gate such as "Only proceed to production rollout once every Pre-Deployment Checklist item is checked" to strengthen the workflow's validation checkpoint.

Add a validate-fix-retry loop to the production crawl wrapper (e.g., on partial failure, fall back to per-URL scrape and retry failed pages) to satisfy the batch-operation feedback-loop expectation.

Resolve the `firecrawl-upgrade-migration` reference by either creating the referenced skill/file or removing the line, so progressive disclosure navigation is not a dead link.

DimensionReasoningScore

Conciseness

The body is lean and actionable — a checkbox checklist, one-line overview, and executable code/commands with no teaching of concepts Claude already knows (no "what Firecrawl is" preamble), so every section earns its tokens, matching the level-3 anchor.

3 / 3

Actionability

Provides fully executable curl, kubectl, and TypeScript snippets plus checklist items with concrete thresholds ("Credits < 1000", "Error rate > 5%", "limit = Math.min(opts.maxPages, 500)") that are copy-paste ready, matching the level-3 anchor.

3 / 3

Workflow Clarity

Steps 1-4 are sequenced with some verification (connectivity check, rollback verify), but the batch crawl operation lacks a validate-fix-retry feedback loop and the pre-deployment checklist has no explicit gate requiring all items to pass before go-live; the rubric caps batch/destructive workflows at level 2 without such loops.

2 / 3

Progressive Disclosure

Sections are well organized with no nested references, but all content (full code blocks, alerting table) lives inline in a ~160-line SKILL.md with no bundle files, and the sole reference `firecrawl-upgrade-migration` is a bare unsignaled name with no corresponding file — fitting the level-2 anchor where content that could be separate stays inline.

2 / 3

Total

10

/

12

Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A well-constructed description with explicit what/when guidance and natural trigger phrases in correct third-person voice. It is slightly under-comprehensive on the specific capabilities bundled in the checklist, which keeps specificity at level 2.

Suggestions

Expand the capability statement to list the concrete areas the checklist covers (e.g., credential management, crawl safety limits, error handling, monitoring) so specificity reaches level 3.

Consider adding one or two more colloquial trigger variants (e.g., "ship firecrawl", "firecrawl prod rollout") to broaden natural phrasing coverage.

DimensionReasoningScore

Specificity

Names the domain ("Firecrawl production deployment") and two concrete actions ("Execute... checklist" and "rollback procedures"), but does not enumerate what the checklist covers, so it is not comprehensive — matching the level-2 anchor rather than the multi-action level-3 example.

2 / 3

Completeness

Explicitly answers both what ("Execute Firecrawl production deployment checklist and rollback procedures") and when ("Use when deploying... preparing for launch, or implementing go-live procedures"), with an explicit trigger clause, matching the level-3 anchor.

3 / 3

Trigger Term Quality

Provides natural trigger phrases a user would say — "firecrawl production", "deploy firecrawl", "firecrawl go-live", "firecrawl launch checklist" — giving good coverage of common variations, matching the level-3 anchor.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (Firecrawl production go-live) with distinctive Firecrawl-specific triggers, making it unlikely to fire for unrelated skills, matching the level-3 anchor.

3 / 3

Total

11

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

14

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-skills
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.