firecrawl-ci-integration
Configure FireCrawl CI/CD integration with GitHub Actions and testing. Use when setting up automated testing, configuring CI pipelines, or integrating FireCrawl tests into your build process. Trigger with phrases like "firecrawl CI", "firecrawl GitHub Actions", "firecrawl automated tests", "CI firecrawl".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill firecrawl-ci-integration88
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
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 with excellent trigger term coverage and clear 'Use when' guidance. The main weakness is that the capabilities could be more specific about what concrete actions the skill enables (e.g., 'create workflow files', 'configure test runners', 'set up secrets'). Overall, it should perform well in skill selection scenarios.
Suggestions
Add more specific concrete actions like 'create GitHub workflow files', 'configure test runners', or 'set up environment secrets' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (FireCrawl CI/CD) and some actions (configure integration, setting up automated testing, configuring CI pipelines), but doesn't list comprehensive concrete actions like specific configuration steps or what the integration actually does. | 2 / 3 |
Completeness | Clearly answers both what (configure FireCrawl CI/CD integration with GitHub Actions and testing) and when (setting up automated testing, configuring CI pipelines, integrating tests into build process) with explicit 'Use when' and 'Trigger with' clauses. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'firecrawl CI', 'firecrawl GitHub Actions', 'firecrawl automated tests', 'CI firecrawl'. Also includes variations like 'automated testing', 'CI pipelines', and 'build process'. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche combining FireCrawl + CI/CD + GitHub Actions. The explicit trigger terms are highly distinctive and unlikely to conflict with generic CI/CD skills or other FireCrawl skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill with excellent conciseness and fully executable code examples. The main weakness is the lack of explicit validation steps in the workflow - there's no checkpoint to verify the GitHub Actions workflow is correctly configured before relying on it, and no feedback loop for troubleshooting initial setup failures.
Suggestions
Add a validation step after creating the workflow, such as 'Step 4: Verify Setup - Push a test commit and check Actions tab for successful run. If failed, review logs and check secret configuration.'
Include a troubleshooting feedback loop: 'If workflow fails on first run: 1) Check Actions logs, 2) Verify secret is set correctly with `gh secret list`, 3) Test locally first with `FIRECRAWL_API_KEY=xxx npm run test:integration`'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing only necessary configuration and code without explaining what GitHub Actions or CI/CD is. Every section serves a clear purpose with no padding. | 3 / 3 |
Actionability | Provides fully executable YAML workflows, bash commands, and TypeScript test code that are copy-paste ready. Includes specific file paths and complete configurations. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, but lacks explicit validation checkpoints. No feedback loop for verifying the workflow works before merging, and no guidance on what to do if the initial setup fails. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections (Overview, Prerequisites, Instructions, Examples, Error Handling). References external resources appropriately and points to related skill for deployment patterns without deep nesting. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
68%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_voice | 'description' should use third person voice; found second person: 'your ' | Warning |
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 | 11 / 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.