firecrawl-sdk-patterns
Apply production-ready Firecrawl SDK patterns for TypeScript and Python. Use when implementing Firecrawl integrations, building reusable scraping services, or establishing team coding standards for Firecrawl. Trigger with phrases like "firecrawl SDK patterns", "firecrawl best practices", "firecrawl code patterns", "idiomatic firecrawl", "firecrawl wrapper".
80
77%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/firecrawl-pack/skills/firecrawl-sdk-patterns/SKILL.mdQuality
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 completeness and distinctiveness due to the specific Firecrawl SDK focus, explicit 'Use when' and 'Trigger with' clauses, and clear niche targeting. The main weakness is that the capability actions could be more concrete—listing specific operations like configuring crawl parameters, handling rate limits, or parsing responses rather than higher-level abstractions like 'building reusable scraping services'.
Suggestions
Replace abstract actions like 'building reusable scraping services' with more concrete capabilities such as 'configure crawl jobs, handle pagination, manage rate limits, extract structured data with Firecrawl SDK'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Firecrawl SDK) and mentions some actions like 'implementing integrations', 'building reusable scraping services', and 'establishing team coding standards', but these are somewhat abstract rather than listing concrete specific actions like 'configure crawl jobs, handle pagination, extract structured data'. | 2 / 3 |
Completeness | The description clearly answers both 'what' (apply production-ready Firecrawl SDK patterns for TypeScript and Python) and 'when' (explicit 'Use when' clause covering integrations, scraping services, and coding standards, plus a 'Trigger with' clause listing specific phrases). | 3 / 3 |
Trigger Term Quality | The description includes a dedicated trigger phrase list with natural terms users would say: 'firecrawl SDK patterns', 'firecrawl best practices', 'firecrawl code patterns', 'idiomatic firecrawl', 'firecrawl wrapper'. These are realistic phrases a developer would use, and the mention of TypeScript and Python adds language-specific triggers. | 3 / 3 |
Distinctiveness Conflict Risk | Firecrawl is a specific SDK/tool, making this highly distinctive. The description is narrowly scoped to Firecrawl SDK patterns specifically, which is unlikely to conflict with general web scraping skills or other SDK-related skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with high-quality executable code examples covering multiple production patterns. Its main weaknesses are verbosity (redundant summary sections and explanatory tables that restate what the code already demonstrates) and lack of validation checkpoints or testing guidance for the multi-step integration workflow. The content would benefit from splitting into a concise overview with referenced detail files.
Suggestions
Remove the 'Output' bullet list and 'Error Handling' table, which redundantly summarize what the code examples already clearly demonstrate.
Add explicit validation steps such as 'Test the singleton client by running a single scrape before proceeding to batch operations' or a minimal smoke-test snippet.
Split Python patterns, Zod validation, and the multi-tenant factory into separate referenced files to improve progressive disclosure and reduce the main file's length.
Remove the 'Prerequisites' section — Claude already understands async/await and TypeScript strict mode.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with executable code examples, but includes some unnecessary sections like 'Prerequisites' (Claude knows async/await), the 'Output' bullet list that just restates what the code does, and the 'Error Handling' table that largely duplicates information already conveyed by the code examples. The overview also restates what the code will show. | 2 / 3 |
Actionability | Every pattern is backed by fully executable, copy-paste-ready TypeScript and Python code with proper imports, file paths, and type definitions. The code is production-quality with concrete details like error status code handling, jitter in backoff, and queue configuration. | 3 / 3 |
Workflow Clarity | The steps are clearly sequenced and build on each other (client → wrapper → retry → service → validation), but there are no explicit validation checkpoints or feedback loops. For a skill involving API integrations and batch scraping operations, there's no guidance on how to verify the setup works, test the patterns, or handle partial failures in scrapeMany. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear headings, but it's a long monolithic file (~200 lines of code) with no bundle files to offload detail into. The Python patterns, Zod validation, and multi-tenant factory pattern could be separate referenced files. The reference to 'firecrawl-core-workflow-a' at the end is unverifiable with no bundle. | 2 / 3 |
Total | 9 / 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
3a2d27d
- 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.