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.
Install with Tessl CLI
npx tessl i github:secondsky/claude-skills --skill workers-performanceOverall
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 excels across all dimensions. It clearly identifies the specific platform (Cloudflare Workers), the optimization domains (CPU, memory, caching, bundle size), and provides explicit trigger conditions using natural language that users would actually use when experiencing performance problems. The description is concise yet comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete optimization areas: 'CPU, memory, caching, bundle size' - these are distinct, actionable domains rather than vague language. | 3 / 3 |
Completeness | Clearly answers both what ('Cloudflare Workers 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'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'slow workers', 'high latency', 'cold starts', 'CPU limits', 'memory issues', 'timeout errors' - these match real user problem descriptions. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific niche targeting Cloudflare Workers performance specifically, with distinct triggers like 'cold starts', 'CPU limits' that wouldn't overlap with general coding or other cloud platform 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 well-crafted performance optimization skill that delivers dense, actionable content efficiently. The code examples are executable and the organization allows quick navigation to specific optimization areas. The main weakness is the lack of explicit validation workflows to verify optimizations are effective.
Suggestions
Add a validation workflow showing how to measure performance before/after optimizations (e.g., 'Run benchmark.sh, apply fix, re-run benchmark.sh, verify CPU time decreased')
Include explicit checkpoints in the profiling section showing how to interpret timing results and decide if further optimization is needed
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, presenting code examples without explaining basic concepts Claude already knows. Every section delivers actionable information without padding or unnecessary context. | 3 / 3 |
Actionability | Provides fully executable TypeScript code examples throughout, with clear good/bad comparisons. The code is copy-paste ready with specific patterns for streaming, caching, batch processing, and profiling. | 3 / 3 |
Workflow Clarity | While individual techniques are clear, the skill lacks explicit validation checkpoints or feedback loops for optimization workflows. The 'Top 10 Performance Errors' table provides symptom-fix mapping but no verification steps to confirm fixes worked. | 2 / 3 |
Progressive Disclosure | Excellent structure with a quick wins section upfront, detailed sections for specific concerns, and clear one-level-deep references to specific reference files, templates, and scripts organized by use case. | 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.