triage-cleanup
Janitor for the auto-triage pipeline. Scans tickets left CLAIMED (carrying the auto-triage claimMarker) whose claim is older than a threshold — a run that crashed, timed out, or was abandoned — and reconciles each to its true state: a ticket that already has an open auto-PR is healthy (→ IN_REVIEW, or left CLAIMED — never reaped), one with an attached plan issue goes to NEEDS_HUMAN, and only a genuinely orphaned one (no PR, no plan) returns to the queue for retry. Use as `triage-cleanup [<minutes>]`, or when asked to unstick / reap stale auto-triage claims. Tracker- and project-agnostic; reuses the triage config + tracker binding. Read-mostly: only posts a comment and a status transition — never edits code, never opens PRs.
65
82%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
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 and processes Jira/Atlassian or GitHub tickets and their comments/attachments via tracker bindings, exposing the agent to outsider-authored free text.
- Repository
- MrToxy/claude-skills
- Commit
66c7102
- 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.