firecrawl-core-workflow-a
Execute FireCrawl primary workflow: Core Workflow A. Use when implementing primary use case, building main features, or core integration tasks. Trigger with phrases like "firecrawl main workflow", "primary task with firecrawl".
Overall
score
32%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill firecrawl-core-workflow-aActivation
0%This description fails on all dimensions by using placeholder-style language that provides no meaningful information about what the skill does. It relies entirely on the word 'firecrawl' for identification while describing capabilities in completely abstract terms like 'Core Workflow A' and 'primary use case'. Claude would have no basis for selecting this skill appropriately.
Suggestions
Replace abstract terms like 'Core Workflow A' and 'primary use case' with specific actions FireCrawl performs (e.g., 'Scrape web pages, extract structured content, crawl entire websites').
Add natural trigger terms users would actually say, such as 'web scraping', 'crawl website', 'extract web content', 'scrape URL', or 'website data extraction'.
Rewrite the 'Use when' clause with concrete scenarios like 'Use when the user needs to scrape websites, extract content from URLs, or crawl multiple pages for data.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, abstract language like 'primary workflow', 'Core Workflow A', 'primary use case', 'main features', and 'core integration tasks' without ever specifying what concrete actions are performed. No actual capabilities are described. | 1 / 3 |
Completeness | While it attempts to answer 'when' with trigger phrases, the 'what' is completely missing - 'Core Workflow A' and 'primary use case' tell Claude nothing about what this skill actually does. Both components are effectively absent or meaningless. | 1 / 3 |
Trigger Term Quality | The trigger phrases 'firecrawl main workflow' and 'primary task with firecrawl' are artificial and unlikely to be naturally spoken by users. Real users would say things like 'scrape website', 'crawl pages', or 'extract web content' - none of which are included. | 1 / 3 |
Distinctiveness Conflict Risk | Terms like 'primary workflow', 'main features', and 'core integration tasks' are extremely generic and could apply to virtually any skill. Only 'firecrawl' provides any distinctiveness, but without describing what FireCrawl does, this offers minimal differentiation. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
30%This skill is a template/skeleton with good structural organization but zero actionable content. Every code block, error table entry, and example contains only placeholder text. While the progressive disclosure and organization are exemplary, the complete absence of real instructions makes this skill unusable.
Suggestions
Replace all placeholder code comments (e.g., '// Step 1 implementation') with actual executable TypeScript code showing FireCrawl API usage
Fill in the error handling table with real FireCrawl errors, their actual causes, and specific solutions
Add concrete examples showing actual API calls, expected responses, and how to process results
Include validation steps between workflow stages to verify each step completed successfully before proceeding
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The structure is lean and doesn't over-explain concepts, but the content is entirely placeholder text with no actual substance, making it impossible to assess true token efficiency. | 2 / 3 |
Actionability | All code blocks contain only comments like '// Step 1 implementation' with no executable code. The error handling table uses placeholder 'Error 1', 'Cause', 'Solution' entries. Nothing is copy-paste ready or concrete. | 1 / 3 |
Workflow Clarity | While steps are numbered, they contain no actual instructions. There are no validation checkpoints, no feedback loops, and no way to know what each step actually does or how to verify success. | 1 / 3 |
Progressive Disclosure | The structure demonstrates good progressive disclosure with clear sections, external resource links, and a reference to related workflow. Navigation is straightforward with one-level-deep references. | 3 / 3 |
Total | 7 / 12 Passed |
Validation
75%Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
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 | 12 / 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.