firecrawl-multi-env-setup

Configure Firecrawl across development, staging, and production environments. Use when setting up multi-environment scraping pipelines, managing credit budgets per env, or configuring self-hosted Firecrawl for development. Trigger with phrases like "firecrawl environments", "firecrawl staging", "firecrawl dev prod", "firecrawl environment setup", "firecrawl config by env".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

87%

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

A dense, highly actionable config skill with executable code throughout and clean sectioning. Its weakest point is workflow_clarity: validation is present but light/implicit and the credit-budget batch operations lack an enforced verify checkpoint.

Suggestions

Turn Step 2's `# Verify: curl http://localhost:3002/health` into an explicit checkpoint — show the expected output and a retry path (e.g., on failure run `docker compose -f docker-compose.dev.yml logs firecrawl` then restart).

Add a credit-budget verification step before running crawls in staging/production (e.g., check remaining credits or assert the per-env limit is enforced) with a feedback loop if the budget is exhausted.

Consider moving the full inline config module and CI/CD workflow into files under `references/` (signaled from SKILL.md) to keep the overview lean given the body is ~200 lines.

Dimension	Reasoning	Score
Conciseness	Lean body of executable TypeScript/YAML/bash with no padding about what Firecrawl or Docker is; the only prose (Overview) conveys the non-obvious credit-pricing rationale that justifies environment separation.	3 / 3
Actionability	Fully executable, copy-paste-ready artifacts: a typed config module, docker-compose.dev.yml, a credit-safe scrape/crawl wrapper, env var listings, and a CI/CD workflow.	3 / 3
Workflow Clarity	Steps 1–5 are clearly sequenced and Step 2 includes a `# Verify: curl ...` health check, but validation checkpoints are mostly implicit (a comment) with no explicit validate→fix→retry loop, and the batch/credit-risky crawl operations lack a credit-budget verification gate.	2 / 3
Progressive Disclosure	Well-organized into clear sections (Overview, Environment Strategy, Instructions, Error Handling, Examples, Resources, Next Steps) with one-level-deep external links in Resources; no nested references and no monolithic wall of text, appropriate for a self-contained skill with no bundle files.	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, third-person description that names concrete capabilities, supplies natural trigger phrases, and explicitly covers both what the skill does and when to use it. The only minor issue is awkward multi-line formatting with stray blank lines mid-sentence, which does not affect substance.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Configure Firecrawl across development, staging, and production environments", "managing credit budgets per env", "configuring self-hosted Firecrawl for development" — rather than vague language.	3 / 3
Completeness	Answers both what ("Configure Firecrawl across ... environments") and when ("Use when setting up multi-environment scraping pipelines, managing credit budgets per env, or configuring self-hosted Firecrawl") with an explicit "Trigger with phrases like" clause.	3 / 3
Trigger Term Quality	Provides natural trigger phrases users would say: "firecrawl environments", "firecrawl staging", "firecrawl dev prod", "firecrawl environment setup", "firecrawl config by env".	3 / 3
Distinctiveness Conflict Risk	Firecrawl-specific multi-environment niche with distinct triggers (staging, dev/prod, config by env) makes it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

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 — 14 / 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

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 50ab626

Reviewed: about 12 hours 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.