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
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 a well-crafted skill description that clearly defines its scope (Firecrawl local development configuration), provides explicit use-case triggers, and lists specific trigger phrases. It uses third-person voice appropriately and covers both the 'what' and 'when' dimensions thoroughly. The niche focus on Firecrawl development setup makes it highly distinctive.
| 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 with vitest), with explicit trigger phrases listed. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms like 'firecrawl dev setup', 'firecrawl local development', 'firecrawl docker', 'firecrawl self-hosted dev', 'firecrawl test setup', plus contextual phrases like 'save credits' and 'vitest' that users would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a very specific niche (Firecrawl local development setup) with unique trigger terms. Unlikely to conflict with other skills due to the specificity of 'Firecrawl' combined with 'local development', 'Docker', and 'vitest'. | 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, unit testing, and integration testing. Its main weaknesses are that it's somewhat long for inline consumption (the full test files could be referenced separately) and lacks integrated validation checkpoints within the workflow steps. The error handling table is a nice touch but would be more effective if validation steps were woven into the workflow itself.
Suggestions
Add explicit validation checkpoints within the workflow steps (e.g., after Step 2, verify Docker health before proceeding; after Step 4, run tests and confirm they pass before moving to integration tests).
Consider moving the full test file contents to referenced files (e.g., 'See tests/scraper.test.ts for complete mock setup') and keeping only the key patterns inline to improve conciseness and progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary elements like the Overview paragraph explaining what the skill does (which is already clear from the title and structure), and the 'Output' section which restates what was already built. The code examples themselves are lean and useful, but the framing could be tighter. | 2 / 3 |
Actionability | Fully executable code throughout: complete docker-compose.yml, working TypeScript config, complete test files with vitest mocks, integration test setup, and package.json scripts. Everything is copy-paste ready with specific commands for verification. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (1-6) and logically ordered, but there's no explicit validation checkpoint after Docker setup beyond a simple curl check. Missing a feedback loop for common failure scenarios during setup — the error handling table exists but is disconnected from the workflow steps rather than integrated as checkpoints. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections, but it's quite long (~180 lines of content) with all code inline. The full test files and docker-compose could be referenced as separate files. The 'Next Steps' reference to firecrawl-sdk-patterns is good, but the main content could benefit from splitting detailed test examples into a separate file. | 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
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.