firecrawl-observability

Monitor Firecrawl scraping pipelines with metrics, credit tracking, and quality alerts. Use when implementing monitoring for Firecrawl operations, setting up dashboards, or configuring alerting for scrape failures and credit consumption. Trigger with phrases like "firecrawl monitoring", "firecrawl metrics", "firecrawl observability", "monitor firecrawl", "firecrawl alerts".

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

76%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 highly actionable, concise instrumentation reference with executable code and alert rules throughout. Its weakest point is workflow clarity: the setup steps lack explicit verification checkpoints to confirm metrics and alerts are actually live.

Suggestions

Add a verification step after instrumentation (e.g. 'Confirm firecrawl_scrapes_total appears in Prometheus before relying on alerts') to close the workflow feedback loop.

Resolve the dangling 'firecrawl-incident-runbook' reference — either ship the runbook as a bundle file or remove the pointer to avoid a dead navigation link.

Optionally split the Prometheus alert rules and dashboard panel definitions into a referenced reference file so the SKILL.md body stays an overview.

Dimension	Reasoning	Score
Conciseness	The body is lean and code/table-heavy with little padding of concepts Claude already knows; only minor prose ('Track these in Grafana/Datadog') could be trimmed.	4 / 5
Actionability	Provides fully executable TypeScript instrumentation, copy-paste Prometheus alert rules in YAML, and concrete PromQL dashboard queries covering the common monitoring cases.	5 / 5
Workflow Clarity	Five numbered steps are sequenced with concrete code, but there are no verification checkpoints (e.g. confirm metrics appear in Prometheus, test that an alert actually fires), leaving validation implicit.	3 / 5
Progressive Disclosure	Good section structure with coherent inline content and valid external resource links; the Next Steps reference to 'firecrawl-incident-runbook' points to a file that is not present in the bundle, a minor navigation gap.	4 / 5
	Total	16 / 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-scoped description that clearly answers both what and when, uses third-person voice, and supplies natural trigger phrases. Minor room to expand synonym coverage in the trigger list.

Dimension	Reasoning	Score
Specificity	Names the Firecrawl scraping domain plus several concrete actions ('metrics, credit tracking, and quality alerts', 'setting up dashboards', 'configuring alerting for scrape failures and credit consumption'), with only minor coverage gaps.	4 / 5
Completeness	Explicitly states what it does ('Monitor Firecrawl scraping pipelines with metrics, credit tracking, and quality alerts') and when to use it ('Use when implementing monitoring... setting up dashboards, or configuring alerting...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Lists five natural trigger phrases ('firecrawl monitoring', 'firecrawl metrics', 'firecrawl observability', 'monitor firecrawl', 'firecrawl alerts') that users would plausibly say, though a few synonyms (e.g. 'scrape monitoring') are absent.	4 / 5
Distinctiveness Conflict Risk	Targets a clear Firecrawl-specific niche with distinct, product-named triggers, making overlap with other skills unlikely.	5 / 5
	Total	18 / 20 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-observability/SKILL.md
Commit: 0540a62

Reviewed: about 17 hours 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.