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.
68
83%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
The canonical home for this skill is triage in flightctl/ai-workflows
W011: Third-party content exposure detected (indirect prompt injection risk).
What this means
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Why it was flagged
The workflow reads Jira bug tracker issues authored by project users via the `/scan` and `/assess` phases, representing an outsider-submitted text feed (Jira ticket summaries and descriptions).
- Repository
- amir-yogev-gh/ai-workflows
- Path
triage/SKILL.md
- Commit
2bd6607
- Audited
- Security analysis
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.