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".
89
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%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 an excellent skill description that clearly defines its scope around Firecrawl monitoring, provides explicit trigger guidance with natural user phrases, and occupies a distinct niche. It covers both what the skill does and when to use it comprehensively, with concrete actions like credit tracking, dashboard setup, and failure alerting.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: monitoring pipelines, metrics tracking, credit tracking, quality alerts, setting up dashboards, and configuring alerting for scrape failures and credit consumption. | 3 / 3 |
Completeness | Clearly answers both 'what' (monitor Firecrawl scraping pipelines with metrics, credit tracking, and quality alerts) and 'when' (explicit 'Use when...' clause covering implementing monitoring, setting up dashboards, configuring alerting, plus explicit trigger phrases). | 3 / 3 |
Trigger Term Quality | Includes a rich set of natural trigger terms explicitly listed: 'firecrawl monitoring', 'firecrawl metrics', 'firecrawl observability', 'monitor firecrawl', 'firecrawl alerts'. Also includes contextual terms like 'dashboards', 'scrape failures', 'credit consumption' that users would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific 'Firecrawl' product focus combined with monitoring/observability niche. The trigger terms are all Firecrawl-specific, making it very unlikely to conflict with generic monitoring or generic web scraping skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill with executable TypeScript code, concrete Prometheus alert rules, and specific Grafana queries. The workflow is well-sequenced with validation checkpoints (credit thresholds, quality evaluation, error rate alerts). Minor weaknesses include the length of inline code that could be split into bundle files and some slightly unnecessary content like external resource links.
Suggestions
Consider moving the larger code blocks (instrumented wrapper, crawl tracker) into separate bundle files and referencing them from SKILL.md to improve progressive disclosure.
Remove the Resources section with external links since Claude cannot browse them, saving tokens.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with good use of tables and code, but includes some unnecessary elements like the Resources section (links Claude can't browse) and minor verbosity in comments. The overview sentence explaining what monitoring means is slightly redundant given the context. | 2 / 3 |
Actionability | Provides fully executable TypeScript code for the instrumented wrapper, credit monitor, and crawl tracker. Prometheus alert rules and Grafana queries are copy-paste ready. The error handling table gives specific, actionable solutions. | 3 / 3 |
Workflow Clarity | The five steps are clearly sequenced from instrumentation → credit monitoring → crawl tracking → alerting → dashboards. The credit health check includes threshold-based alerting (warning/critical), the crawl monitor includes polling with progress metrics, and the alert rules provide explicit validation thresholds for detecting degradation. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections and tables, but the skill is quite long (~150 lines of substantive content) and could benefit from splitting the code examples into separate files. The reference to 'firecrawl-incident-runbook' in Next Steps is good but the bundle has no supporting files. | 2 / 3 |
Total | 10 / 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
a04d1a2
- 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.