firecrawl-known-pitfalls

Identify and avoid Firecrawl anti-patterns and common integration mistakes. Use when reviewing Firecrawl code, onboarding new developers, or auditing existing integrations for best practices violations. Trigger with phrases like "firecrawl mistakes", "firecrawl anti-patterns", "firecrawl pitfalls", "firecrawl what not to do", "firecrawl code review".

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

80%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable and token-efficient, presenting real production pitfalls as executable BAD/GOOD TypeScript pairs. Its main weakness is structure: it is a monolithic catalog with no progressive disclosure into reference files and no gated workflow with validation checkpoints.

Suggestions

Add a short sequenced code-review workflow with explicit validation gates (e.g., run the checklist, flag each violation, re-verify fixes) to raise workflow_clarity.

Move detailed per-pitfall remediation or extended examples into a references/ file (e.g., PITFALLS.md) and keep SKILL.md as an overview with one-level-deep links to improve progressive_disclosure.

Add a feedback loop for the batch/extract pitfalls (validate-extract → on failure log issues and skip) so destructive or persistence operations have explicit retry guidance.

Dimension	Reasoning	Score
Conciseness	The body assumes Claude's competence — "Real gotchas from production Firecrawl integrations" with no padding about what Firecrawl or credits are — and each pitfall is a terse BAD/why/GOOD block where every token earns its place, matching the lean score-3 anchor.	3 / 3
Actionability	Each pitfall ships fully executable TypeScript (e.g., "import FirecrawlApp from \"@mendable/firecrawl-js\"" with options like "limit: 100, maxDepth: 3, includePaths"), plus an install command and a Zod validation schema, making it copy-paste ready per the score-3 anchor.	3 / 3
Workflow Clarity	The closing "Code Review Checklist" lists steps but the skill is fundamentally a pitfall catalog rather than a sequenced process, and there are no explicit validation checkpoints or fix→retry feedback loops, so it sits at the score-2 anchor rather than the gated score-3 example.	2 / 3
Progressive Disclosure	Content is well-sectioned (## per pitfall) but everything is inline in a single ~210-line file with no bundle references (references/, scripts/, assets/ absent), so content that could be split stays inline, matching the score-2 anchor; the "Next Steps" pointer is to a sibling skill, not a one-level-deep bundle file.	2 / 3
	Total	10 / 12 Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: it states concrete capabilities, provides an explicit "Use when" clause, and enumerates natural trigger phrases in third person. It closely follows the rubric's good-example pattern.

Dimension	Reasoning	Score
Specificity	"Identify and avoid Firecrawl anti-patterns and common integration mistakes" plus enumerated contexts ("reviewing Firecrawl code, onboarding new developers, or auditing existing integrations") lists multiple specific concrete actions, matching the score-3 anchor rather than the single-action score-2 anchor.	3 / 3
Completeness	It answers both what ("Identify and avoid Firecrawl anti-patterns and common integration mistakes") and when ("Use when reviewing Firecrawl code, onboarding new developers, or auditing existing integrations"), matching the explicit-trigger score-3 anchor and exceeding the what-only score-2 anchor.	3 / 3
Trigger Term Quality	Explicit "Trigger with phrases like" lists natural terms a user would say ("firecrawl mistakes", "firecrawl anti-patterns", "firecrawl pitfalls", "firecrawl what not to do", "firecrawl code review"), giving good coverage rather than just "Works with Firecrawl" (score 2).	3 / 3
Distinctiveness Conflict Risk	The Firecrawl-specific niche with distinct trigger phrases is clearly distinguishable from general skills and unlikely to fire for the wrong skill, matching the score-3 anchor; it is far less generic than the score-2 "Works with document files" example.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/saas-packs/firecrawl-pack/skills/firecrawl-known-pitfalls/SKILL.md
Commit: 4c47e33

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.