cloudflare-kv
Store key-value data globally with Cloudflare KV's edge network. Use when: caching API responses, storing configuration, managing user preferences, handling TTL expiration, or troubleshooting KV_ERROR, 429 rate limits, eventual consistency, cacheTtl errors, wrangler types issues, or remote binding configuration.
87
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
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 technology (Cloudflare KV), lists concrete capabilities, provides explicit trigger guidance with the 'Use when:' clause, and includes specific error codes that users would naturally mention when troubleshooting. The description is concise yet comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Store key-value data globally', 'caching API responses', 'storing configuration', 'managing user preferences', 'handling TTL expiration', plus specific troubleshooting scenarios. | 3 / 3 |
Completeness | Clearly answers both what ('Store key-value data globally with Cloudflare KV's edge network') and when with explicit 'Use when:' clause listing multiple trigger scenarios including both use cases and error troubleshooting. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Cloudflare KV', 'caching', 'configuration', 'user preferences', 'TTL', plus specific error codes like 'KV_ERROR', '429 rate limits', 'eventual consistency', 'cacheTtl errors', 'wrangler types'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche around Cloudflare KV specifically. The combination of 'Cloudflare KV', 'edge network', and specific error codes like 'KV_ERROR' and 'wrangler types' makes it unlikely to conflict with generic caching or storage skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality, production-ready skill with excellent actionability - nearly every concept is backed by executable code. The workflow clarity is strong with explicit validation steps and error recovery patterns. The main weakness is length; the document could benefit from splitting detailed API reference and advanced patterns into separate files to improve progressive disclosure and reduce token usage for simpler use cases.
Suggestions
Consider splitting the API Reference section into a separate KV-API.md file, keeping only the most common operations (get, put, delete) in the main skill
Move Advanced Patterns (caching, metadata optimization, hot/cold keys) to a separate KV-PATTERNS.md file with a brief summary and link in the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy (e.g., limits table repeated in multiple contexts, consistency explanation appears in multiple sections). Some sections like 'Understanding Eventual Consistency' could be tightened, though overall it respects Claude's intelligence and avoids explaining basic concepts. | 2 / 3 |
Actionability | Excellent executable code examples throughout - all TypeScript snippets are copy-paste ready with proper imports, types, and error handling. CLI commands are complete with flags. Patterns like retry with exponential backoff and pagination helpers are fully implemented. | 3 / 3 |
Workflow Clarity | Clear multi-step workflows with explicit validation checkpoints. The pagination pattern explicitly warns about checking list_complete, the retry pattern has clear error recovery, and the production checklist provides a comprehensive verification sequence. Critical rules section clearly separates 'Always Do' from 'Never Do'. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and a logical flow from Quick Start to Advanced Patterns to Troubleshooting. However, at ~500 lines, some content (like the full API reference or advanced patterns) could be split into separate files. References to external docs are present but internal progressive disclosure could be improved. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (589 lines); consider splitting into references/ and linking | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 12 / 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.