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

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

92%Weight 40%Scale 1-3

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

The body is concise, highly actionable, and workflows are clearly sequenced with a credit-budget validation checkpoint before risky crawls. The main weakness is a dangling reference to a non-existent firecrawl-reference-architecture file, which drags down progressive disclosure.

Suggestions

Remove or fix the dangling Next Steps reference to 'firecrawl-reference-architecture' since no such bundle file exists, or create the referenced file.

Consider extracting the CreditBudget class and cachedScrape helper into a scripts/ file referenced one level deep, keeping SKILL.md as a tighter overview.

Add a brief verification step for the credit-monitoring curl (e.g. expected jq output shape) so the monitoring workflow has an explicit checkpoint like the crawl workflow does.

Dimension	Reasoning	Score
Conciseness	The body is lean and code-forward with no padding about what crawls or APIs are; every section earns its place with executable snippets and tight cost tables, matching the lean-and-efficient anchor. Not below 3 because there is no unnecessary conceptual explanation.	3 / 3
Actionability	Provides fully executable TypeScript using the real @mendable/firecrawl-js SDK and copy-paste curl examples with exact options and credit tallies, satisfying the copy-paste-ready anchor. Not below 3 because no guidance is vague or pseudocode.	3 / 3
Workflow Clarity	Six numbered steps form a clear sequence, and the risky batch operation (crawl) is gated by an explicit pre-flight validation checkpoint (budget.canAfford check that throws before spending credits) with an error-handling recovery table. Not below 3 because validation is present rather than only implied.	3 / 3
Progressive Disclosure	Content is well-organized into clear sections but the closing Next Steps points to a firecrawl-reference-architecture reference that does not exist as a bundle file, a poorly-signaled dangling reference. Not 3 because the navigation pointer is broken; not 1 because the core content is self-contained and well-structured rather than a monolithic wall or deeply nested.	2 / 3
	Total	11 / 12 Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, complete, and well-triggered, naming four concrete cost-optimization actions and six natural trigger phrases with an explicit Use-when clause. It is concise and tightly scoped to the Firecrawl billing niche.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "crawl limits, format selection, caching, and credit monitoring" — rather than vague language; matches the 3-anchor example of enumerating specific capabilities.	3 / 3
Completeness	Explicitly answers both what it does (optimize costs via the four techniques) and when to use it ("Use when analyzing Firecrawl billing, reducing API costs, or implementing credit budget alerts") with explicit trigger guidance, satisfying the top anchor.	3 / 3
Trigger Term Quality	Provides six natural phrases a user would actually say ("firecrawl cost", "firecrawl billing", "reduce firecrawl costs", "firecrawl pricing", "firecrawl credits", "firecrawl budget"), giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear Firecrawl-specific niche with distinct triggers unlikely to collide with other skills; not below 2 because it is not generic, and not above 3 as 3 is the scale max.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/saas-packs/firecrawl-pack/skills/firecrawl-cost-tuning/SKILL.md
Commit: 4c47e33

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.