firecrawl-install-auth
Install and configure Firecrawl SDK authentication for web scraping. Use when setting up a new Firecrawl integration, configuring API keys, or initializing Firecrawl in your project. Trigger with phrases like "install firecrawl", "setup firecrawl", "firecrawl auth", "configure firecrawl API key".
68
83%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Risky
Do not use without reviewing
Quality
Discovery
89%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 well-structured skill description with explicit 'Use when' and 'Trigger with' clauses, strong natural trigger terms, and a clearly defined niche around Firecrawl SDK setup. The main weakness is that the capability description could be more specific about the concrete actions performed (e.g., environment variable setup, client initialization steps). Minor issue: uses second person 'your project' which slightly deviates from the preferred third-person voice.
Suggestions
Add more specific concrete actions like 'sets environment variables, initializes the Firecrawl client, verifies API key authentication' to improve specificity.
Replace 'your project' with third-person phrasing like 'a project' to align with the preferred voice guidelines.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Firecrawl SDK) and some actions (install, configure authentication), but doesn't list multiple concrete actions beyond setup—e.g., it doesn't mention specific steps like 'add environment variables', 'initialize client', or 'verify connection'. | 2 / 3 |
Completeness | Clearly answers both 'what' (install and configure Firecrawl SDK authentication for web scraping) and 'when' (setting up a new Firecrawl integration, configuring API keys, initializing Firecrawl), with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'install firecrawl', 'setup firecrawl', 'firecrawl auth', 'configure firecrawl API key', plus mentions 'web scraping' and 'API keys'. These are terms users would naturally say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive—'Firecrawl' is a specific product name, and the scope is narrowed to installation/configuration/authentication. Very unlikely to conflict with other skills unless there are multiple Firecrawl-related skills. | 3 / 3 |
Total | 11 / 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 solid, actionable skill with clear step-by-step instructions and executable code for both TypeScript and Python. Its main weakness is moderate verbosity — covering both languages in full with separate verification steps, plus an extensive error table and multiple example variants, makes it longer than necessary for a setup skill. The workflow is well-sequenced with a verification checkpoint.
Suggestions
Trim the overview sentence explaining what Firecrawl does — Claude can infer this from context and the skill description.
Consider consolidating the TypeScript and Python verification into a single step with both code blocks, rather than two separate numbered steps, to reduce perceived complexity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some redundancy — providing both TypeScript and Python verification as separate numbered steps inflates the content, and some explanatory text (e.g., 'Firecrawl turns any website into LLM-ready markdown or structured data') is unnecessary context Claude already knows. The error handling table and examples section add useful but slightly verbose content. | 2 / 3 |
Actionability | All code examples are fully executable and copy-paste ready across both TypeScript and Python. Install commands, environment variable setup, verification scripts, and error handling are all concrete and specific with real package names and API patterns. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced (install → configure → verify → optional self-hosted). The verification step serves as an explicit validation checkpoint confirming API connectivity, and the error handling table provides a clear feedback loop for common failure modes. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections, but for a setup/auth skill it's quite long (~100 lines of content). The self-hosted setup, multiple language examples, and extensive error table could be split into referenced files. However, with no bundle files, inline content is the only option, and the sections are at least well-organized with clear headers. | 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.