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".
85
83%
Does it follow best practices?
Impact
Pending
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, making it easy for Claude to select appropriately. The trigger terms are natural and specific to the Firecrawl product. The main weakness is that the capability description could be more specific about the concrete actions performed during setup (e.g., installing packages, setting env vars, initializing the client).
Suggestions
Add more specific concrete actions like 'install the firecrawl-js or firecrawl-py package, set environment variables for API keys, initialize the Firecrawl client' to improve specificity.
| 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. | 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 phrases 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. | 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 setup skill with clear step-by-step instructions, executable code in both TypeScript and Python, and a useful error handling table. Its main weakness is moderate verbosity — the dual-language verification steps and partially redundant examples section inflate the token count. The workflow is well-sequenced with proper validation checkpoints.
Suggestions
Consolidate the Examples section with Steps 3-4 to avoid repeating initialization patterns — the dotenv examples could be inline notes rather than separate code blocks.
Consider moving the error handling table and self-hosted setup to a referenced file (e.g., TROUBLESHOOTING.md) to keep the main skill leaner.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some redundancy — separate TypeScript and Python verification steps could be consolidated, and the Examples section partially repeats initialization patterns already shown in Steps 3-4. The overview sentence explaining what Firecrawl does is borderline unnecessary context for Claude. | 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 sequenced (install → configure → verify → optional self-hosted), with an explicit verification/connection test step that serves as a validation checkpoint. The error handling table provides a clear feedback loop for diagnosing failures at each stage. | 3 / 3 |
Progressive Disclosure | The content is reasonably well-structured with clear sections, but it's somewhat long for a setup/auth skill — the error table, multiple examples, and resources could potentially be referenced externally. However, it does reference 'firecrawl-hello-world' as a next step, showing awareness of content splitting. | 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
c8a915c
- 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.