firecrawl-scraper
Convert websites into LLM-ready data with Firecrawl API. Features: scrape, crawl, map, search, extract, agent (autonomous), batch operations, and change tracking. Handles JavaScript, anti-bot bypass, PDF/DOCX parsing, and branding extraction. Prevents 10 documented errors. Use when: scraping websites, crawling sites, web search + scrape, autonomous data gathering, monitoring content changes, extracting brand/design systems, or troubleshooting content not loading, JavaScript rendering, bot detection, v2 migration, job status errors, DNS resolution, or stealth mode pricing.
Install with Tessl CLI
npx tessl i github:jezweb/claude-skills --skill firecrawl-scraper86
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
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 an excellent skill description that comprehensively covers the Firecrawl API's capabilities with specific actions, includes a well-structured 'Use when:' clause with diverse trigger scenarios, and maintains clear distinctiveness through domain-specific terminology. The description effectively balances technical specificity with natural language triggers users would actually use.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: scrape, crawl, map, search, extract, agent (autonomous), batch operations, change tracking, plus technical capabilities like JavaScript handling, anti-bot bypass, PDF/DOCX parsing, and branding extraction. | 3 / 3 |
Completeness | Clearly answers both what (Firecrawl API features and capabilities) AND when with an explicit 'Use when:' clause covering multiple trigger scenarios including both common use cases and troubleshooting situations. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'scraping websites', 'crawling sites', 'web search', 'content changes', 'JavaScript rendering', 'bot detection', plus specific technical terms like 'Firecrawl' and error scenarios users might mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche around Firecrawl API specifically, web scraping/crawling domain, and unique triggers like 'v2 migration', 'stealth mode pricing', and specific error troubleshooting that wouldn't overlap with generic web or document 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 highly actionable and well-structured API reference skill with excellent executable code examples and comprehensive error prevention guidance. The main weaknesses are verbosity (the 'What is Firecrawl?' section and some explanatory text are unnecessary for Claude) and the monolithic structure that could benefit from splitting detailed content like Known Issues into separate files.
Suggestions
Remove or drastically shorten the 'What is Firecrawl?' section - Claude doesn't need explanations of what JavaScript rendering or anti-bot bypass means
Split the Known Issues Prevention section (10 issues, ~200 lines) into a separate KNOWN_ISSUES.md file with a brief summary and link in the main skill
Consider moving the detailed Cloudflare Workers integration and Rate Limits sections to separate reference files to reduce main skill length
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary explanations (e.g., 'What is Firecrawl?' section explaining concepts Claude knows). The tables and endpoint overviews add value, but some sections could be tightened. | 2 / 3 |
Actionability | Excellent executable code examples throughout in both Python and TypeScript. Every endpoint has copy-paste ready code with realistic parameters and clear output expectations. | 3 / 3 |
Workflow Clarity | Clear sequences for async operations with explicit validation (check status, retry logic). The Known Issues section provides excellent error recovery patterns with specific code for handling race conditions and failures. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but this is a monolithic 600+ line file. Advanced topics like Known Issues Prevention could be split into separate reference files. No external file references for detailed content. | 2 / 3 |
Total | 10 / 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 |
|---|---|---|
skill_md_line_count | SKILL.md is long (937 lines); consider splitting into references/ and linking | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | 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.