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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

80%

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

Highly actionable, executable pitfall reference with tight, value-adding comments. Weaker on workflow clarity (flat checklist, no review sequence) and progressive disclosure (single monolithic file, no split references).

Suggestions

Add a short sequenced review workflow before the checklist (e.g., 1. Locate Firecrawl calls via grep, 2. Evaluate each against the pitfalls, 3. Report violations with the matching pitfall number) to lift workflow clarity.

Move the per-pitfall detail into a referenced file (e.g., references/pitfalls.md) and keep SKILL.md as a concise overview + checklist, enabling true one-level-deep progressive disclosure.

Tighten the few chatty inline comments (e.g., 'Hammering the API', 'might be undefined!') where they restate what the code already shows.

Dimension	Reasoning	Score
Conciseness	Lean inline comments that earn their place (e.g., 'no limit — a docs site with 50K pages burns your entire credit balance'); no explaining of concepts Claude already knows. Though long, each of the 10 pitfalls is a distinct, non-redundant unit rather than padding.	3 / 3
Actionability	Every pitfall ships fully executable TypeScript with the correct package name (@mendable/firecrawl-js) and concrete GOOD/BETTER option blocks — copy-paste ready, not pseudocode.	3 / 3
Workflow Clarity	A Code Review Checklist of checkboxes is provided, but the body offers no sequenced review process or validation checkpoints (e.g., read file -> check each pitfall -> report). It is a flat checklist rather than a validated workflow.	2 / 3
Progressive Disclosure	Well sectioned into Overview / Pitfalls / Checklist / Resources / Next Steps with no nested references, but it is a monolithic ~230-line single file with no bundle files; content that could be split (e.g., pitfalls into a reference file) is entirely inline.	2 / 3
	Total	10 / 12 Passed

Description

100%

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

A strong, well-constructed description: third-person voice, explicit what-and-when guidance, concrete actions, and a clear set of natural trigger phrases scoped to a distinct niche.

Dimension	Reasoning	Score
Specificity	States concrete actions — 'Identify and avoid Firecrawl anti-patterns and common integration mistakes' and expands to reviewing, onboarding, and auditing — listing multiple specific actions rather than vague language.	3 / 3
Completeness	Clearly answers 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') with explicit triggers.	3 / 3
Trigger Term Quality	Provides explicit natural trigger phrases a user would say — 'firecrawl mistakes', 'firecrawl anti-patterns', 'firecrawl pitfalls', 'firecrawl what not to do', 'firecrawl code review' — with good coverage of variations.	3 / 3
Distinctiveness Conflict Risk	Targets a narrow Firecrawl-specific niche with distinct triggers ('firecrawl pitfalls', etc.), making it unlikely to fire for unrelated skills.	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
Commit: 50ab626

Reviewed: 2 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.