CtrlK
BlogDocsLog inGet started
Tessl Logo

triage-issue

Intelligently triage bug reports and error messages by searching for duplicates in Jira and offering to create new issues or add comments to existing ones. When an agent needs to: (1) Triage a bug report or error message, (2) Check if an issue is a duplicate, (3) Find similar past issues, (4) Create a new bug ticket with proper context, or (5) Add information to an existing ticket. Searches Jira for similar issues, identifies duplicates, checks fix history, and helps create well-structured bug reports.

72

Quality

88%

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

77%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Highly actionable with a clear, checkpointed workflow, but undermined by verbosity from repeated output templates and a failure to offload existing reference material into the bundle files that already exist.

Suggestions

Replace the inline JQL search patterns and bug-report templates in the body with one-line links to references/search-patterns.md and references/bug-report-templates.md, keeping only a single representative example in SKILL.md.

Collapse the duplicated presentation/output blocks across Steps 4, 6, and the Examples section into one canonical template referenced where needed, removing redundant full mock outputs.

Trim the 'Tips for Effective Triage' Do/Don't lists since the workflow steps and Search Tips already convey the same guidance.

DimensionReasoningScore

Conciseness

The ~700-line body is mostly actionable but highly redundant — full presentation/output blocks are repeated across Steps 4, 6, and the Examples section, and the Tips section restates guidance already implied by the workflow.

2 / 3

Actionability

Provides executable JQL queries and real MCP tool calls (searchJiraIssuesUsingJql, createJiraIssue, addCommentToJiraIssue) with parameters, plus copy-paste summary and description templates and a required-fields retry path.

3 / 3

Workflow Clarity

A clearly sequenced Extract→Search→Analyze→Present→Execute→Confirm flow with an explicit checkpoint ("CRITICAL: Always present findings and wait for user decision") and an error-recovery loop for custom required fields.

3 / 3

Progressive Disclosure

Two reference files exist (references/search-patterns.md, references/bug-report-templates.md) but the body never links to them and instead duplicates their JQL and template content inline, making the SKILL.md monolithic.

2 / 3

Total

10

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 that states concrete capabilities, gives explicit when-to-use triggers, and stays distinct and third-person. No significant weaknesses.

DimensionReasoningScore

Specificity

Names multiple concrete actions — "searching for duplicates in Jira", "create new issues", "add comments", "checks fix history", "create well-structured bug reports" — rather than vague language.

3 / 3

Completeness

Explicitly answers both what (search, identify duplicates, check fix history, create/comment) and when via the numbered "When an agent needs to" trigger list.

3 / 3

Trigger Term Quality

Trigger clauses like "Triage a bug report or error message" and "Check if an issue is a duplicate" map to natural user phrasings such as "triage this error" and "is this a duplicate".

3 / 3

Distinctiveness Conflict Risk

Occupies a clear Jira bug-triage niche with distinct triggers, written in third person, making conflicts with other skills unlikely.

3 / 3

Total

12

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (701 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository
openai/plugins
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.