CtrlK
BlogDocsLog inGet started
Tessl Logo

firecrawl-reference-architecture

Implement Firecrawl reference architecture with scrape/crawl/map/extract pipelines. Use when designing new Firecrawl integrations, reviewing project structure, or building content ingestion pipelines for AI/RAG applications. Trigger with phrases like "firecrawl architecture", "firecrawl project structure", "firecrawl pipeline", "firecrawl RAG", "firecrawl knowledge base".

64

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/saas-packs/firecrawl-pack/skills/firecrawl-reference-architecture/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%Weight 40%Scale 1-5

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

A clean, code-centric skill body that is executable and well-structured, with the main weakness being absent explicit validation/retry checkpoints in the batch crawl and scrape workflows.

Suggestions

Add explicit validation checkpoints to the crawl/batch-scrape workflows (e.g. verify crawl job completed, retry on partial results, validate manifest against discovered URLs) to lift workflow clarity above the batch-operation cap of 3.

Reconcile imports across files: show the `firecrawl` import in the pipeline files that use it, and define `batchScrapeUrls` in the service layer so the Step 3 example is fully self-contained.

Trim minor redundancy (inline comments like '(1 credit)'/'(LLM+JSON)' and the large ASCII diagram) to push conciseness toward fully lean.

DimensionReasoningScore

Conciseness

Mostly lean code-first body with a compact overview, diagram, and error table that assume Claude's competence; a few inline comments and the ASCII diagram could be trimmed slightly to reach fully token-efficient.

4 / 5

Actionability

Provides mostly executable, copy-paste-ready TypeScript across four steps with concrete examples, but minor gaps exist (e.g. `firecrawl` used in pipeline files without the import shown, and `batchScrapeUrls` not defined in the service layer).

4 / 5

Workflow Clarity

The four steps are sequenced and include implicit quality checks (thin-content skip, content-hash dedup), but the batch crawl/scrape operations lack explicit validation checkpoints or error-retry feedback loops, capping this per the batch-operation rule.

3 / 5

Progressive Disclosure

Well-organized sections (Overview, Diagram, Instructions, Error Handling, Examples, Resources, Next Steps) with clear external links and a one-level-deep pointer to firecrawl-multi-env-setup; no internal bundle files exist, which is appropriate for this content size.

4 / 5

Total

15

/

20

Passed

Description

87%Weight 40%Scale 1-5

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-structured description that explicitly answers both what and when with concrete, niche-specific trigger phrases. Minor room to tighten the more abstract 'reference architecture' framing into additional concrete actions.

DimensionReasoningScore

Specificity

Names concrete endpoint actions ('scrape/crawl/map/extract pipelines') plus design/review/build tasks, but the 'reference architecture' framing and 'designing integrations' are partly abstract, leaving minor coverage gaps versus a fully concrete action list.

4 / 5

Completeness

Clearly states what ('Implement Firecrawl reference architecture with scrape/crawl/map/extract pipelines') and when ('Use when designing new Firecrawl integrations... or building content ingestion pipelines'), plus explicit trigger phrases.

5 / 5

Trigger Term Quality

Explicitly lists natural trigger phrases like 'firecrawl architecture', 'firecrawl pipeline', 'firecrawl RAG', and 'firecrawl knowledge base' that users would plausibly say, though a few natural synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

The Firecrawl-specific niche and firecrawl-prefixed trigger phrases make it clearly distinguishable with minimal risk of firing for an unrelated skill.

5 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
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.