CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cloudflare-workers-expert

Expert in Cloudflare Workers and the Edge Computing ecosystem. Covers Wrangler, KV, D1, Durable Objects, and R2 storage.

Quality

69%

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/AI-Agents-Safe-Coding-Skills-claude/skills/cloudflare-workers-expert/SKILL.md

The canonical home for this skill is cloudflare-workers-expert in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a lean, well-structured reference with executable examples and genuinely edge-specific guidance rather than filler. Its main gaps are the absence of a sequenced develop-test-deploy workflow with validation, and thin coverage of Durable Objects and Queues that are named in the instructions.

DimensionReasoningScore

Conciseness

The body is efficient and dense with useful edge-specific facts (0ms cold starts, 1MB bundle limit, waitUntil()), but minor instances of over-explanation like "Remember that Workers use the Web standard Fetch API, not Node.js globals" and the persona opener could be trimmed.

4 / 5

Actionability

Two complete, executable code examples plus concrete commands ("npx wrangler dev", "wrangler tail") cover the common cases, but "Use Durable Objects for stateful coordination" and the Queues mention lack any code or configuration detail.

4 / 5

Workflow Clarity

The numbered Instructions are a list of tips rather than a sequenced development workflow, and no validation checkpoints or deploy step are given; sequence is present but checkpoints are missing, matching anchor 3.

3 / 5

Progressive Disclosure

Well-organized single-file skill with clear sections and no bundle to navigate; it sits above the simple-skill threshold with no reference split for deeper topics (Durable Objects patterns, Queues), keeping it at anchor 4 rather than 5.

4 / 5

Total

15

/

20

Passed

Description

56%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 clearly identifies a niche with strong product-name keywords, but it never states when the skill should be used and describes capabilities only generically ("Expert in", "Covers") rather than as concrete actions. Adding an explicit trigger clause and action verbs would raise both completeness and specificity.

Suggestions

Append a trigger clause such as "Use when deploying to Cloudflare Workers, configuring KV/D1/Durable Objects/R2 bindings, or debugging with Wrangler" so the 'when' is explicit rather than absent.

Replace generic framing ("Expert in", "Covers") with concrete actions, e.g., "Design, build, and deploy Cloudflare Workers; configure KV, D1, Durable Objects, and R2 bindings; debug with Wrangler."

Include common natural phrasings like "serverless", "edge functions", and "Cloudflare Pages" to improve trigger-term coverage against neighboring edge/serverless skills.

DimensionReasoningScore

Specificity

The description names the domain and specific technologies ("Covers Wrangler, KV, D1, Durable Objects, and R2 storage") but contains no concrete actions — "Expert in" and "Covers" are generic framing, matching the anchor for naming the domain with minimal or generic actions.

2 / 5

Completeness

It clearly answers "what" (Cloudflare Workers expertise across named products) but has no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Good keyword coverage with natural product terms users would say ("Cloudflare Workers", "Edge Computing", "Wrangler", "KV", "D1", "Durable Objects", "R2"), but common variations like "serverless", "deploy a Worker", or "Cloudflare Pages" are missing.

4 / 5

Distinctiveness Conflict Risk

Cloudflare-specific product names make the niche mostly distinct, but "Edge Computing ecosystem" is broad enough to overlap with generic edge/serverless skills; minor conflict risk, matching anchor 4 rather than 5.

4 / 5

Total

13

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills-claude/skills/cloudflare-workers-expert/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.