CtrlK
BlogDocsLog inGet started
Tessl Logo

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

69

Quality

84%

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

68%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 well-structured, actionable observability reference with strong code examples and clear reference navigation, weakened mainly by the lack of an explicit sequenced workflow with validation checkpoints and a broken templates/ reference path.

Suggestions

Add an explicit end-to-end setup workflow with validation checkpoints (configure wrangler.jsonc → deploy → verify logs in dashboard → attach Tail Worker → verify events received) instead of presenting only standalone patterns.

Remove the redundant simple createLogger() factory in Quick Start since the full Logger class in 'Structured Logging Pattern' supersedes it, tightening conciseness and removing overlap.

Fix or remove the dangling templates/ references — the Templates table points to templates/logging-setup.ts, analytics-worker.ts, and tail-worker.ts, but no templates/ directory exists in the bundle.

DimensionReasoningScore

Conciseness

The body is dense and code-heavy without explaining basic concepts Claude already knows, but the Quick Start simple logger factory duplicates the fuller Logger class in 'Structured Logging Pattern', so a little trimming is possible.

4 / 5

Actionability

Provides concrete, mostly copy-paste-ready TypeScript, a wrangler.jsonc config, and runnable script commands, with only minor gaps such as the undefined handleRequest() and env.LOGGING_ENDPOINT stubs.

4 / 5

Workflow Clarity

The body is organized as a reference cookbook of standalone patterns and config rather than an explicit end-to-end setup sequence, and no validation checkpoints (e.g., verify logs appear, verify Tail Worker receives events) are given.

3 / 5

Progressive Disclosure

Clear section structure with a well-signaled 'When to Load References' map pointing to real one-level-deep reference files, but the Templates table references a templates/ directory that does not exist in the bundle — a dangling reference that prevents a top score.

4 / 5

Total

15

/

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 strong, third-person description that concisely states what the skill does and when to use it with concrete trigger terms. No vagueness, over-claims, or voice issues.

DimensionReasoningScore

Specificity

Names the domain and lists multiple concrete components and actions — 'logging, Analytics Engine, Tail Workers, metrics, and alerting' plus 'monitoring, debugging, tracing' — giving comprehensive coverage rather than vague language.

5 / 5

Completeness

Explicitly answers both 'what' ('Cloudflare Workers observability with logging, Analytics Engine, Tail Workers, metrics, and alerting') and 'when' ('Use for monitoring, debugging, tracing...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural trigger phrases a user would actually say — 'monitoring, debugging, tracing, or encountering log parsing, metric aggregation, alert configuration errors' — covering the common synonyms for the domain.

5 / 5

Distinctiveness Conflict Risk

The Cloudflare Workers observability niche with product-specific triggers (Tail Workers, Analytics Engine) is clearly distinct from generic skills with minimal conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
secondsky/claude-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.