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
Pending
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 description with strong completeness and distinctiveness due to the specific Firecrawl domain focus. The explicit 'Use when' and 'Trigger with' clauses are excellent. The main weakness is that the specific capabilities could be more concrete—listing actual SDK operations rather than high-level patterns would improve specificity.
Suggestions
Add more concrete actions such as 'configure crawl jobs, handle rate limiting, extract structured data, manage async scraping workflows' to improve specificity beyond the abstract 'patterns' framing.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Firecrawl SDK) and mentions some actions like 'implementing integrations', 'building reusable scraping services', and 'establishing team coding standards', but doesn't list specific concrete actions like 'configure crawl jobs', 'handle pagination', 'extract structured data', etc. | 2 / 3 |
Completeness | Clearly answers both 'what' (apply production-ready Firecrawl SDK patterns for TypeScript and Python) and 'when' (implementing Firecrawl integrations, building scraping services, establishing coding standards) with explicit trigger phrases listed. | 3 / 3 |
Trigger Term Quality | Includes a good set of natural trigger terms: 'firecrawl SDK patterns', 'firecrawl best practices', 'firecrawl code patterns', 'idiomatic firecrawl', 'firecrawl wrapper'. Also mentions TypeScript and Python, and 'scraping services' which users might naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Firecrawl is a specific SDK/tool, making this highly distinctive. The repeated use of 'Firecrawl' as a qualifier throughout the description makes it very unlikely to conflict with generic web scraping or other SDK 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 production-quality code examples covering key Firecrawl SDK patterns. Its main weaknesses are the lack of validation checkpoints in the workflow (e.g., verifying client connectivity, testing individual steps) and some redundant sections (Output bullets, Error Handling table) that restate what the code already demonstrates. The content would benefit from being more concise and splitting detailed patterns into referenced files.
Suggestions
Add a validation checkpoint after Step 1 (e.g., 'Test connection: await getFirecrawl().scrapeUrl("https://example.com", { formats: ["markdown"] })') to verify setup before proceeding.
Remove the 'Output' bullet list and 'Error Handling' table, which largely duplicate information already clear from the code examples.
Consider splitting Steps 3-5 (retry, queue service, Zod validation) into a separate PATTERNS.md reference file, keeping SKILL.md as a concise overview with the singleton client and basic scrape wrapper.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with executable code, but includes some unnecessary sections like 'Prerequisites' (Claude knows async/await), the 'Output' bullet list that just restates what the code already shows, and the 'Error Handling' table that largely duplicates information already evident from the code examples. | 2 / 3 |
Actionability | All code examples are fully executable, copy-paste ready TypeScript and Python with proper imports, types, and file paths. The patterns are concrete and production-ready with specific implementation details like retry status codes, queue configuration, and Zod schemas. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced from client setup through service composition, but there are no validation checkpoints or feedback loops. For a skill involving API integrations and batch scraping operations, there's no guidance on verifying the setup works, testing individual steps, or handling partial failures in scrapeMany. | 2 / 3 |
Progressive Disclosure | The content is somewhat monolithic at ~180 lines with all code inline. The Resources section links to external docs, and there's a reference to 'firecrawl-core-workflow-a', but the main content could benefit from splitting detailed patterns (retry, queue, Zod validation) into separate reference files while keeping the SKILL.md as a concise overview. | 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
c8a915c
- 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.