firecrawl-hello-world
Create a minimal working Firecrawl example that scrapes a page to markdown. Use when starting a new Firecrawl integration, testing your setup, or learning the scrape/crawl/map/extract API surface. Trigger with phrases like "firecrawl hello world", "firecrawl example", "firecrawl quick start", "simple firecrawl code".
84
82%
Does it follow best practices?
Impact
Pending
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 a specific tool (Firecrawl), a concrete action (creating a minimal scraping example), and explicit trigger conditions. It uses third person voice, provides natural user phrases, and occupies a clear niche that would be easy to distinguish from other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists concrete actions: 'Create a minimal working Firecrawl example', 'scrapes a page to markdown', and references the specific 'scrape/crawl/map/extract API surface'. These are specific, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (create a minimal Firecrawl example that scrapes a page to markdown) and 'when' (starting a new integration, testing setup, learning the API surface) with explicit trigger phrases. | 3 / 3 |
Trigger Term Quality | Includes excellent natural trigger phrases users would actually say: 'firecrawl hello world', 'firecrawl example', 'firecrawl quick start', 'simple firecrawl code'. Also mentions 'new Firecrawl integration', 'testing your setup', and API surface terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — 'Firecrawl' is a specific tool, and the description is narrowly scoped to a hello-world/quickstart use case. Unlikely to conflict with other skills unless there are multiple Firecrawl-related skills, and even then the 'minimal example' framing distinguishes it. | 3 / 3 |
Total | 12 / 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, actionable skill with excellent executable code examples covering all four Firecrawl endpoints. Its main weaknesses are moderate verbosity (redundant Output section, explanatory comments, dual-language examples inline) and lack of validation checkpoints between steps. Trimming the inline content and adding a simple verification step (e.g., confirming API key validity) would elevate it.
Suggestions
Remove the 'Output' section — it merely restates what the code snippets already demonstrate, wasting tokens.
Move the Python example and batch scrape example to a separate EXAMPLES.md file and reference it, keeping SKILL.md focused on the core TypeScript hello-world path.
Add a brief validation step after Step 1 (e.g., 'Verify result.success is true before proceeding') to establish a feedback loop pattern.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary elements: the Output section restates what the code already shows, comments in code snippets explain things Claude already knows (e.g., 'follows links, respects robots.txt'), and the Python example adds a second language variant that inflates the content. The error handling table is useful but some entries are generic troubleshooting Claude would know. | 2 / 3 |
Actionability | All four core endpoints have fully executable, copy-paste-ready TypeScript snippets with real URLs, proper imports, and concrete output logging. The Python example and batch scrape example are also complete and runnable. The error handling table provides specific solutions for specific errors. | 3 / 3 |
Workflow Clarity | The steps are clearly sequenced and labeled, but they are independent standalone snippets rather than a true multi-step workflow. There are no validation checkpoints — for instance, no guidance on verifying the API key works before proceeding, no check that scrape succeeded before crawling, and no feedback loop for handling failures during execution. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a reference to 'firecrawl-local-dev-loop' for next steps, plus external documentation links. However, the skill is quite long (~120 lines of content) and could benefit from splitting the additional examples (Python, batch scrape) into a separate file. The Resources section is good but the main body carries more inline content than ideal for an overview. | 2 / 3 |
Total | 9 / 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
3a2d27d
- 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.