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".
80
77%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/firecrawl-pack/skills/firecrawl-multi-env-setup/SKILL.mdQuality
Discovery
89%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-structured skill description that clearly defines its niche (Firecrawl environment configuration) with explicit 'Use when' and 'Trigger with' clauses. The trigger terms are specific and natural. The main weakness is that the core capability statement could be more specific about the concrete actions performed (e.g., generating config files, setting API keys, defining rate limits).
Suggestions
Expand the first sentence to list more concrete actions, e.g., 'Generate environment-specific config files, set API keys and rate limits, manage credit budgets, and configure self-hosted Firecrawl instances across development, staging, and production environments.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Firecrawl multi-environment configuration) and some actions like 'setting up multi-environment scraping pipelines', 'managing credit budgets per env', and 'configuring self-hosted Firecrawl', but the core capability statement ('Configure Firecrawl across development, staging, and production environments') is somewhat general and doesn't list deeply specific concrete actions like template generation, config file creation, or credential management. | 2 / 3 |
Completeness | Clearly answers both 'what' (configure Firecrawl across dev/staging/prod, manage credit budgets, configure self-hosted instances) and 'when' (explicit 'Use when' clause with specific scenarios, plus a 'Trigger with phrases' section listing concrete trigger terms). | 3 / 3 |
Trigger Term Quality | Includes explicit trigger phrases like 'firecrawl environments', 'firecrawl staging', 'firecrawl dev prod', 'firecrawl environment setup', 'firecrawl config by env' which are natural terms a user would say. Also includes natural keywords like 'scraping pipelines', 'credit budgets', and 'self-hosted Firecrawl' that provide good coverage. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — focuses specifically on Firecrawl multi-environment configuration, which is a very narrow niche. The trigger terms are all Firecrawl-specific with environment qualifiers, making it unlikely to conflict with general scraping skills or other configuration skills. | 3 / 3 |
Total | 11 / 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, actionable skill with complete executable code for multi-environment Firecrawl setup. Its main strengths are concrete, copy-paste-ready configurations and a logical step sequence. Weaknesses include missing validation checkpoints between steps (especially important for Docker/infrastructure setup) and a somewhat monolithic structure that could benefit from splitting Docker and CI/CD configs into separate bundle files.
Suggestions
Add explicit validation checkpoints after Steps 2 and 3, e.g., 'Verify self-hosted is running: curl http://localhost:3002/health — expect 200 before proceeding' as a required gate, not a comment.
Split the docker-compose.dev.yml and .github/workflows/deploy.yml into actual bundle files and reference them from SKILL.md to improve progressive disclosure.
Remove the 'Check Active Configuration' example section — it's trivial code that Claude can generate without guidance and adds token overhead.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with good use of tables and code blocks, but includes some unnecessary elements like the 'Examples' section that just prints config (Claude knows how to do this), and the environment strategy table partially duplicates what's in the code. The error handling table adds value though. | 2 / 3 |
Actionability | Fully executable TypeScript code, complete docker-compose configuration, concrete bash commands, and specific environment variable templates. All code is copy-paste ready with real package names, ports, and configuration values. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (config → Docker → wrapper → env vars → CI/CD), but there are no validation checkpoints between steps. Step 2 has a commented-out health check rather than an explicit validation gate, and there's no feedback loop for verifying the full pipeline works end-to-end before moving to staging/production. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a table of contents-like flow, but it's a fairly long monolithic file (~150 lines of code) with no bundle files to offload detail. The Docker config and CI/CD pipeline could be separate referenced files. The 'Next Steps' reference to 'firecrawl-deploy-integration' is good but the main content could benefit from splitting. | 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.