cloudflare-workers-runtime-apis
Cloudflare Workers Runtime APIs including Fetch, Streams, Crypto, Cache, WebSockets, and Encoding. Use for HTTP requests, streaming, encryption, caching, real-time connections, or encountering API compatibility, response handling, stream processing errors.
86
82%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
92%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 strong skill description that clearly identifies the domain (Cloudflare Workers Runtime APIs), lists specific capabilities, and provides explicit 'Use for...' trigger guidance. The main weakness is that several trigger terms (HTTP requests, streaming, encryption, caching) are generic enough to potentially conflict with non-Cloudflare-specific skills. Overall it is well-structured and informative.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and APIs: Fetch, Streams, Crypto, Cache, WebSockets, Encoding, along with specific use cases like HTTP requests, streaming, encryption, caching, and real-time connections. | 3 / 3 |
Completeness | Clearly answers both what (Cloudflare Workers Runtime APIs including Fetch, Streams, Crypto, Cache, WebSockets, Encoding) and when ('Use for HTTP requests, streaming, encryption, caching, real-time connections, or encountering API compatibility, response handling, stream processing errors'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'HTTP requests', 'streaming', 'encryption', 'caching', 'real-time connections', 'WebSockets', 'Cloudflare Workers', 'response handling', 'stream processing errors'. Good coverage of both API names and natural language terms. | 3 / 3 |
Distinctiveness Conflict Risk | While 'Cloudflare Workers' is a distinct niche, terms like 'HTTP requests', 'streaming', 'encryption', and 'caching' are quite broad and could overlap with general web development or Node.js skills. The Cloudflare Workers qualifier helps but the trigger terms themselves are generic enough to cause some conflict. | 2 / 3 |
Total | 11 / 12 Passed |
Implementation
72%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, well-structured reference skill covering six Cloudflare Workers runtime APIs with executable code examples and good progressive disclosure via reference file pointers. Its main weaknesses are moderate verbosity (the error table and some explanatory text could be trimmed) and lack of explicit validation/feedback loops in multi-step operations. The actionability is excellent with copy-paste ready TypeScript throughout.
Suggestions
Trim the 'Top 10 Errors Prevented' table to the 4-5 most non-obvious errors—many entries (like 'check content-type before parsing JSON') are things Claude already knows.
Add explicit validation checkpoints to multi-step patterns, e.g., for crypto operations: verify key import succeeded before signing, or for streaming: validate the response status before piping through transforms.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill covers six APIs with executable examples, but some content is somewhat verbose for Claude's level—the quick reference table, error prevention table, and resources section add bulk. The 'Critical Rules' section contains some obvious advice (e.g., handle errors in try/catch). However, most code examples earn their place. | 2 / 3 |
Actionability | All code examples are fully executable TypeScript with proper imports and types. Patterns like fetchWithTimeout, fetchWithRetry, sha256, HMAC signing, Cache API, and WebSocket Durable Objects are copy-paste ready with realistic implementations. | 3 / 3 |
Workflow Clarity | Individual patterns are clear, but there's no explicit multi-step workflow with validation checkpoints. The Cache API example shows a check-then-fetch pattern, but for operations like crypto or streaming large files, there are no validation/error-recovery feedback loops. The skill presents isolated patterns rather than sequenced workflows. | 2 / 3 |
Progressive Disclosure | The skill has a clear overview structure with a quick reference table, inline examples for common patterns, and well-signaled one-level-deep references to specific reference files and templates. The 'When to Load References' section provides excellent navigation guidance. | 3 / 3 |
Total | 10 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- secondsky/claude-skills
- Commit
88da5ff
- 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.