CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

fix-the-ticket

Use this whenever there is a ticket, issue, task, bug, request, or anything to do in this repo. Handles everything end to end from issue to merged PR.

Quality

69%

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

65%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 is a lean, well-sequenced workflow with a genuine review feedback loop, but it is instructionally thin: no concrete commands for review summoning, comment checking, or merging, an unbounded polling loop with no failure exit, and no pre-merge validation. It reads clearly but leaves key execution details to guesswork.

Suggestions

Add the concrete commands for each step — e.g. the exact way to summon a Copilot review ('gh copilot review' or the actual invocation), checking review comments ('gh pr view --comments'), and merging ('gh pr merge --squash').

Bound the polling loop with an exit condition (e.g. 'if no review arrives after N checks, report back and stop') instead of 'do not give up, just keep polling until it lands'.

Add a pre-merge validation checkpoint — verify CI checks pass and the PR is mergeable before merging, since merging is irreversible.

DimensionReasoningScore

Conciseness

The body is short (~20 lines) with no concept explanations and assumes Claude's competence, but step 4 has trimmable redundancy — 'do not give up, just keep polling until it lands' restates 'Keep checking in a loop until the review is posted'. It sits between lean (5) and efficient-with-minor-trims (4), closer to the latter due to that padded phrasing.

4 / 5

Actionability

The sequence is specific about ordering (commit, open PR, review, address comments, merge) but provides no concrete commands or tool invocations — no command for 'summon a code review on the PR (Copilot)', no command to check for review comments, and no merge command. For an instruction-only skill this is incomplete executable guidance, matching level 3 rather than 4.

3 / 5

Workflow Clarity

A clear numbered sequence with a review-to-fix-to-re-review feedback loop exists, but merging — an irreversible operation — has no verification checkpoint (no CI or status check before merge), and the polling loop is explicitly unbounded ('do not give up, just keep polling until it lands') with no exit condition if the review never arrives. Per the destructive-operation cap, this cannot exceed 3.

3 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, needs no external references (none exist in the bundle), and is organized as a clean numbered workflow — meeting the simple-skill exception for a top score.

5 / 5

Total

15

/

20

Passed

Description

57%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 an explicit and well-populated trigger clause with natural terms like 'ticket', 'issue', and 'bug', but the capability statement is generic ('Handles everything end to end') and the catch-all 'anything to do in this repo' creates major conflict risk with other skills. It communicates the niche but over-claims scope.

Suggestions

Replace 'Handles everything end to end' with concrete actions, e.g. 'Reads the ticket, implements the fix, commits, opens a PR, iterates on code review, and merges.'

Remove the catch-all 'or anything to do in this repo' and bound the trigger to the concrete nouns (ticket, issue, task, bug, request) so it does not fire for every possible repo activity.

Add natural trigger variations such as 'fix', 'work item', or 'pull request request' to round out keyword coverage.

DimensionReasoningScore

Specificity

The description names the domain ('from issue to merged PR') but the capability statement is generic — 'Handles everything end to end' lists no concrete actions (no mention of committing, opening PRs, review iteration, or merging as discrete actions). It matches 'names the domain but actions are minimal or generic', not level 3, which requires 1-2 concrete named actions.

2 / 5

Completeness

Both parts are present: an explicit 'when' ('Use this whenever there is a ticket, issue, task, bug, request...') and a 'what' ('Handles everything end to end from issue to merged PR'). It is not level 5 because the 'what' is vague ('handles everything'), and not level 3 because the 'when' clause is explicit rather than merely implied.

4 / 5

Trigger Term Quality

'ticket, issue, task, bug, request' are natural terms users would say, giving good keyword coverage. It falls short of level 5 because common variations are missing and 'anything to do in this repo' is a generic catch-all rather than a genuine synonym or extension-based trigger.

4 / 5

Distinctiveness Conflict Risk

The clause 'or anything to do in this repo' makes the trigger extremely broad, creating high overlap risk with virtually any repo-related skill. It sits above level 1 only because the concrete nouns (ticket, bug, issue) do carve out a recognizable ticket-workflow niche.

2 / 5

Total

12

/

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-start

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.