firecrawl-deploy-integration
Deploy FireCrawl integrations to Vercel, Fly.io, and Cloud Run platforms. Use when deploying FireCrawl-powered applications to production, configuring platform-specific secrets, or setting up deployment pipelines. Trigger with phrases like "deploy firecrawl", "firecrawl Vercel", "firecrawl production deploy", "firecrawl Cloud Run", "firecrawl Fly.io".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill firecrawl-deploy-integration81
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 an excellent skill description that hits all the marks. It provides specific actions, names concrete platforms, includes explicit 'Use when' guidance, and provides natural trigger phrases. The description is concise yet comprehensive, clearly distinguishing this skill from both generic deployment skills and other FireCrawl-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Deploy FireCrawl integrations', names three specific platforms (Vercel, Fly.io, Cloud Run), mentions 'configuring platform-specific secrets' and 'setting up deployment pipelines'. | 3 / 3 |
Completeness | Clearly answers both what (deploy FireCrawl integrations to specific platforms, configure secrets, set up pipelines) AND when (explicit 'Use when...' clause plus 'Trigger with phrases like...' providing concrete trigger guidance). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'deploy firecrawl', 'firecrawl Vercel', 'firecrawl production deploy', 'firecrawl Cloud Run', 'firecrawl Fly.io'. These are realistic phrases a user would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: specifically FireCrawl + deployment to named platforms. The combination of 'FireCrawl' with specific cloud platforms (Vercel, Fly.io, Cloud Run) creates a unique trigger profile unlikely to conflict with generic deployment or web scraping 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 skill provides solid, actionable deployment guidance for three platforms with executable code examples. However, it's somewhat verbose with generic patterns Claude already knows (health checks, config patterns), and lacks explicit validation steps between deployment stages. The content would benefit from tighter focus on FireCrawl-specific concerns and clearer verification checkpoints.
Suggestions
Add explicit validation steps after each deployment phase (e.g., 'Verify secret was set: fly secrets list | grep FIRECRAWL', 'Confirm deployment: curl https://your-app.fly.dev/api/health')
Remove or minimize generic patterns like the health check endpoint and environment configuration that Claude can generate without guidance
Consider splitting platform-specific guides into separate files (VERCEL.md, FLY.md, CLOUDRUN.md) with SKILL.md as a brief overview pointing to each
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is mostly efficient with good code examples, but includes some unnecessary sections like the generic health check endpoint and environment configuration pattern that Claude could generate without guidance. The prerequisites section states obvious requirements. | 2 / 3 |
Actionability | Provides fully executable code and commands for all three platforms - bash commands, configuration files, TypeScript code, and Dockerfiles are all copy-paste ready with specific examples. | 3 / 3 |
Workflow Clarity | Steps are listed in the Instructions section but lack validation checkpoints. No explicit verification between steps (e.g., confirming secrets were set correctly before deploying, or validating the deployment succeeded before checking health). | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections per platform, but the skill is quite long (~180 lines) and could benefit from splitting platform-specific guides into separate files. The inline configuration examples could be referenced externally. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
- 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.