CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

54

Quality

60%

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

62%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 lean and presents a clear, well-sequenced workflow with a genuine polling and review-feedback loop, but it stays at a high-level directive level without concrete commands or code, limiting how directly executable it is.

Suggestions

Add concrete commands for the actionable steps — e.g., the exact git commit/branch/PR commands and the specific way to summon and poll a Copilot review — so the guidance is copy-paste ready.

Define an explicit termination/validation checkpoint for 'review is clean' (e.g., zero unresolved comments and a passing CI check) and how to confirm the PR merged successfully.

Clarify the polling cadence and bound the loop (e.g., maximum retries or backoff) so the 'keep checking' instruction is unambiguous rather than an open-ended loop.

DimensionReasoningScore

Conciseness

The body is short and assumes Claude's competence, with almost no padding; the only mild over-explanation is 'do not give up, just keep polling until it lands', which restates the prior instruction.

4 / 5

Actionability

Steps are high-level directives ('Make the change', 'Summon a code review', 'merge the PR') with no concrete commands, no git invocation, and no example of how to summon or poll Copilot review, leaving the actual execution underspecified.

2 / 5

Workflow Clarity

The sequence is clearly numbered with an explicit polling loop and a feedback loop (address comments, re-review, repeat), which are strong checkpoints; it loses a point because 'clean review' and how to confirm merge success are not precisely defined.

4 / 5

Progressive Disclosure

This is a short single-purpose skill with no external references needed; the content is well-organized into one clear ordered list and a closing reminder, which satisfies the simple-skill exception for a top score.

5 / 5

Total

15

/

20

Passed

Description

58%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 explicitly pairs a what (issue-to-merged-PR flow) with a when clause and uses natural trigger terms, but its scope is unbounded ('anything to do in this repo'), which undercuts distinctiveness and risks the skill firing for nearly any task.

Suggestions

Tighten the trigger so it fires for clearly bounded work items rather than 'anything to do in this repo' — e.g., 'Use when a GitHub issue or ticket is assigned and you must ship it as a merged PR.'

Add concrete capability verbs that distinguish this from generic task skills (e.g., 'Reviews PR feedback, iterates on fixes, and merges once review is clean') rather than the abstract 'Handles everything end to end'.

Narrow trigger synonyms to terms tied to the issue/PR workflow (e.g., 'GitHub issue, Jira ticket, assigned task') to reduce overlap with unrelated skills.

DimensionReasoningScore

Specificity

Names the domain (ticket/issue/task/bug/request handling) and several concrete actions (address it, commit, open PR, merge), but 'Handles everything end to end' is somewhat generic and the actions read as a workflow rather than discrete capability verbs.

3 / 5

Completeness

It has both a clear 'what' (handles issue to merged PR end to end) and a 'when' clause ('Use this whenever there is a ticket...'), but the 'when' trigger is extremely broad and could be more specifically scoped.

4 / 5

Trigger Term Quality

'ticket, issue, task, bug, request' are natural terms users say, and it covers several synonyms; it slightly lacks file-type or platform-specific cues but provides good keyword coverage.

4 / 5

Distinctiveness Conflict Risk

'anything to do in this repo' is so broad it would overlap with virtually every other skill, posing high conflict risk; the only narrow signal is the PR/merge workflow, but the trigger scope is maximal.

2 / 5

Total

13

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
jbaruch/skill-issue-brickbox-start
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.