CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

fix-the-ticket

Use this for any ticket, issue, task, bug, or request in this repo — takes it from issue to done.

Quality

68%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/fix-the-ticket/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 presents a clear, well-sequenced workflow with genuine feedback loops (polling for review, iterating until clean) in a lean, appropriately sized single file. Its main weakness is actionability: the two hardest steps — summoning a Copilot review and checking whether it has returned — are given as prose with no concrete commands or mechanisms.

Suggestions

Add the concrete command(s) for the non-obvious steps, e.g., how to request a Copilot review (such as the relevant gh CLI invocation or UI action) and how to check its status (e.g., gh pr view / gh api for review comments).

Add a pre-merge checkpoint for CI/mergeability (e.g., verify checks pass before merging) to close the last validation gap in the workflow.

Remove the redundant closing 'Use your judgment' line since 'When in doubt, treat it as a real change' already states the same guidance.

DimensionReasoningScore

Conciseness

The body is lean (~25 lines) with no explanations of concepts Claude already knows. Minor trimming is possible: the 'err on the full flow' guidance is stated twice ('When in doubt, treat it as a real change' and the closing 'Use your judgment — but err on the side of the full flow'). This matches anchor 4 ('Efficient; minor instances of over-explanation that could be trimmed') rather than 5, where every token would earn its place.

4 / 5

Actionability

The sequence is concrete ('Create a branch, make the change, commit, and open a pull request') but the non-obvious mechanics are unspecified — there is no command for 'Summon a Copilot code review on the PR' or for checking whether the review has landed. This matches anchor 3 ('Some concrete guidance but incomplete; missing key details'); anchor 4 requires concrete code or commands, which are absent.

3 / 5

Workflow Clarity

The numbered sequence 1-5 is clear, with an explicit poll loop (step 3: 'wait about 10 seconds and check again') and a fix → re-review feedback loop with a termination condition ('Repeat until the review is clean'). Validation is present (the review loop), so the destructive-operation cap does not apply; minor gaps (no CI/merge-readiness check before merging, no mechanism for checking review status) keep it at anchor 4 rather than 5.

4 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, with no bundle files and no content that belongs in external references. Per the simple-skill guideline, well-organized short-form content with no need for external references scores 5.

5 / 5

Total

16

/

20

Passed

Description

48%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 has strong, explicit trigger coverage for the ticket/issue domain but its capability statement is a vague slogan, and its deliberate claim over 'any task or request' creates high conflict risk with more specific repo skills. It tells Claude when to fire but barely what will happen.

Suggestions

Replace 'takes it from issue to done' with 2-3 concrete actions, e.g., 'Triages the ticket, implements the fix, opens a pull request, and iterates through Copilot code review until clean before merging.'

Narrow the trigger scope or add distinguishing qualifiers so it does not capture every conceivable request (e.g., specify it applies to substantive code/doc changes, and name what it does differently from plain implementation).

Add missing natural trigger synonyms such as 'story', 'work item', or 'feature request' to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain ('ticket, issue, task, bug, or request') but its only action claim is the generic slogan 'takes it from issue to done' — no concrete actions like branching, opening a PR, or running a review are stated. This matches the anchor 'Names the domain but actions are minimal or generic'; it does not reach 3 because no 1-2 concrete actions are listed.

2 / 5

Completeness

The 'when' is explicit ('Use this for any ticket, issue, task, bug, or request in this repo'), but the 'what' is vague — 'takes it from issue to done' describes an outcome, not what the skill actually does. It sits between anchor 2 (vague what, no when) and anchor 4 (both present, one could be more explicit), so the even-adjacent midpoint 3 applies.

3 / 5

Trigger Term Quality

'ticket, issue, task, bug, or request' provides five natural synonyms users would actually say, giving good keyword coverage. It falls short of 5 because a few common variations are missing (e.g., 'story', 'work item', 'feature request').

4 / 5

Distinctiveness Conflict Risk

'any ticket, issue, task, bug, or request in this repo' claims essentially all repo work, so it would trigger ahead of more specific skills (review, docs, commit-message skills). It is scoped to repo work items rather than entirely generic, matching anchor 2 ('Very broad; high overlap risk with many similar skills') rather than 1.

2 / 5

Total

11

/

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

jbaruch/skill-issue-brickbox

Path

.claude/skills/fix-the-ticket/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.