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".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

85%

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

A concise, highly actionable skill body with executable code throughout and well-structured sections. The main gap is in explicit validation checkpoints and feedback loops for the Docker bring-up and test workflows.

Suggestions

Add an explicit validation checkpoint after `docker compose up -d` — e.g. wait for `/health` to return success before proceeding to Step 3, and instruct to re-run or check `docker compose logs` on failure.

Add a feedback loop for the integration tests: if `test:integration` fails with ECONNREFUSED/timeout, loop back to verify the container is healthy and the port is free (cross-link the Error Handling table as the recovery path).

The health check uses `curl ... | jq .` but never asserts the expected output; state the success condition (e.g. `jq -e .status` or an expected HTTP 200) so the verify step is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — it jumps straight into executable docker-compose, config, and test snippets without explaining what Docker, vitest, or Firecrawl are, so every token earns its place.	3 / 3
Actionability	All examples are executable and copy-paste ready: a complete docker-compose.yml, a getFirecrawl() config function, vitest unit and integration test files, npm scripts, and a runnable `npx tsx scripts/dev-scrape.ts` command.	3 / 3
Workflow Clarity	Steps 1-6 are clearly sequenced and the Error Handling table plus `curl ... /health` verification help, but operations like `docker compose up -d` lack an explicit validate-then-proceed checkpoint, and there is no feedback loop after the health check.	2 / 3
Progressive Disclosure	Content is well-organized into clearly signaled sections (Overview, Prerequisites, Steps 1-6, Output, Error Handling, Examples, Resources, Next Steps) with a one-level-deep pointer to `firecrawl-sdk-patterns`; no nested references and nothing that should be separated is left inline.	3 / 3
	Total	11 / 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.

A strong description that concretely states capabilities, gives an explicit 'Use when' clause, and lists natural trigger phrases. It is written in third person and clearly scoped to the Firecrawl local-dev niche.

Dimension	Reasoning	Score
Specificity	Names concrete actions across the domain: 'self-hosted Docker', 'mocking', and 'testing', plus specific activities like 'running Firecrawl locally to save credits' and 'configuring test workflows with vitest'.	3 / 3
Completeness	Clearly states both what ('Configure Firecrawl local development with self-hosted Docker, mocking, and testing') and when ('Use when setting up a development environment... or configuring test workflows with vitest'), with an explicit trigger clause.	3 / 3
Trigger Term Quality	Provides an explicit, natural set of trigger phrases users would say — 'firecrawl dev setup', 'firecrawl local development', 'firecrawl docker', 'firecrawl self-hosted dev', 'firecrawl test setup' — covering common variations.	3 / 3
Distinctiveness Conflict Risk	The Firecrawl-specific niche and scoped trigger phrases make it unlikely to fire for unrelated skills; the dev-loop framing is clearly distinguishable from a general Firecrawl or testing skill.	3 / 3
	Total	12 / 12 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 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
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	13 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 6e3a65f

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.