CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cloudflare-workers-performance

Cloudflare Workers performance optimization with CPU, memory, caching, bundle size. Use for slow workers, high latency, cold starts, or encountering CPU limits, memory issues, timeout errors.

64

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/cloudflare-workers/skills/cloudflare-workers-performance/SKILL.md
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, code-first optimization guide with good reference routing and mostly executable examples. Its main gaps are the absence of an explicit optimize-then-verify workflow (benchmarking is never used as a checkpoint) and a Templates table that references files missing from the bundle.

Suggestions

Add a short explicit workflow, e.g., 1. Profile with `scripts/profile-worker.sh` or the timing wrapper, 2. Apply the relevant optimization section, 3. Re-run `scripts/benchmark.sh <url>` and compare before/after — this gives the skill the validation checkpoint it currently lacks (workflow_clarity).

Fix the progressive-disclosure gap: either add the three `templates/*.ts` files referenced in the Templates table or remove/replace that table with pointers to content that exists.

Tighten conciseness by merging the 'Critical Rules' list into the 'Top 10 Performance Errors' table (or vice versa), since they cover nearly identical ground, and complete the Quick Wins cache example with the cache.put path so the snippet is self-contained.

DimensionReasoningScore

Conciseness

The body is mostly lean, contrastive code (❌/✅ pairs) and dense tables with little explanation of concepts Claude already knows. Minor trims remain: the 'Critical Rules' list substantially duplicates the 'Top 10 Performance Errors' table, and the CacheLayer interface boilerplate is slightly padded, so it sits just below the 'every token earns its place' anchor.

4 / 5

Actionability

Concrete, mostly executable TypeScript throughout (profiling wrapper, batch generator, multi-layer cache, lazy imports) plus runnable script commands like `./benchmark.sh <url>`. Small gaps keep it from a 5: `process(chunk)` is undefined in the streaming example, the Quick Wins cache snippet shows `match` but not the `put` path, and `heavy-lib` is a placeholder rather than a real dependency.

4 / 5

Workflow Clarity

Sections are organized by concern and 'When to Load References' routes tasks to files, but there is no explicit diagnostic sequence (profile → optimize → re-benchmark) and no validation checkpoints — the benchmark script is listed yet never wired into a verify loop. It matches 'sequence present but checkpoints missing or implicit'; not a 4 because no verification step appears anywhere in the optimization flow.

3 / 5

Progressive Disclosure

Scored against the actual bundle: the overview cleanly routes tasks to five real one-level-deep references (cpu-optimization.md, memory-optimization.md, etc.) and lists real scripts. However, the 'Templates' table points to `templates/performance-middleware.ts`, `templates/caching-layer.ts`, and `templates/optimized-worker.ts`, which do not exist in the bundle — dead references that keep this below a 5.

4 / 5

Total

15

/

20

Passed

Description

82%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 description that explicitly states domain and scope and includes concrete, natural 'Use for' trigger phrases in third person. Its only weakness is that capabilities are expressed as topic nouns (CPU, memory, caching, bundle size) rather than concrete action verbs, and some common trigger synonyms are absent.

DimensionReasoningScore

Specificity

"Cloudflare Workers performance optimization with CPU, memory, caching, bundle size" names the domain and concrete scope areas, but these are topic nouns rather than specific actions (no 'extract', 'profile', 'optimize' verbs), matching the 'names domain and 1-2 concrete actions' anchor. Not a 4 because it never lists multiple concrete capability actions, and not a 2 because the optimization areas are explicitly enumerated.

3 / 5

Completeness

Explicitly answers both: what ("performance optimization with CPU, memory, caching, bundle size") and when ("Use for slow workers, high latency, cold starts, or encountering CPU limits, memory issues, timeout errors") with concrete trigger phrases, in third person. Matches the anchor-5 example pattern of a clear what followed by an explicit 'Use when' clause with triggers.

5 / 5

Trigger Term Quality

"slow workers, high latency, cold starts, CPU limits, memory issues, timeout errors" are phrases users would naturally say, giving good keyword coverage. Not a 5 because common synonyms and variations (e.g., 'Worker script', '100ms CPU', 'startup time', 'request timeouts' only partially covered) are missing.

4 / 5

Distinctiveness Conflict Risk

"Cloudflare Workers performance optimization" carves out a clear niche with edge-specific triggers (CPU limits, cold starts, edge caching) that would not naturally fire for other skills. Minor theoretical overlap with generic web performance skills, but the Cloudflare Workers scope keeps conflict risk minimal.

5 / 5

Total

17

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

secondsky/claude-skills

Path

plugins/cloudflare-workers/skills/cloudflare-workers-performance/SKILL.md

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.