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.

65

Quality

77%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./plugins/cloudflare-workers/skills/cloudflare-workers-observability/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

64%

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

This is a solid, actionable skill with good executable code examples covering the key Cloudflare Workers observability components. Its main weaknesses are the lack of an end-to-end setup workflow with validation checkpoints and some redundancy between the quick start and the full Logger class. The progressive disclosure structure is well-designed in theory but unsupported by actual bundle files.

Suggestions

Add an explicit end-to-end setup workflow with validation steps (e.g., 1. Configure wrangler.jsonc → 2. Deploy → 3. Verify logs appear with `wrangler tail` → 4. Confirm Analytics Engine writes via SQL query)

Remove the simple logger factory from Quick Start since the full Logger class below covers the same ground more completely, or consolidate into one example

Trim explanatory comments in the Critical Rules section (e.g., 'Plain text logs are hard to parse and aggregate') that Claude already understands

DimensionReasoningScore

Conciseness

The skill is reasonably efficient but includes some redundancy—the quick start logger factory and the full Logger class cover similar ground. The error prevention table and component overview table add value but could be tighter. Some explanations like 'Plain text logs are hard to parse and aggregate' are unnecessary for Claude.

2 / 3

Actionability

The skill provides fully executable TypeScript code for logging, Analytics Engine integration, and Tail Workers. The wrangler.jsonc configuration is copy-paste ready, and the code examples are complete with proper types and interfaces.

3 / 3

Workflow Clarity

The skill presents individual components clearly but lacks an explicit multi-step workflow for setting up observability end-to-end. There are no validation checkpoints—e.g., no steps to verify that Tail Workers are receiving events, that Analytics Engine bindings work, or how to confirm logging is properly configured after setup.

2 / 3

Progressive Disclosure

The skill references multiple files (references/logging.md, references/analytics-engine.md, templates/, scripts/) with clear navigation signals, which is good structure. However, no bundle files are provided, so all referenced paths are unverifiable. The main file itself is quite long with substantial inline code that could be offloaded to the referenced templates.

2 / 3

Total

9

/

12

Passed

Description

89%

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 solid skill description that clearly identifies its niche (Cloudflare Workers observability) and provides explicit trigger guidance. Its main weakness is that it lists feature areas rather than concrete actions the skill can perform. The trigger terms are well-chosen and cover both Cloudflare-specific and general observability vocabulary.

Suggestions

Replace feature area listing with specific concrete actions, e.g., 'Configure Tail Workers for distributed tracing, set up Analytics Engine queries, create alert rules, and debug worker logs' instead of just naming the concepts.

DimensionReasoningScore

Specificity

Names the domain (Cloudflare Workers observability) and lists several relevant concepts (logging, Analytics Engine, Tail Workers, metrics, alerting), but these are more feature areas than concrete actions. It doesn't describe specific actions like 'configure alert rules', 'parse tail worker logs', or 'set up Analytics Engine bindings'.

2 / 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'). The 'Use for...' clause serves as an explicit trigger guidance.

3 / 3

Trigger Term Quality

Includes strong natural keywords users would say: 'monitoring', 'debugging', 'tracing', 'log parsing', 'metric aggregation', 'alert configuration', 'Cloudflare Workers', 'Analytics Engine', 'Tail Workers'. Good coverage of both product-specific and general observability terms.

3 / 3

Distinctiveness Conflict Risk

Highly specific to Cloudflare Workers observability, which is a clear niche. The combination of Cloudflare-specific terms (Analytics Engine, Tail Workers) with observability concepts makes it very unlikely to conflict with other skills.

3 / 3

Total

11

/

12

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.

Validation11 / 11 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.