CtrlK
BlogDocsLog inGet started
Tessl Logo

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".

68

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is highly actionable with complete executable examples and clean section organization, but it is somewhat verbose due to inline full-file listings and lacks explicit validation checkpoints in its multi-step CI workflow.

Suggestions

Add validation checkpoints between steps, e.g. confirm 'gh secret list' shows FIRECRAWL_API_KEY and verify the workflow file passes YAML lint before moving to test authoring.

Move the full integration test and GitHub Actions workflow files into a references/ or scripts/ bundle with one-line pointers, keeping SKILL.md lean.

Trim inline full-file code blocks to the minimal runnable snippet per step to reduce token cost while preserving actionability.

DimensionReasoningScore

Conciseness

Mostly efficient with executable code blocks and a lean error-handling table, but the full integration test file and both GitHub Actions workflows are embedded inline rather than referenced, adding length Claude could do without.

2 / 3

Actionability

Provides copy-paste ready bash, YAML, and TypeScript snippets with real commands (gh secret set, npm test, firecrawl.scrapeUrl) and concrete assertions.

3 / 3

Workflow Clarity

Steps are numbered and sequenced (secrets, workflow, tests, mock tests, credit-aware CI), but there is no validation checkpoint confirming secrets are set or workflow runs before proceeding, and batch/CI operations lack an explicit validate-fix-retry loop.

2 / 3

Progressive Disclosure

No bundle files exist and none are needed; the single-file skill is well organized into clear sections (Overview, Prerequisites, Steps 1-5, Error Handling, Resources, Next Steps) per the simple-skill guidance.

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

The description is specific, complete, and distinct, with both explicit capability statements and natural trigger phrases. It uses appropriate third-person voice throughout and clearly signals when to use the skill.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: 'Configure Firecrawl CI/CD integration with GitHub Actions and automated scraping tests' and 'setting up automated testing of Firecrawl integrations, configuring CI pipelines, or validating scraping behavior in pull requests'.

3 / 3

Completeness

Explicitly answers what (configure Firecrawl CI/CD with GitHub Actions and scraping tests) and when ('Use when setting up automated testing...') with explicit trigger guidance.

3 / 3

Trigger Term Quality

Provides five natural trigger phrases ('firecrawl CI', 'firecrawl GitHub Actions', 'firecrawl automated tests', 'CI firecrawl', 'test firecrawl in CI') that a user would realistically say.

3 / 3

Distinctiveness Conflict Risk

Clear narrow niche (Firecrawl-specific CI/CD testing) with distinct Firecrawl-branded triggers unlikely to conflict with other 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.