CtrlK
BlogDocsLog inGet started
Tessl Logo

wrangler

Wrangler CLI: Workers, KV, tail, deploy, account routing.

68

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

93%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 concise, highly actionable Wrangler reference with executable commands and sensible pre-flight validation for account-sensitive and deploy operations; its only soft spot is that guidance is reference-styled rather than a fully sequenced workflow with explicit recovery loops.

DimensionReasoningScore

Conciseness

The body is lean throughout — tight bullets in Defaults and Pitfalls, concrete commands in Quick Commands — and assumes Claude's competence without explaining concepts Claude already knows, matching the anchor 5 'every token earns its place' example.

5 / 5

Actionability

Quick Commands provides copy-paste-ready, fully executable invocations (whoami, deploy, tail, kv key list/get) and Pitfalls gives specific actionable constraints (use 0.999 not 1, run serially to avoid SQLITE_BUSY), matching anchor 5.

5 / 5

Workflow Clarity

Validation checkpoints are present for destructive/account-sensitive work ("wrangler whoami before account-sensitive work", the Account Check stop-and-ask rule), but the body is organized as a reference rather than a fully numbered sequenced workflow with explicit error-recovery loops, fitting anchor 4 rather than 5.

4 / 5

Progressive Disclosure

The skill is under 50 lines, has no bundle files and no need for external references, and is cleanly organized into Defaults, Pitfalls, Quick Commands, and Account Check sections, meeting the simple-skill exception for anchor 5.

5 / 5

Total

19

/

20

Passed

Description

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

A tight, domain-specific description that names concrete capabilities and is highly distinct, but it lacks any explicit 'when to use' trigger guidance, which caps its completeness at 3.

Suggestions

Add a 'Use when…' clause naming natural triggers, e.g. 'Use when working with Cloudflare Workers, Wrangler deploys, KV/R2/D1, or account routing.'

Expand the capability list to include R2, D1, Queues, and secrets so the description matches the body's full scope.

Include the synonym 'Cloudflare' and the 'wrangler.toml' trigger so users phrasing it differently still match.

DimensionReasoningScore

Specificity

The description lists several concrete Wrangler capability areas ("Workers, KV, tail, deploy, account routing"), but omits others covered in the body (R2, D1, Queues, secrets, bindings), leaving minor gaps consistent with anchor 4 rather than comprehensive anchor 5.

4 / 5

Completeness

It clearly states what the skill covers but provides no "Use when…" clause or equivalent trigger guidance, so per the judging guidelines completeness is capped at 3 (clear what, missing when).

3 / 5

Trigger Term Quality

"Wrangler CLI", "Workers", "KV", "tail", and "deploy" are natural terms users would say, but common synonyms like "Cloudflare" and "wrangler.toml" are missing, matching anchor 4 (good coverage, a few natural terms absent).

4 / 5

Distinctiveness Conflict Risk

"Wrangler CLI" plus "Workers", "KV", and "account routing" define a clear, distinct niche tied to Cloudflare tooling with minimal conflict risk against other skills.

5 / 5

Total

16

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
steipete/agent-scripts
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.