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
Pending
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 an excellent skill description that clearly defines its scope around Firecrawl SDK version migration, provides explicit trigger guidance with natural user phrases, and occupies a very distinct niche. It follows best practices by using third person voice, including a 'Use when' clause, and listing concrete trigger phrases.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'Upgrade Firecrawl SDK versions', 'migrate between API versions (v0 to v1/v2)', 'handling breaking changes between versions'. 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 explicitly listed: 'upgrade firecrawl', 'firecrawl migration', 'firecrawl v2', 'update firecrawl SDK', 'firecrawl breaking changes'. These are terms users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a very specific niche (Firecrawl SDK version migration). The named product, version numbers, and migration-specific language make it extremely unlikely to conflict with other skills. | 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 solid migration skill with excellent actionability — the before/after code examples are the highlight, making it very clear what needs to change. The workflow is well-sequenced with proper validation and rollback steps. It could be slightly more concise by trimming the overview and tightening some sections, and the inline content is borderline long enough to warrant splitting into sub-files.
Suggestions
Trim the overview paragraph since it largely restates the YAML description; a single sentence would suffice.
Consider moving the detailed migration code examples (v0→v1, v1→v2) into a separate MIGRATION_EXAMPLES.md and keeping only a summary table with the most critical changes inline.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient 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 skill description. | 2 / 3 |
Actionability | Provides fully executable code examples with clear before/after migration patterns, concrete bash commands with `set -euo pipefail`, and specific TypeScript examples showing exact API changes. The integration check script is copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear 5-step sequence with explicit validation (Step 4 runs tests and integration check), a rollback step (Step 5), and a breaking changes checklist. The workflow includes creating a branch first, testing after upgrade, and rolling back if needed — a proper feedback loop for a potentially destructive upgrade. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a checklist, but it's fairly long and inline. The error handling table and detailed migration examples could potentially be split into a separate reference file. The Resources section provides good external links, and the Next Steps reference is one level deep. | 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
c8a915c
- 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.