Create a minimal working FireCrawl example. Use when starting a new FireCrawl integration, testing your setup, or learning basic FireCrawl API patterns. Trigger with phrases like "firecrawl hello world", "firecrawl example", "firecrawl quick start", "simple firecrawl code".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill firecrawl-hello-world66
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 excellent trigger terms and clear 'when to use' guidance. The main weakness is the lack of specificity about what concrete actions the skill performs beyond 'create a minimal example' - it doesn't specify what the example does (scraping, crawling, API calls, etc.).
Suggestions
Add 2-3 specific concrete actions the example demonstrates, e.g., 'Demonstrates basic web scraping, single-page crawling, and API authentication setup'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (FireCrawl) and one action ('Create a minimal working example'), but lacks comprehensive concrete actions like specific API operations, data extraction methods, or output formats. | 2 / 3 |
Completeness | Clearly answers both what ('Create a minimal working FireCrawl example') and when ('Use when starting a new FireCrawl integration, testing your setup, or learning basic FireCrawl API patterns') with explicit trigger phrases. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'firecrawl hello world', 'firecrawl example', 'firecrawl quick start', 'simple firecrawl code' - these match how developers naturally request starter code. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche - specifically targets FireCrawl beginners/quick starts with clear trigger phrases. Unlikely to conflict with other skills due to the specific 'hello world' and 'quick start' framing. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill has good structure and organization but fails at its core purpose: providing a working 'hello world' example. The code snippets are incomplete placeholders rather than executable examples, which defeats the purpose of a quick-start skill. The error handling table is useful but the main content needs actual API calls.
Suggestions
Replace placeholder comments with actual executable API calls (e.g., scraping a test URL and printing the result)
Consolidate the duplicate TypeScript examples into a single, complete working example
Add a verification step after the API call to confirm success (e.g., 'You should see the scraped content printed to console')
Show the expected output structure from a real API response, not just a generic success message
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content has some redundancy - the TypeScript example is duplicated in both Step 2/3 and the Examples section. The structure is reasonable but could be tightened by consolidating examples. | 2 / 3 |
Actionability | The code examples are incomplete placeholders with '// Your first API call here' comments instead of actual executable API calls. A 'hello world' skill should show a complete, working example that demonstrates the API actually doing something. | 1 / 3 |
Workflow Clarity | Steps are listed sequentially but lack validation checkpoints. There's no verification step to confirm the setup works before proceeding, and the 'Make Your First API Call' step contains no actual API call to validate. | 2 / 3 |
Progressive Disclosure | Good structure with clear sections, appropriate use of external resource links, and a clear 'Next Steps' pointer to the next skill. Content is well-organized for a simple skill. | 3 / 3 |
Total | 8 / 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 | |
Table of Contents
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.