firecrawl-install-auth
Install and configure FireCrawl SDK/CLI authentication. 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".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill firecrawl-install-auth80
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
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 strong completeness and trigger term coverage. It explicitly includes 'Use when' and 'Trigger with phrases' clauses which provide clear guidance for skill selection. The main weakness is that the specific capabilities could be more concrete - listing actual setup actions rather than general terms like 'configure' and 'initialize'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (FireCrawl SDK/CLI) and some actions (install, configure, authentication), but doesn't comprehensively list specific concrete actions like 'set environment variables', 'validate API key', or 'create config file'. | 2 / 3 |
Completeness | Clearly answers both what (install and configure FireCrawl SDK/CLI authentication) and when (setting up new integration, configuring API keys, initializing) with explicit 'Use when' and 'Trigger with phrases' clauses. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'install firecrawl', 'setup firecrawl', 'firecrawl auth', 'configure firecrawl API key', plus mentions 'API keys' and 'initializing FireCrawl'. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche focused on FireCrawl setup/authentication specifically. The explicit tool name and authentication focus make it unlikely to conflict with general web scraping or other SDK installation skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is well-structured and concise, with good error handling documentation and clear examples for both TypeScript and Python. However, the incomplete Step 3 verification code is a significant gap that undermines the workflow's completeness - users cannot actually confirm their setup works without this critical validation step.
Suggestions
Complete Step 3 with actual executable verification code that tests the API connection and confirms authentication succeeded
Add expected success output for the verification step so users know what a working setup looks like
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is lean and efficient with no unnecessary explanations. Every section serves a purpose and assumes Claude understands basic concepts like environment variables and package installation. | 3 / 3 |
Actionability | Most code is executable and copy-paste ready, but Step 3 'Verify Connection' contains only a placeholder comment '// Test connection code here' instead of actual verification code, which is a significant gap. | 2 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, but the verification step (Step 3) is incomplete, leaving no actual validation checkpoint. For an auth setup skill, verifying the connection actually works is critical. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections, appropriate use of tables for error handling, and external resources properly linked. Content is appropriately sized for a single file with clear navigation to next steps. | 3 / 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 |
|---|---|---|
description_voice | 'description' should use third person voice; found second person: 'your ' | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | 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.