firecrawl-core-workflow-b
Execute FireCrawl secondary workflow: Core Workflow B. Use when implementing secondary use case, or complementing primary workflow. Trigger with phrases like "firecrawl secondary workflow", "secondary task with firecrawl".
Overall
score
28%
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-bActivation
0%This description fails across all dimensions due to its reliance on self-referential, circular language that never explains what the skill actually does. It assumes the reader already knows what FireCrawl is and what 'Core Workflow B' means, making it useless for skill selection. The trigger terms are artificial constructs rather than natural user language.
Suggestions
Replace abstract terms like 'secondary workflow' and 'Core Workflow B' with concrete actions (e.g., 'Scrape website content, extract structured data, crawl linked pages').
Add natural trigger terms users would actually say, such as 'web scraping', 'extract website data', 'crawl pages', or specific file types/outputs.
Rewrite the 'Use when' clause to describe actual scenarios (e.g., 'Use when the user needs to extract content from websites, scrape multiple pages, or convert web content to structured data').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, abstract language like 'secondary workflow', 'secondary use case', and 'complementing primary workflow' without describing any concrete actions. There is no indication of what FireCrawl actually does or what 'Core Workflow B' entails. | 1 / 3 |
Completeness | The 'what' is essentially missing - we don't know what this skill actually does beyond vague references to 'secondary workflow'. The 'when' is present but meaningless without understanding what the skill does or what constitutes a 'secondary use case'. | 1 / 3 |
Trigger Term Quality | The trigger phrases are artificial and unlikely to be naturally spoken by users ('firecrawl secondary workflow', 'secondary task with firecrawl'). No natural keywords describing actual functionality are present - users wouldn't know to ask for a 'secondary workflow'. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it provides no clear niche. Terms like 'secondary workflow' and 'complementing primary workflow' could apply to virtually anything and provide no distinguishing characteristics from other skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
22%This skill is a template or skeleton with no actual content. All code blocks are empty placeholders, the error handling section is mislabeled, and there's no actionable guidance. The structure and cross-references are reasonable, but the skill provides zero value in its current state.
Suggestions
Replace all placeholder code comments with actual executable TypeScript/JavaScript code showing real FireCrawl API usage
Add concrete examples of what 'secondary workflow' means - what specific FireCrawl operations does this cover?
Rename 'Error Handling' section to 'Comparison' or move actual error handling code there with try/catch patterns and recovery steps
Add validation checkpoints between steps (e.g., 'Verify API response status before proceeding to Step 3')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The structure is reasonably lean, but the content is essentially placeholder text with no actual implementation. The comparison table and section headers add tokens without providing real value since the code blocks are empty comments. | 2 / 3 |
Actionability | All code blocks contain only placeholder comments like '// Step 1 implementation' with no actual executable code, commands, or concrete guidance. Claude cannot act on this skill as written. | 1 / 3 |
Workflow Clarity | While steps are numbered, they contain no actual instructions. The 'Error Handling' section is mislabeled (it's a comparison table, not error handling). No validation checkpoints or feedback loops are present. | 1 / 3 |
Progressive Disclosure | The skill references related skills (firecrawl-install-auth, firecrawl-core-workflow-a, firecrawl-common-errors) and external documentation appropriately. However, the main content itself is empty, making the structure hollow. | 2 / 3 |
Total | 6 / 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.