triage

Bulk-triage unresolved Jira bugs with AI-driven recommendations and an interactive HTML report. Scan also loads recently resolved bugs for regression matching in analyze. Use when triaging a project backlog, prioritizing bug fixes, identifying candidates for automated fixing, or reviewing stale issues. For one bug in depth (no artifacts), use /assess. Activated by commands: /run, /start, /scan, /analyze, /report, and /assess.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

The canonical home for this skill is triage in flightctl/ai-workflows

Quality

Content

78%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 clean, concise orchestrator/router with a solid error-feedback loop, but it is structurally broken as progressive disclosure: every reference points to non-existent skills/*.md and guidelines.md files, and the real scripts/*.py bundle is orphaned and never linked.

Suggestions

Create the referenced skills/run.md, skills/assess.md, skills/start.md, skills/scan.md, skills/analyze.md, skills/report.md, and guidelines.md — or repoint the body at the files that actually exist.

Reference the actual scripts/ bundle (e.g. scripts/scan.py, scripts/prepare_analysis.py, scripts/render_report.py) from the relevant phase files so the implementation is reachable from SKILL.md.

Add a per-phase validation checkpoint (e.g. after scan, verify analyzed.json exists before proceeding to analyze) to turn the generic stop-on-failure rule into explicit per-step gates.

Dimension	Reasoning	Score
Conciseness	Lean ~26-line router with no padding and no explanation of concepts Claude already knows; every line directs a concrete action and earns its place.	5 / 5
Actionability	Routing guidance is concrete and executable ('read skills/run.md and follow it', 'start with skills/start.md to validate access'), but the body delegates all real work to referenced files and contains no triage logic or code itself, leaving minor gaps.	4 / 5
Workflow Clarity	Clear numbered routing sequence with an explicit feedback loop ('If a step fails... stop and report... Do not advance... Offer to retry or escalate'), but validation is a single generic stop rule rather than per-phase checkpoints, a minor gap versus the fully-checklisted anchor.	4 / 5
Progressive Disclosure	The overview-to-detail intent is sound (one-level-deep, clearly signaled references to skills/{phase}.md and guidelines.md), but those referenced files do not exist in the bundle while the actual scripts/*.py bundle is never referenced, so the navigation is broken and disconnected from the real bundle.	3 / 5
	Total	16 / 20 Passed

Description

87%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 strong description: it states concrete capabilities, gives explicit 'Use when...' trigger guidance, and carves out a distinctive Jira-triage niche. The only weakness is mild genericness in 'AI-driven recommendations' and a few missing natural-term synonyms.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'Bulk-triage unresolved Jira bugs', 'AI-driven recommendations', 'interactive HTML report', 'loads recently resolved bugs for regression matching' — but 'AI-driven recommendations' is slightly generic, leaving minor gaps versus the comprehensive anchor.	4 / 5
Completeness	Explicitly answers both what ('Bulk-triage unresolved Jira bugs with AI-driven recommendations and an interactive HTML report') and when ('Use when triaging a project backlog, prioritizing bug fixes... or reviewing stale issues') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural phrases users would say are present — 'triaging a project backlog', 'prioritizing bug fixes', 'reviewing stale issues' — giving good coverage, but a few natural synonyms/variants are missing versus the comprehensive anchor.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Jira bug backlog triage) with distinct triggers — 'Jira bugs', 'project backlog', 'stale issues' — and minimal overlap risk with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: amir-yogev-gh/ai-workflows
Path: triage/SKILL.md
Commit: 2bd6607

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.