workers-observability
Cloudflare Workers observability with logging, Analytics Engine, Tail Workers, metrics, and alerting. Use for monitoring, debugging, tracing, or encountering log parsing, metric aggregation, alert configuration errors.
Install with Tessl CLI
npx tessl i github:secondsky/claude-skills --skill workers-observabilityOverall
score
92%
Does it follow best practices?
Validation for skill structure
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 a well-crafted skill description that clearly identifies the Cloudflare Workers observability domain with specific named features, provides explicit 'Use for' trigger guidance, and includes natural keywords users would employ when debugging or monitoring. The description is concise yet comprehensive, using proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete capabilities: 'logging, Analytics Engine, Tail Workers, metrics, and alerting' - these are distinct, named features rather than vague abstractions. | 3 / 3 |
Completeness | Clearly answers both what ('Cloudflare Workers observability with logging, Analytics Engine, Tail Workers, metrics, and alerting') and when ('Use for monitoring, debugging, tracing, or encountering log parsing, metric aggregation, alert configuration errors'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'monitoring', 'debugging', 'tracing', 'log parsing', 'metric aggregation', 'alert configuration errors' - good coverage of both high-level tasks and specific error scenarios. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to Cloudflare Workers observability stack with named components (Analytics Engine, Tail Workers) - unlikely to conflict with generic monitoring or other cloud provider skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill with excellent actionability and progressive disclosure. The content provides production-ready code examples, clear configuration patterns, and well-organized references. The main weakness is the lack of explicit validation workflows for setup and configuration tasks, which would help catch errors early in observability implementation.
Suggestions
Add a validation workflow section with explicit steps to verify logging is working (e.g., 'After configuration: 1. Deploy worker, 2. Send test request, 3. Check dashboard for logs, 4. If missing, verify observability.enabled in wrangler.jsonc')
Include a troubleshooting checklist with verification commands for common setup issues like 'Tail Worker not receiving' events
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing executable code examples without explaining basic concepts Claude already knows. Every section serves a clear purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides fully executable TypeScript code examples that are copy-paste ready, including complete logger implementations, Analytics Engine usage, and Tail Worker patterns with proper type definitions. | 3 / 3 |
Workflow Clarity | While the content provides clear patterns and configuration examples, it lacks explicit validation checkpoints and feedback loops for setup processes. The 'Top 8 Errors Prevented' table helps but doesn't provide step-by-step verification workflows. | 2 / 3 |
Progressive Disclosure | Excellent structure with a quick start, clear component overview, and well-signaled one-level-deep references to specific reference files, templates, and scripts. The 'When to Load References' section provides clear navigation guidance. | 3 / 3 |
Total | 11 / 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 — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 13 / 16 Passed | |
- 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.