CtrlK
BlogDocsLog inGet started
Tessl Logo

firecrawl-cost-tuning

Optimize Firecrawl costs through crawl limits, format selection, caching, and credit monitoring. Use when analyzing Firecrawl billing, reducing API costs, or implementing credit budget alerts. Trigger with phrases like "firecrawl cost", "firecrawl billing", "reduce firecrawl costs", "firecrawl pricing", "firecrawl credits", "firecrawl budget".

72

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 strong, executable cost-tuning guide with concrete code for each technique and a validation gate for batch operations. Its main weaknesses are mild redundancy between inline cost comments and the summary table, and an all-inline structure that could offload some reference material to bundle files.

Suggestions

Trim redundancy: drop the per-step 'Cost:' comment lines or the Cost Optimization Summary table rather than carrying both, since they convey the same savings data.

Add an explicit validate-then-proceed checkpoint linking Step 5's budget gate into the crawl workflow (e.g., 'always call budget.canAfford() before crawlUrl and abort on failure') so the sequence reads as a true pipeline.

Consider moving the full CreditBudget class and the credit cost table into a references/ file, keeping SKILL.md as an overview that links to it, to improve progressive disclosure for a skill of this length.

DimensionReasoningScore

Conciseness

The body is code-forward and assumes competence (no explanation of what Firecrawl or an API is), but the inline 'Cost:' annotations and the Cost Optimization Summary table restate technique/savings information already shown in the steps.

4 / 5

Actionability

Provides copy-paste-ready TypeScript and bash for every common case — bounded crawl, batch scrape, map-then-scrape, caching, credit monitoring, and minimal-format selection — with real API calls and parameters.

5 / 5

Workflow Clarity

Six clearly numbered steps form a usable sequence, and Step 5's budget.canAfford() gate is a validation checkpoint before batch crawls (avoiding the destructive/batch cap of 3); however the steps read more as a technique menu than a strict validate-between-steps pipeline.

4 / 5

Progressive Disclosure

Content is well-sectioned (Overview, Credit Cost Table, Steps 1-6, Error Handling, Summary, Resources, Next Steps) with no nested references and a clearly signaled pointer to 'firecrawl-reference-architecture'; the minor gap is that everything lives inline with no split reference files for a ~190-line skill.

4 / 5

Total

17

/

20

Passed

Description

100%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 well-crafted description that clearly states capabilities, provides explicit use-when guidance, and includes comprehensive natural trigger phrases with minimal conflict risk. It uses appropriate third-person voice and avoids fluff.

DimensionReasoningScore

Specificity

Lists four concrete actions — 'crawl limits, format selection, caching, and credit monitoring' — giving comprehensive coverage of the cost-tuning domain rather than vague language.

5 / 5

Completeness

Explicitly answers both 'what' (optimize costs via crawl limits, format selection, caching, credit monitoring) and 'when' ('Use when analyzing Firecrawl billing, reducing API costs, or implementing credit budget alerts') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Provides six natural trigger phrases ('firecrawl cost', 'firecrawl billing', 'reduce firecrawl costs', 'firecrawl pricing', 'firecrawl credits', 'firecrawl budget') covering synonyms a user would actually say.

5 / 5

Distinctiveness Conflict Risk

Firecrawl-specific niche with distinct triggers; the branded 'firecrawl' qualifier makes conflict with other skills minimal.

5 / 5

Total

20

/

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.