firecrawl-core-workflow-a
Execute Firecrawl primary workflow: scrape and crawl websites into LLM-ready markdown. Use when scraping single pages, crawling entire sites, or building content ingestion pipelines with Firecrawl's scrapeUrl and crawlUrl methods. Trigger with phrases like "firecrawl scrape", "firecrawl crawl site", "scrape page to markdown", "crawl documentation".
71
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
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 a strong skill description that clearly identifies the tool (Firecrawl), lists concrete actions (scrape, crawl, build pipelines), specifies methods (scrapeUrl, crawlUrl), and provides explicit trigger guidance with natural user phrases. It uses proper third-person voice throughout and is concise without being vague. The description would perform well in a large skill library for accurate selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: scrape websites, crawl websites, convert to LLM-ready markdown, build content ingestion pipelines. Also names specific methods (scrapeUrl, crawlUrl). | 3 / 3 |
Completeness | Clearly answers both 'what' (scrape and crawl websites into LLM-ready markdown using Firecrawl's scrapeUrl and crawlUrl methods) and 'when' (explicit 'Use when' clause with specific scenarios and a 'Trigger with phrases' section). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'firecrawl scrape', 'firecrawl crawl site', 'scrape page to markdown', 'crawl documentation', plus method names like scrapeUrl and crawlUrl that technical users would reference. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific tool name 'Firecrawl', specific method names (scrapeUrl, crawlUrl), and the niche of converting web content to LLM-ready markdown. Unlikely to conflict with generic web scraping or other crawling skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%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 executable code examples covering the full Firecrawl scrape/crawl workflow. The step-by-step progression from single-page scrape through async crawling to result processing is well-structured with good error handling guidance. Minor improvements could be made in conciseness by trimming the overview/prerequisites and in progressive disclosure by splitting advanced examples into a separate file.
Suggestions
Remove or condense the Overview and Prerequisites sections — the description metadata already covers the overview, and Claude can infer prerequisites from the code imports.
Consider moving the Examples section (multiple formats, webhook) into a separate EXAMPLES.md to keep the main skill focused on the core 4-step workflow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with executable code examples, but includes some unnecessary elements like the Overview section restating the description, and the Prerequisites section listing things Claude would know to check. The inline comments are helpful but some are slightly verbose. | 2 / 3 |
Actionability | Fully executable TypeScript code throughout with copy-paste ready examples. Every step includes concrete, runnable code with specific API methods, options, and error handling patterns. The error handling table provides specific causes and solutions. | 3 / 3 |
Workflow Clarity | Clear 4-step sequential workflow progressing from simple scrape to multi-page crawl to async jobs to processing results. The async crawl includes an explicit polling loop with backoff and status checking, and the error handling table serves as a validation/troubleshooting checkpoint. The progression is logical and well-structured. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and a reference to workflow-b for next steps, but the skill is fairly long (~120 lines of content) with the Examples section adding additional patterns that could potentially be in a separate file. The Resources section links to external docs which is good, but there are no bundle files to offload advanced content to. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%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 | |
- Commit
a04d1a2
- 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.