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.
Install with Tessl CLI
npx tessl i github:secondsky/claude-skills --skill workers-runtime-apisOverall
score
90%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 Cloudflare Workers Runtime APIs domain with specific capabilities and explicit usage triggers. The description effectively covers both what the skill does and when to use it, including error scenarios. Minor weakness is potential overlap with generic web development skills due to common terms like 'HTTP requests' and 'caching'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete APIs (Fetch, Streams, Crypto, Cache, WebSockets, Encoding) and concrete actions (HTTP requests, streaming, encryption, caching, real-time connections). | 3 / 3 |
Completeness | Clearly answers both what (Cloudflare Workers Runtime APIs with specific capabilities) and when ('Use for HTTP requests, streaming, encryption...' provides explicit trigger guidance). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'HTTP requests', 'streaming', 'encryption', 'caching', 'real-time connections', 'WebSockets', plus error-related triggers like 'API compatibility', 'response handling', 'stream processing errors'. | 3 / 3 |
Distinctiveness Conflict Risk | While 'Cloudflare Workers' is specific, terms like 'HTTP requests', 'encryption', 'caching' could overlap with general web development or other cloud platform skills. The Cloudflare Workers context helps but generic terms create some conflict risk. | 2 / 3 |
Total | 11 / 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-structured, highly actionable skill that efficiently covers multiple runtime APIs with executable code examples. The quick reference table and 'Top 10 Errors Prevented' section add significant value. The main weakness is the lack of explicit validation/error recovery workflows for complex operations like caching and WebSocket handling.
Suggestions
Add explicit error handling and validation steps to the Cache API example (e.g., what to do if cache.put fails)
Include a try/catch wrapper with specific error handling in the Crypto API examples, as noted in the Critical Rules
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables for quick reference, avoiding explanations of concepts Claude already knows (like what HTTP or WebSockets are), and providing code examples without unnecessary preamble. | 3 / 3 |
Actionability | All code examples are fully executable TypeScript with proper imports and complete implementations. Patterns like fetchWithTimeout, fetchWithRetry, sha256, and HMAC signing are copy-paste ready. | 3 / 3 |
Workflow Clarity | While individual patterns are clear, the skill lacks explicit validation checkpoints for multi-step operations. The Cache API example shows a workflow but doesn't include error handling or validation steps for cache failures. | 2 / 3 |
Progressive Disclosure | Excellent structure with a quick reference table, quick start section, then detailed patterns. Clear signposting to reference files and templates with specific guidance on when to load each reference. | 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.