firecrawl-ci-integration

Configure Firecrawl CI/CD integration with GitHub Actions and automated scraping tests. Use when setting up automated testing of Firecrawl integrations, configuring CI pipelines, or validating scraping behavior in pull requests. Trigger with phrases like "firecrawl CI", "firecrawl GitHub Actions", "firecrawl automated tests", "CI firecrawl", "test firecrawl in CI".

Quality

77%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/saas-packs/firecrawl-pack/skills/firecrawl-ci-integration/SKILL.md

Quality

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 description with strong completeness and distinctiveness. It clearly states what the skill does and when to use it, and includes explicit trigger phrases. The main weakness is that the 'what' portion could be more specific about the concrete actions performed (e.g., generating workflow YAML files, writing test assertions, configuring environment variables).

Suggestions

Add more specific concrete actions to the capability list, e.g., 'generates GitHub Actions workflow YAML, writes scraping test assertions, configures API keys as secrets' to improve specificity.

Dimension	Reasoning	Score
Specificity	Names the domain (Firecrawl CI/CD) and some actions (configure integration, automated scraping tests), but doesn't list multiple concrete actions in detail—e.g., it doesn't specify what configuration steps, what kinds of tests, or what validation outputs are produced.	2 / 3
Completeness	Clearly answers both 'what' (configure Firecrawl CI/CD integration with GitHub Actions and automated scraping tests) and 'when' (setting up automated testing, configuring CI pipelines, validating scraping in PRs), with explicit trigger phrases.	3 / 3
Trigger Term Quality	Includes a strong set of natural trigger phrases: 'firecrawl CI', 'firecrawl GitHub Actions', 'firecrawl automated tests', 'CI firecrawl', 'test firecrawl in CI'. These cover realistic variations a user would say, including reordered terms.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive—the combination of Firecrawl + CI/CD + GitHub Actions is a very specific niche. It's unlikely to conflict with general CI skills or general Firecrawl usage skills due to the explicit scoping to CI/CD integration and automated testing.	3 / 3
	Total	11 / 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, highly actionable skill with complete, executable code examples covering the full CI/CD setup for Firecrawl. Its main weaknesses are the lack of explicit validation/verification checkpoints in the workflow (e.g., verifying secrets are set, confirming workflow runs pass) and the monolithic structure that could benefit from splitting detailed test files into separate bundle references. The content is mostly concise but has room for tightening.

Suggestions

Add explicit validation checkpoints after key steps—e.g., 'Verify secret is set: `gh secret list | grep FIRECRAWL`' after Step 1, and guidance on checking workflow run status after Step 2.

Extract the full integration and unit test files into bundle files (e.g., `tests/firecrawl.integration.test.ts`) and reference them from SKILL.md, keeping only key snippets inline.

Add a brief feedback loop for workflow failures—e.g., 'If the workflow fails: check Actions tab → read error log → common fixes in Error Handling table below.'

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient with executable code examples, but includes some unnecessary sections like 'Prerequisites' listing obvious requirements and the 'Overview' paragraph that restates the title. The error handling table and resources section add value but the overall content could be tightened—e.g., the mock test example is quite long and includes an import of a hypothetical `processPage` function without context.	2 / 3
Actionability	Excellent actionability throughout—every step includes fully executable, copy-paste ready code: bash commands for secrets, complete YAML workflow files, full TypeScript test files with imports and assertions, and a credit-aware CI configuration. The code is concrete and specific, not pseudocode.	3 / 3
Workflow Clarity	Steps are clearly numbered and sequenced (configure secrets → workflow → integration tests → unit tests → credit-aware CI), but there are no explicit validation checkpoints or feedback loops. There's no step to verify the secrets were set correctly, no guidance on validating the workflow runs successfully, and no 'if this fails, do X' recovery steps within the workflow itself—only a static error table at the end.	2 / 3
Progressive Disclosure	The content is well-structured with clear headers and a logical progression, but it's quite long (~150 lines of code examples) with no bundle files to offload detail into. The full integration test suite and mock test suite could be separate reference files. The single reference to 'firecrawl-deploy-integration' in Next Steps is helpful but the main content is monolithic.	2 / 3
	Total	9 / 12 Passed

Validation

81%

Warnings & errors only

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

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 3a2d27d

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.