CtrlK
BlogDocsLog inGet started
Tessl Logo

firecrawl-migration-deep-dive

Migrate to Firecrawl from Puppeteer, Playwright, Cheerio, or other scraping tools. Use when replacing custom scraping code with Firecrawl, migrating between scraping APIs, or re-platforming content ingestion pipelines. Trigger with phrases like "migrate to firecrawl", "replace puppeteer with firecrawl", "switch to firecrawl", "firecrawl vs puppeteer", "firecrawl migration".

69

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

76%Weight 40%Scale 1-5

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

The body delivers concrete, executable migration guidance with strong before/after examples and a useful comparison table. Its main weakness is the destructive dependency-removal step lacking an explicit validate-before-proceed checkpoint.

Suggestions

Add an explicit validation gate before Step 5: require confirmation that parallel-run output comparison passed and that `grep -r` for old references is clean before running `npm uninstall`, with a fix-and-retry loop if checks fail.

Move the destructive `npm uninstall` / `npx playwright uninstall` commands behind a pre-flight verification block that fails the migration if any old-tool references still exist in src/.

Tighten the overview by removing the "This skill shows equivalent code..." sentence, since the structure already makes this self-evident.

DimensionReasoningScore

Conciseness

Largely lean and efficient with no padding about concepts Claude already knows; the comparison table and code examples all earn their place, with only minor instances (the overview restatement, the "Current State" probe command) that could be trimmed.

4 / 5

Actionability

Fully executable BEFORE/AFTER TypeScript examples and a copy-paste bash cleanup block cover the common migration cases with concrete, runnable code rather than pseudocode or abstractions.

5 / 5

Workflow Clarity

The five-step sequence is clearly ordered, but Step 5 performs destructive/batch dependency removal without an explicit validation checkpoint gating the uninstall, and the rubric caps workflow_clarity at 3 for destructive operations lacking validation.

3 / 5

Progressive Disclosure

Well-organized single-file structure with clear section headers and a single outward reference to advanced troubleshooting; no bundle files exist to verify, and the inline content is appropriately cohesive for this single-purpose skill.

4 / 5

Total

16

/

20

Passed

Description

95%Weight 40%Scale 1-5

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

The description is specific, complete, and trigger-rich, clearly communicating what the skill does and when to invoke it with natural user phrases. It avoids vague fluff and third-person voice is maintained throughout.

DimensionReasoningScore

Specificity

Names the migration domain and several concrete source tools ("Puppeteer, Playwright, Cheerio, or other scraping tools"), giving comprehensive source coverage, though the migration actions themselves stay at a high level rather than enumerating discrete operations.

4 / 5

Completeness

Explicitly answers both what ("Migrate to Firecrawl from Puppeteer, Playwright, Cheerio...") and when (explicit "Use when..." clause plus a concrete "Trigger with phrases like..." list), matching the top anchor.

5 / 5

Trigger Term Quality

Provides comprehensive natural trigger phrases including variations and synonyms ("migrate to firecrawl", "replace puppeteer with firecrawl", "switch to firecrawl", "firecrawl vs puppeteer", "firecrawl migration") that users would realistically say.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (Firecrawl migration) with triggers naming specific competing tools, making it highly distinguishable with minimal conflict risk against unrelated skills.

5 / 5

Total

19

/

20

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.