CtrlK
BlogDocsLog inGet started
Tessl Logo

firecrawl-deploy-integration

Deploy Firecrawl integrations to Vercel, Cloud Run, and Docker platforms. Use when deploying Firecrawl-powered applications to production, configuring platform-specific secrets, or setting up self-hosted Firecrawl. Trigger with phrases like "deploy firecrawl", "firecrawl Vercel", "firecrawl production deploy", "firecrawl Cloud Run", "firecrawl Docker".

72

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

Highly actionable and token-efficient with executable examples across all platforms, but the multi-step deployment workflow lacks explicit validation checkpoints and the monolithic inline body underuses progressive disclosure.

Suggestions

Add an explicit validation checkpoint after each deployment step (e.g. 'Verify: gcloud run services describe ... --format=json | grep READY', or 'curl /api/scrape returns 200 before proceeding') so failures are caught before the next step.

Move the large docker-compose and webhook-handler blocks into reference files (e.g. references/self-hosted-compose.yml, references/webhook-route.ts) and link to them from SKILL.md, keeping the body as an overview.

Turn the Error Handling table into a validate→fix→retry loop referenced inline at the deployment steps where each issue is most likely to surface.

DimensionReasoningScore

Conciseness

Lean body of code blocks and a tight error table with no padding or explanation of concepts Claude already knows; every section earns its tokens.

3 / 3

Actionability

Fully executable, copy-paste-ready artifacts: Next.js route TS, docker-compose YAML, gcloud deploy command, webhook and health-check handlers with real values.

3 / 3

Workflow Clarity

Steps are sequenced (Step 1–6) and a health check exists, but there are no explicit validate-then-proceed checkpoints or feedback loops for a production deployment, capping clarity at 2 per the destructive/risky-operation guideline.

2 / 3

Progressive Disclosure

Well-organized into sections but ~200 lines are entirely inline with no bundle reference files; substantial blocks (docker-compose, webhook handler) that could be offloaded stay in SKILL.md, so structure is present but content is not split.

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

A strong description: concrete multi-action capability statement, explicit 'Use when' trigger guidance, natural trigger phrases, and a distinct niche. Third-person voice is maintained throughout.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Deploy Firecrawl integrations to Vercel, Cloud Run, and Docker platforms', 'configuring platform-specific secrets', 'setting up self-hosted Firecrawl' — across three named platforms, matching the multi-action anchor.

3 / 3

Completeness

Explicitly answers what ('Deploy Firecrawl integrations to Vercel, Cloud Run, and Docker platforms') and when ('Use when deploying Firecrawl-powered applications to production, configuring platform-specific secrets, or setting up self-hosted Firecrawl'), with an explicit 'Use when' clause.

3 / 3

Trigger Term Quality

Provides natural phrases a user would say — 'deploy firecrawl', 'firecrawl Vercel', 'firecrawl production deploy', 'firecrawl Cloud Run', 'firecrawl Docker' — with good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche — Firecrawl deployments on specific platforms — with distinct 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.