CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

seo-firecrawl

Full-site crawling, scraping, and site mapping via Firecrawl MCP. Use when user says "crawl site", "map site", "full crawl", "find all pages", "broken links", "site structure", "discover pages", "JS rendering", or needs site-wide analysis.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a well-structured, highly actionable reference for orchestrating Firecrawl MCP tools, with strong parameter documentation, cost awareness, and error handling. Its weaknesses are mild: some redundancy between usage-pattern and cross-skill sections, no result-verification step for batch crawls, and an inlined parameter reference that could be split out.

DimensionReasoningScore

Conciseness

The body is dense and reference-style (tables, parameter lists, decision matrices) with essentially no explanation of concepts Claude already knows. It is not anchor 5 because the per-command "SEO Usage Patterns" lists repeat material that reappears in "Cross-Skill Integration" (e.g., broken link detection under crawl and again under seo-technical), which could be trimmed.

4 / 5

Actionability

For an instruction-only (MCP orchestration) skill, guidance is fully actionable: exact MCP tool names, complete parameter specs with types/defaults/examples (e.g., `includePaths`: `["/blog/*"]`), a scrape-vs-fetch decision table, an orchestration example with real call syntax (`firecrawl_crawl(url, limit=50)`), and concrete error resolutions. This matches the anchor 5 standard of copy-paste-ready coverage of common cases.

5 / 5

Workflow Clarity

Sequences are clear and most checkpoints are present: a pre-flight MCP availability check, a credit-usage checkpoint before large crawls, and an error table with recovery actions (429 → wait 60s, reduce concurrency). It is not anchor 5 because the batch crawl workflow lacks a verification step on results (e.g., confirming pages returned before feeding subagents), though validation is present so the batch-cap at 3 does not apply.

4 / 5

Progressive Disclosure

The single file is well organized with a Quick Reference table up front and clear section headers, and there are no bundle files to reference (so no buried or nested references). It is not anchor 5 because roughly a hundred lines of per-command parameter reference are inlined in SKILL.md rather than split into a one-level-deep reference file, a minor organization gap.

4 / 5

Total

17

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that clearly states capabilities and provides an explicit, well-populated trigger list in the recommended 'Use when...' form. The main gaps are the omission of the search capability and a few generic trigger phrases that could collide with related SEO skills.

DimensionReasoningScore

Specificity

"Full-site crawling, scraping, and site mapping via Firecrawl MCP" names three concrete, specific actions with a clear domain. It falls short of anchor 5 because the body documents a fourth capability (site-scoped search) that the description omits, a minor coverage gap.

4 / 5

Completeness

It explicitly answers both questions: what it does ("Full-site crawling, scraping, and site mapping via Firecrawl MCP") and when to use it ("Use when user says ... or needs site-wide analysis") with concrete trigger phrases. This is a direct match to the anchor 5 example pattern; anchor 4's "'when' could be more explicit" does not apply since the triggers are explicit and enumerated.

5 / 5

Trigger Term Quality

The description quotes many natural phrases users would say ("crawl site", "map site", "full crawl", "find all pages", "broken links", "site structure", "discover pages", "JS rendering", "site-wide analysis"). It is not anchor 5 because common variants tied to its own scrape command (e.g., "scrape this page", "get page content") are missing.

4 / 5

Distinctiveness Conflict Risk

The Firecrawl/web-crawling niche is clear and mostly distinct, but triggers like "find all pages", "broken links", and "discover pages" are generic enough to overlap with sibling SEO skills (sitemap, technical audit) referenced in the body. Minor overlap risk matches anchor 4 rather than anchor 5's minimal conflict risk.

4 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

AgriciDaniel/claude-seo

Path

extensions/firecrawl/skills/seo-firecrawl/SKILL.md

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.