CtrlK
BlogDocsLog inGet started
Tessl Logo

wrangler

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

65

Quality

77%

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 ./skills/wrangler/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is concise, highly actionable, and well-structured for a simple CLI skill, with copy-paste commands and targeted pitfalls. Its only gap is the absence of an explicit sequenced workflow with validation feedback loops for destructive operations.

Suggestions

Add a short numbered workflow for risky operations (e.g., deploy: whoami -> confirm account -> deploy -> verify) with an explicit validate/retry checkpoint.

Make the destructive-operation safeguards (never print secrets, stop and ask on account mismatch) part of an explicit checklist rather than only a pitfall.

DimensionReasoningScore

Conciseness

The body is lean and efficient — Defaults, Pitfalls, and Quick Commands each carry concrete guidance with no padding or explanation of concepts Claude already knows, so every token earns its place.

3 / 3

Actionability

Quick Commands provides fully executable, copy-paste-ready invocations (`npm exec --yes --package wrangler -- wrangler ...`) with concrete flags and values (e.g., `--sampling-rate 0.999`).

3 / 3

Workflow Clarity

Guidance is organized as defaults/pitfalls/commands with one stop-and-ask checkpoint in Account Check, but there is no explicit numbered workflow with validate-then-retry feedback loops for risky operations like deploy or secret handling.

2 / 3

Progressive Disclosure

At under 50 lines with no need for external references, the well-organized sections (Defaults, Pitfalls, Quick Commands, Account Check) satisfy the rubric's allowance for simple skills to score 3 on progressive disclosure.

3 / 3

Total

11

/

12

Passed

Description

67%

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 is specific and distinctive, naming concrete Wrangler actions, but it omits any explicit 'Use when...' trigger guidance, capping completeness and weakening trigger-term quality. A short trigger clause would raise both.

Suggestions

Add an explicit 'Use when ...' clause naming natural user phrases (e.g., 'Use when deploying or tailing Cloudflare Workers, managing KV/R2/D1, or routing between accounts').

Include common trigger terms users actually say, such as 'Cloudflare', 'secrets', and 'bindings'.

DimensionReasoningScore

Specificity

Lists multiple concrete actions in the domain — 'Workers, KV, tail, deploy, account routing' — matching the anchor for enumerating several specific concrete actions rather than vague language.

3 / 3

Completeness

It clearly states what the skill does but provides no 'Use when...' clause or equivalent explicit trigger guidance, which the rubric guidelines cap at 2.

2 / 3

Trigger Term Quality

Relevant keywords exist ('deploy', 'tail', 'KV', 'Workers') but the colon-list format omits common natural variations a user would say ('Cloudflare', 'secrets', 'bindings') and lacks a phrase-shaped trigger.

2 / 3

Distinctiveness Conflict Risk

'Wrangler CLI' with Cloudflare-specific terms (Workers, KV, account routing) is a clear niche with distinct triggers unlikely to overlap with other skills.

3 / 3

Total

10

/

12

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.