CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cloudflare-kv

Cloudflare Workers KV global key-value storage. Use for namespaces, caching, TTL, or encountering KV_ERROR, 429 rate limits, consistency issues.

58

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/cloudflare-kv/skills/cloudflare-kv/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 highly actionable skill body with excellent executable code and a clear quick-start sequence, weakened by duplicated content that belongs in its own reference files and a Resources section pointing at non-existent bundle paths. Tightening the overview and removing dead references would lift both conciseness and progressive disclosure.

Suggestions

Trim the inline 'KV API Methods' section to a few key examples and defer full signatures to references/workers-api.md, and cut the 'What Is Workers KV?' and 'Eventual Consistency' sections that duplicate reference content.

Remove or actually create the templates/, examples/, /cloudflare-kv:* commands, and agent entries listed in Resources — currently they point at files that do not exist in the bundle.

Add an explicit validation step to the Quick Start, e.g., step 4: run scripts/test-kv-connection.sh to verify the namespace and binding work before proceeding.

DimensionReasoningScore

Conciseness

The body is mostly practical (dense Critical Rules, concrete use cases), but the 'What Is Workers KV?' section explains concepts Claude already knows, and the ~60-line API methods section plus the Limits and Eventual Consistency sections largely duplicate references/workers-api.md and references/limits-quotas.md, matching the 'mostly efficient but could be tightened' anchor.

3 / 5

Actionability

Fully executable, copy-paste-ready guidance throughout: concrete wrangler CLI commands, complete put/get/delete/list snippets with options, and five complete use-case implementations covering the common cases. Clearly matches the top anchor.

5 / 5

Workflow Clarity

The Quick Start is a clearly numbered 3-step sequence (create namespace → configure binding → basic operations), but no validation checkpoint is wired into the flow even though scripts/test-kv-connection.sh and validate-kv-config.sh exist in the bundle — a minor validation gap below the explicit-checkpoint anchor 5.

4 / 5

Progressive Disclosure

References are well-signaled via a 'When to Load References' section and all 7 reference files plus 5 scripts exist, but the full API method reference is inlined rather than deferred to the existing workers-api.md, and the Resources section lists templates/, examples/, commands, and agents that do not exist in the bundle — dead references and misplaced inline content match the anchor 3 pattern.

3 / 5

Total

15

/

20

Passed

Description

65%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.

The description has a strong explicit trigger clause with good natural keywords and a clear product niche, but it tells the model nothing about what the skill does — only what the product is. Adding 1-2 concrete capability verbs would raise both specificity and completeness.

Suggestions

Add concrete capability verbs to the 'what' clause, e.g., 'Create and manage KV namespaces, implement get/put/delete/list operations, configure wrangler bindings, and troubleshoot consistency and rate-limit errors.'

Include one or two common synonyms users would say, such as 'key-value store' or 'wrangler kv', to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain ('Cloudflare Workers KV global key-value storage') and feature nouns (namespaces, caching, TTL) but contains no concrete action verbs describing what the skill does, matching the anchor 'Names the domain but actions are minimal or generic'. A score of 3 would require 1-2 concrete actions, which are absent.

2 / 5

Completeness

An explicit 'Use for...' clause provides concrete when-triggers, satisfying the trigger requirement; the 'what' names the product domain but not what the skill actually does (setup, operations, troubleshooting), keeping it below the fully explicit anchor 5.

4 / 5

Trigger Term Quality

Good natural keyword coverage including 'namespaces', 'caching', 'TTL', 'KV_ERROR', '429 rate limits', and 'consistency issues' — phrases users would naturally say. A few natural terms/synonyms (e.g., 'key-value store', 'wrangler kv') are missing from the description, so it falls short of the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

'Cloudflare Workers KV' plus distinct error triggers (KV_ERROR, 429) establishes a clear niche, but generic terms 'caching' and 'TTL' create minor overlap risk with general caching/Redis storage skills, so it sits between the mostly-distinct anchor 4 and minimal-conflict anchor 5.

4 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

Total

15

/

16

Passed

Repository

secondsky/claude-skills

Path

plugins/cloudflare-kv/skills/cloudflare-kv/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.