CtrlK
BlogDocsLog inGet started
Tessl Logo

firecrawl-upgrade-migration

Upgrade Firecrawl SDK versions and migrate between API versions (v0 to v1/v2). Use when upgrading the SDK, handling breaking changes between versions, or migrating from the old API to the current v2 API. Trigger with phrases like "upgrade firecrawl", "firecrawl migration", "firecrawl v2", "update firecrawl SDK", "firecrawl breaking changes".

71

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

77%

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

The body is highly actionable with a clear, validated workflow, but it loses points on conciseness (duplication between the checklist/error table and the code examples) and progressive disclosure (everything inline with no reference files for a longer skill).

Suggestions

Remove the 'Breaking Changes Checklist' and 'Error Handling' table entries that duplicate the BEFORE/AFTER code examples, or fold them into the examples, to cut redundant tokens and improve conciseness.

Split the detailed v0->v1/v2 migration code examples or the error-handling reference into a one-level-deep file (e.g. MIGRATION-EXAMPLES.md) with a clearly signaled link from the overview, to improve progressive disclosure for this longer skill.

Add an explicit 'if npm test fails: fix the breaking change and re-run' feedback loop in Step 4 rather than only offering rollback, making the validate->fix->retry cycle explicit.

DimensionReasoningScore

Conciseness

The body is mostly lean and code-focused, but the 'Breaking Changes Checklist' and 'Error Handling' table restate changes already shown in the BEFORE/AFTER code examples, so it could be tightened; not level 3 because not every token earns its place due to this duplication.

2 / 3

Actionability

Bash steps use 'set -euo pipefail' with concrete npm/git commands, and the TypeScript BEFORE/AFTER examples are executable and copy-paste ready; the v2 extract comment is explicitly justified rather than unjustified pseudocode, meeting the level-3 anchor.

3 / 3

Workflow Clarity

Five steps are clearly sequenced with validation checkpoints ('npm test' in Steps 2 and 4 plus an integration check), a rollback path in Step 5, and a checklist plus error-handling table for recovery, matching the level-3 anchor.

3 / 3

Progressive Disclosure

Sections are well-organized, but all content is inline in a single ~175-line file with no bundle-file references; for a skill this long, detailed migration examples or error handling could be split into one-level-deep reference files, so it does not reach level 3.

2 / 3

Total

10

/

12

Passed

Description

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.

The description is strong across all dimensions: it states concrete actions, provides natural trigger phrases, explicitly covers both what and when, and occupies a distinct niche. No changes needed.

DimensionReasoningScore

Specificity

It lists multiple concrete actions — 'Upgrade Firecrawl SDK versions and migrate between API versions (v0 to v1/v2)', 'handling breaking changes between versions', and 'migrating from the old API to the current v2 API' — rather than vague language, matching the level-3 anchor.

3 / 3

Completeness

It explicitly answers both what ('Upgrade Firecrawl SDK versions and migrate between API versions') and when ('Use when upgrading the SDK, handling breaking changes... or migrating from the old API to the current v2 API') with explicit trigger phrases, matching the level-3 anchor.

3 / 3

Trigger Term Quality

Phrases like 'upgrade firecrawl', 'firecrawl migration', 'firecrawl v2', 'update firecrawl SDK', and 'firecrawl breaking changes' are natural terms a user would actually say, giving good coverage as required for level 3.

3 / 3

Distinctiveness Conflict Risk

The Firecrawl SDK upgrade/migration niche is highly specific with distinct triggers, making it unlikely to fire for unrelated skills and matching the level-3 anchor for a clear niche.

3 / 3

Total

12

/

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.