CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

debug-workers

Use when a deployed Cloudflare Worker in this repository misbehaves or fails to deploy — osn-api, cire-api or a cire Worker — or when setting or rotating a Worker secret. Covers where to look first, the secret-setting trap for JSON and JWK values, why a secret change needs a redeploy, and the module-evaluation crash on a first deploy.

Quality

91%

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

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

An excellent traps-oriented reference: terse, symptom-first sections with mostly copy-paste-ready commands and well-signaled pointers to the wiki for bulk detail. The two weaker spots are fixes described prose-only (lazy thunks, routes TOML) and missing post-change verification in the secret workflows.

Suggestions

Add a complete copy-paste example for the two prose-only fixes: a lazy-thunk/request-time snippet for the module-evaluation crash and a full `[[env.production.routes]]` TOML block for the named-environment routes trap.

Add a verification step after secret changes (e.g., confirm with `wrangler secret list` or a test request) and after the forced redeploy, since section 3 notes warm isolates keep old behaviour.

Section 5 could name where the routes block goes (top level vs `env.production` in which file) to remove the last ambiguity for a first-time fixer.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence: no explanation of what Cloudflare Workers or wrangler are, and every sentence delivers either a trap, a command, or a pointer ("This skill holds the traps that cost time"). It matches the score-5 anchor — every token earns its place — rather than score 4, which would require trimmable over-explanation.

5 / 5

Actionability

Most guidance is copy-paste ready: `bunx wrangler tail <worker-name> --env production`, the grep/sed/printf secret pipe, `gh workflow run production-release.yml -f surfaces=osn_api -f force=true`, and `bun run test`. It falls short of score 5 because two fixes are described without complete code — the module-evaluation fix ("Move both into request-time code or lazy thunks") and the routes fix name `[[env.production.routes]]` without a full TOML block.

4 / 5

Workflow Clarity

Each section is a clearly sequenced conditional procedure keyed to a symptom ("When a request ... misbehaves, run `wrangler tail` ... before forming any theory"), and section 4 includes an explicit verification checkpoint ("Verify with a real `wrangler deploy`; `--dry-run` does not catch it"). It sits below score 5 because the secret-setting and redeploy flows lack a post-change verification step (e.g., confirming the secret landed or the behaviour changed), which matters since `wrangler secret put/delete` is a risky operation.

4 / 5

Progressive Disclosure

The body is under 50 lines with well-organized numbered sections, and bulk material (tier map, secrets checklist, deploy steps) is pointed out cleanly to `wiki/shared/production-deploy.md` and `wiki/shared/dev-environment.md` — one level deep, clearly signaled, no nesting. No bundle files exist to misorganize, so this matches the simple-skill case for a top score.

5 / 5

Total

18

/

20

Passed

Description

92%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 strong description: it states explicit 'use when' triggers, enumerates the specific failure modes the skill covers, and scopes itself tightly to this repository's Workers. The only gap is modest synonym coverage (e.g., 'wrangler', 'debug') that would catch more natural user phrasings.

Suggestions

Add one or two natural trigger synonyms such as 'wrangler' or 'debugging a Worker' so the description matches phrasings users commonly use when reaching for this skill.

DimensionReasoningScore

Specificity

The description lists multiple concrete, specific capabilities: "misbehaves or fails to deploy", "setting or rotating a Worker secret", "the secret-setting trap for JSON and JWK values", "why a secret change needs a redeploy", and "the module-evaluation crash on a first deploy" — comprehensive coverage of the skill's niche. It goes beyond score 4 ('several specific actions; minor gaps') because every clause names a distinct concrete capability rather than a generic category.

5 / 5

Completeness

Both halves are explicit: 'when' is stated directly ("Use when a deployed Cloudflare Worker in this repository misbehaves or fails to deploy ... or when setting or rotating a Worker secret") and 'what' is enumerated concretely ("Covers where to look first, the secret-setting trap ..., why a secret change needs a redeploy, and the module-evaluation crash"). This matches the score-5 anchor of explicitly answering both with concrete triggers, not the score-4 anchor where 'when' could be more specific.

5 / 5

Trigger Term Quality

Good natural keyword coverage: "Cloudflare Worker", "misbehaves", "fails to deploy", "setting or rotating a Worker secret" — phrases a user would plausibly say. It falls short of score 5's comprehensive synonym coverage because it omits common variations users would use, notably "wrangler", "debug", or "tail logs".

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche — Cloudflare Workers scoped to this repository's named surfaces ("osn-api, cire-api or a cire Worker") — with triggers unlikely to fire for unrelated skills. Conflict risk is minimal, matching the score-5 anchor for a distinct niche with distinct triggers.

5 / 5

Total

19

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

englishstreetventures/osn

Path

.claude/skills/debug-workers/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.