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".
89
88%
Does it follow best practices?
Impact
—
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 well-crafted skill description that clearly defines its scope (Firecrawl SDK version upgrades and API migration), provides explicit trigger guidance with natural user phrases, and occupies a distinct niche unlikely to conflict with other skills. It uses proper third-person voice and is concise without being vague.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'Upgrade Firecrawl SDK versions', 'migrate between API versions (v0 to v1/v2)', and references handling breaking changes. These are specific, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (upgrade SDK versions, migrate between API versions v0 to v1/v2) and 'when' (explicit 'Use when...' clause plus a 'Trigger with phrases like...' section with concrete examples). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'upgrade firecrawl', 'firecrawl migration', 'firecrawl v2', 'update firecrawl SDK', 'firecrawl breaking changes'. These are phrases users would naturally say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a very specific niche (Firecrawl SDK version migration). The combination of the product name 'Firecrawl' with version-specific terms (v0, v1, v2) makes conflicts with other skills extremely unlikely. | 3 / 3 |
Total | 12 / 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 well-structured migration guide with strong actionability — the before/after code examples are concrete and executable, the workflow is clearly sequenced with validation and rollback steps, and the error handling table is practical. Minor weaknesses include some verbosity that could be trimmed and the lack of bundle files to offload detailed migration examples, keeping the main skill leaner.
Suggestions
Consider moving the detailed before/after code examples for each migration path into a separate MIGRATION_EXAMPLES.md to keep the main skill as a concise overview with references.
Trim the overview paragraph which largely restates the skill description, and remove the comment in the import section ('No change needed') which adds little value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient with good use of tables and code blocks, but includes some unnecessary elements like the version history table that adds little value, and the Extract v2 section is somewhat vague. The overview paragraph could be trimmed since it restates the description. | 2 / 3 |
Actionability | Provides fully executable code examples with clear before/after migration patterns, concrete bash commands with error handling (set -euo pipefail), and a practical integration check. The breaking changes checklist and error handling table are highly actionable. | 3 / 3 |
Workflow Clarity | Clear 5-step sequence from checking current version through migration, testing, and rollback. Includes explicit validation (Step 4 with npm test and integration check), a rollback plan (Step 5), and a breaking changes checklist. The feedback loop of test → fix → re-test is implicit but the structure supports it well. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections and headers, but the skill is fairly long (~150 lines of substantive content) and could benefit from splitting detailed migration examples into a separate reference file. The external resource links are good, but the reference to 'firecrawl-ci-integration' at the end is unverifiable with no bundle files. | 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
a04d1a2
- 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.