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".
84
82%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
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.
This is a strong skill description that clearly defines its scope, provides explicit trigger guidance, and uses natural keywords users would employ. It covers the what, when, and how-to-trigger comprehensively while maintaining a distinct niche that minimizes conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: deploying to Vercel, Cloud Run, and Docker platforms; configuring platform-specific secrets; setting up self-hosted Firecrawl. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (deploy Firecrawl integrations to Vercel, Cloud Run, Docker; configure secrets; set up self-hosted Firecrawl) and 'when' (explicit 'Use when' clause plus specific trigger phrases). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'deploy firecrawl', 'firecrawl Vercel', 'firecrawl production deploy', 'firecrawl Cloud Run', 'firecrawl Docker'. These are phrases users would naturally say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Firecrawl-specific deployment across named platforms. The combination of 'Firecrawl' with specific deployment targets (Vercel, Cloud Run, Docker) makes it very unlikely to conflict with generic deployment or generic Firecrawl skills. | 3 / 3 |
Total | 12 / 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 deployment skill with excellent executable code examples covering multiple platforms. Its main weaknesses are the lack of validation/verification checkpoints in the deployment workflow (important for production deployments) and the monolithic structure that forces all platform-specific details inline rather than splitting them into separate files. The content is mostly efficient but could trim some explanatory text.
Suggestions
Add explicit validation steps after each deployment action (e.g., 'Verify secret: `vercel env ls production | grep FIRECRAWL`', 'Test endpoint: `curl -X POST https://your-app.vercel.app/api/scrape`') to create feedback loops for these production-impacting operations.
Split platform-specific deployment details (Vercel, Cloud Run, Docker) into separate referenced files, keeping SKILL.md as a concise overview with quick-start commands and links to each platform's full guide.
Remove the Overview paragraph and Prerequisites section—Claude already knows what API keys and CLIs are. Jump straight into the deployment instructions.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient with code-forward examples, but includes some unnecessary elements like the Prerequisites section (Claude knows what an API key is) and the 'Overview' paragraph that restates the skill description. The error handling table is useful but some entries are somewhat obvious. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready code for every deployment target: complete TypeScript API routes, Docker Compose configuration, gcloud CLI commands, and Vercel commands. Code examples are concrete with real file paths and realistic configurations. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced and numbered, but there are no validation checkpoints between steps. For deployment operations (which are destructive/production-impacting), there should be explicit verification steps like 'verify the secret was set correctly', 'test the endpoint after deploy', or 'check container health before proceeding'. The health check is provided but not integrated into the workflow as a validation gate. | 2 / 3 |
Progressive Disclosure | Has a Resources section with external links and a Next Steps reference to another skill, which is good. However, the skill is quite long with all platform-specific code inline. The Vercel, Cloud Run, and Docker sections could be split into separate reference files with the SKILL.md providing a concise overview and links, since a user typically only needs one platform. | 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
70e9fa4
- 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.