<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Issue Triage on Top AI Skills</title><link>https://topaiskills.com/tags/issue-triage/</link><description>Recent content in Issue Triage on Top AI Skills</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 19 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://topaiskills.com/tags/issue-triage/index.xml" rel="self" type="application/rss+xml"/><item><title>I Ran Matt Pocock's Triage Skill on a Stale Backlog of Issues</title><link>https://topaiskills.com/tutorials/guides/triage-backlog-narrative-experience/</link><pubDate>Wed, 19 Aug 2026 00:00:00 +0000</pubDate><guid>https://topaiskills.com/tutorials/guides/triage-backlog-narrative-experience/</guid><description>&lt;p&gt;I expected a fancy issue sorter and got a discipline. My plan was simple: take a repo whose issues nobody had touched in months and let the Triage skill from &lt;a href="https://github.com/mattpocock/skills" rel="nofollow" target="_blank"&gt;mattpocock/skills&lt;/a&gt; (223K stars, skills.sh #11, roughly 33,000 weekly installs) sort them out. What I actually ran into was a strict five-state machine, a verification gate that stopped me cold, and a comment disclaimer I&amp;rsquo;d never have thought to add. Here&amp;rsquo;s the walkthrough, including the part where the skill refused to move forward until I proved a claim.&lt;/p&gt;</description></item></channel></rss>