firecrawl-local-dev-loop
Configure Firecrawl local development with self-hosted Docker, mocking, and testing. Use when setting up a development environment, running Firecrawl locally to save credits, or configuring test workflows with vitest. Trigger with phrases like "firecrawl dev setup", "firecrawl local development", "firecrawl docker", "firecrawl self-hosted dev", "firecrawl test setup".
84
82%
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 local development configuration), provides explicit trigger guidance, and occupies a distinct niche. It uses third-person voice correctly, lists concrete actions, and includes both 'Use when' and 'Trigger with' clauses that cover natural user phrasings.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: configuring local development, self-hosted Docker setup, mocking, and testing. These are distinct, actionable capabilities rather than vague language. | 3 / 3 |
Completeness | Clearly answers both 'what' (configure Firecrawl local dev with Docker, mocking, testing) and 'when' (setting up dev environment, running locally to save credits, configuring test workflows). Has explicit 'Use when' and 'Trigger with' clauses. | 3 / 3 |
Trigger Term Quality | Includes excellent natural trigger terms that users would actually say: 'firecrawl dev setup', 'firecrawl local development', 'firecrawl docker', 'firecrawl self-hosted dev', 'firecrawl test setup', plus mentions of vitest and saving credits. Good coverage of variations. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a very specific niche (Firecrawl local development). The combination of 'Firecrawl' + 'local development' + 'Docker' + 'vitest' makes it extremely unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%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, highly actionable skill with complete, executable code examples covering Docker setup, configuration, mocking, and testing. Its main weaknesses are moderate verbosity (some sections could be tightened) and missing explicit validation checkpoints between steps — particularly around confirming Docker services are fully healthy before proceeding to integration tests. The error handling table is a nice touch that adds practical value.
Suggestions
Add an explicit validation checkpoint between Docker startup (Step 2) and integration testing (Step 5), e.g., a script or command that confirms Firecrawl is accepting requests before proceeding.
Trim the Overview and Output sections — the step titles and code already communicate what's being built; these sections add little for Claude.
Consider extracting the longer test files (Steps 4-5) into referenced bundle files to improve progressive disclosure and reduce inline content length.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary elements — the 'Overview' section restates what the description already conveys, the 'Prerequisites' list is somewhat obvious for Claude, and the 'Output' section is redundant given the steps already describe what's produced. However, the code examples themselves are lean and purposeful. | 2 / 3 |
Actionability | Excellent actionability — every step includes fully executable code: a complete docker-compose.yml, TypeScript config, vitest unit and integration test files, package.json scripts, and a dev scrape script. All are copy-paste ready with realistic configurations. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (1-6) and logically ordered, but validation is limited. Step 2 includes a health check curl, which is good, but there's no explicit feedback loop for Docker startup failures, no 'wait until healthy then proceed' checkpoint, and no validation step after the full setup is complete to confirm everything works end-to-end. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a helpful error table, but it's quite long (~170 lines of content) with all code inline. The unit test and integration test examples could be referenced as separate files. The 'Next Steps' reference to 'firecrawl-sdk-patterns' is good but there are no bundle files to support progressive disclosure. | 2 / 3 |
Total | 9 / 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
3a2d27d
- 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.