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".
94
95%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
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 strong trigger terms and clear completeness. Its main weakness is that the specificity of capabilities could be improved by listing concrete anti-patterns or specific types of mistakes it covers, rather than staying at the abstract level of 'anti-patterns and common integration mistakes'.
Suggestions
Add 2-3 specific examples of the anti-patterns or mistake categories covered (e.g., 'rate limiting violations, improper error handling, missing pagination') to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Firecrawl integration) and some actions ('identify and avoid anti-patterns', 'reviewing code', 'auditing integrations'), but doesn't list specific concrete anti-patterns or actions it can perform. 'Common integration mistakes' is somewhat vague. | 2 / 3 |
Completeness | Clearly answers both 'what' (identify and avoid Firecrawl anti-patterns and common integration mistakes) and 'when' (reviewing Firecrawl code, onboarding new developers, auditing existing integrations) with explicit trigger phrases. | 3 / 3 |
Trigger Term Quality | Excellent trigger term coverage with natural phrases users would say: 'firecrawl mistakes', 'firecrawl anti-patterns', 'firecrawl pitfalls', 'firecrawl what not to do', 'firecrawl code review'. These are realistic search/query terms. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche — specifically about Firecrawl anti-patterns and mistakes, not general Firecrawl usage or web scraping. The focus on 'what not to do' and 'anti-patterns' clearly distinguishes it from a general Firecrawl usage skill. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill file that efficiently communicates 10 concrete Firecrawl anti-patterns with executable BAD/GOOD code pairs. The structure is highly scannable, the code review checklist provides a practical summary, and external references are cleanly signaled. It exemplifies what a pitfalls/anti-patterns skill should look like.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every pitfall is structured as BAD/GOOD with minimal prose. No unnecessary explanations of what Firecrawl is or how APIs work. Comments within code are terse and informative. Each token earns its place. | 3 / 3 |
Actionability | All 10 pitfalls include fully executable TypeScript code showing both the anti-pattern and the correct approach. The code is copy-paste ready with real package names, real options, and concrete values. | 3 / 3 |
Workflow Clarity | This is a checklist/reference skill rather than a multi-step workflow, and the single-purpose structure is clear and unambiguous. The code review checklist at the end provides an explicit validation checkpoint. Error handling and validation patterns are demonstrated in pitfalls 6 and 10. | 3 / 3 |
Progressive Disclosure | Content is well-organized with a clear overview, numbered pitfalls for easy scanning, a summary checklist, and one-level-deep references to external docs and the reference architecture skill. Nothing is buried or nested too deeply. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Commit
4dee593
- 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.