CtrlK
BlogDocsLog inGet started
Tessl Logo

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

69

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

72%Weight 40%Scale 1-3

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

The content is highly actionable with complete executable code, but slightly padded in its overview/strategy and missing explicit validation checkpoints for its destructive and credit-bearing operations.

Suggestions

Tighten or trim the Overview rationale and the Environment Strategy table since the code blocks already encode the same per-environment configuration.

Add explicit validation/verification gates to the CI/CD deploy and the production crawl steps (e.g., a verify-balance check and a deploy smoke test) to close the workflow-clarity feedback loop for cost-bearing operations.

Consider moving the error-handling table closer to its relevant step or framing it as a validate→fix→retry loop for batch crawl failures.

DimensionReasoningScore

Conciseness

Mostly efficient with executable blocks and tables, but the Overview rationale paragraph and the Environment Strategy table (which duplicates the code config below) add unnecessary context that could be tightened.

2 / 3

Actionability

Provides fully executable, copy-paste-ready TypeScript config, docker-compose YAML, bash commands, env-var examples, and a CI/CD workflow with concrete specifics.

3 / 3

Workflow Clarity

Steps are clearly sequenced (Step 1–5), but cost-bearing/batch operations (production deploy, credit-consuming crawls) lack explicit validation gates and feedback loops beyond an Error Handling table, capping clarity at 2 per the destructive/batch guideline.

2 / 3

Progressive Disclosure

With no bundle files present, the self-contained body is well-organized into clear sections (Overview, Strategy, Steps, Error Handling, Examples, Resources, Next Steps) with only one-level-deep external pointers, satisfying the simple-skill allowance.

3 / 3

Total

10

/

12

Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, complete, and well-triggered, covering concrete per-environment actions with natural user phrasings and an explicit Use-when clause. It is distinct from neighboring skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Configure Firecrawl across development, staging, and production environments", "managing credit budgets per env", and "configuring self-hosted Firecrawl for development" — matching the anchor for several specific concrete actions.

3 / 3

Completeness

Explicitly answers both what ("Configure Firecrawl across ... environments") and when ("Use when setting up multi-environment scraping pipelines ..."), satisfying the explicit-trigger requirement.

3 / 3

Trigger Term Quality

Provides natural user-facing phrases ("firecrawl environments", "firecrawl staging", "firecrawl dev prod", "firecrawl environment setup", "firecrawl config by env") with good coverage of variations a user would actually say.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (Firecrawl multi-environment setup) with environment-scoped triggers unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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