CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

resolve-issue

Take a dwmkerr.com GitHub issue to a reviewable PR in one pass, with before/after evidence. Use when the user says "resolve issue

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

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.

An exemplarily lean, actionable skill: every command is copy-paste ready, the six-step sequence has real validation checkpoints and safety gates, and the content is appropriately self-contained with no bundle files. The single gap is the absence of an explicit error-recovery loop for the build and social-image checks.

DimensionReasoningScore

Conciseness

Every line is instruction; no concept Claude already knows is explained, and details like "PR bodies can't take attachments through the API" and "The repo is public, so the image is too" are non-obvious facts that earn their tokens. Lean and efficient throughout.

5 / 5

Actionability

Concrete executable commands throughout: `gh issue view <n>`, `git switch -c fix/<n>-<slug> origin/main`, `hugo --minify`, the `sips`/`base64`/`gh api` upload sequence, and a complete PR body template. Placeholders like `<n>` and `<slug>` are appropriate parameterization, and the only flexible step (before/after capture) varies by issue, so the flexibility is justified.

5 / 5

Workflow Clarity

A clear numbered 1-6 sequence with explicit validation checkpoints ("must build", "must pass (CI runs it too)"), a decision gate in step 1 (comment instead of coding for large/ambiguous issues), and a "Merge or release only when the user asks" safety gate. Falls short of 5 because there is no error-recovery feedback loop telling Claude what to do when the hugo build or social-image check fails.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent) and none are needed: the skill is a single self-contained workflow in well-organized numbered sections, well under any threshold where splitting would help. Per the simple-skill scoring note, well-organized sections alone merit 5.

5 / 5

Total

19

/

20

Passed

Description

90%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 concise, distinctive description that clearly states what the skill does and when to use it, with literal user-quoted trigger phrases. Its only weakness is that it summarizes the workflow as one composite action rather than naming the specific actions involved.

DimensionReasoningScore

Specificity

"Take a dwmkerr.com GitHub issue to a reviewable PR in one pass, with before/after evidence" names a concrete domain and a concrete outcome, but describes a single composite action rather than listing several specific actions, and omits the internal steps (build, checks, image upload, PR format). Fits anchor 3 (domain plus 1-2 concrete actions, not comprehensive); not 4 because it does not list several specific actions.

3 / 5

Completeness

Explicitly answers both what ("Take a dwmkerr.com GitHub issue to a reviewable PR in one pass, with before/after evidence") and when ("Use when the user says...\" with three concrete trigger phrases). Matches anchor 5 exactly.

5 / 5

Trigger Term Quality

"Use when the user says \"resolve issue #N\", \"fix issue #N\" or \"zero-shot this\"" quotes the literal natural phrases a user would say, covering the main phrasings of the request. Matches the comprehensive-coverage anchor 5.

5 / 5

Distinctiveness Conflict Risk

Scoped to a single named repository (dwmkerr.com) with distinctive quoted trigger phrases; a clear niche with minimal risk of triggering for unrelated skills. Matches anchor 5.

5 / 5

Total

18

/

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

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

dwmkerr/dwmkerr.com

Path

.claude/skills/resolve-issue/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.