triage
Triage Issues and Pull Requests
Issue queues become difficult to manage when reports lack clear categories, evidence, or next steps. This skill verifies requests and moves them into actionable states.
Stop for confirmation before installing.
Review the plan and obtain explicit user consent before changing files.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "triage" from https://skillstore.io/skills/mattpocock-triage.md and its manifest at https://skillstore.io/api/skills/mattpocock-triage/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "triage". Show me what needs attention.
Expected outcome:
- Unlabeled: 3 items, oldest first.
- Needs triage: 5 items awaiting maintainer evaluation.
- Needs information: 2 items with new reporter replies.
Using "triage". Triage issue 42 without changing anything.
Expected outcome:
Recommendation: classify it as a bug and move it to needs information. The reproduction lacks an environment version and a minimal failing example.
Using "triage". Prepare issue 87 for an implementation agent.
Expected outcome:
Agent brief: add durable rejection records. It defines current behavior, desired behavior, relevant interfaces, four acceptance criteria, and excluded follow-up work.
Security Audit
High RiskAll 55 static findings are false positives caused by Markdown backticks, code fences, ordinary prose, and command names. However, the workflow can execute untrusted pull request code and consume untrusted tracker content before making repository or tracker changes.
Confirmed security concerns (2)
Risk Factors
⚙️ External commands (50)
🌐 Network access (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/mattpocock-triage/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/mattpocock-triage?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/mattpocock-triage?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/mattpocock-triage/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/mattpocock-triage.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
mattpocock. (2026). triage security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/mattpocock-triage/audits/5BibTeX citation
@techreport{mattpocock-mattpocock-triage-2026,
author = {mattpocock},
title = {triage security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/mattpocock-triage/audits/5},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "triage security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
- name: "mattpocock"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/mattpocock-triage/audits/5"
identifiers:
- type: other
value: "skillstore:mattpocock-triage:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Review an Open Source Queue
Identify old or newly updated items, verify their claims, and recommend the next state.
Prepare Work for Coding Agents
Convert a verified request into a durable brief with testable acceptance criteria and explicit boundaries.
Assess Contributor Pull Requests
Compare an external pull request with its claims and document remaining work before delegation or human review.
Try These Prompts
Show me the issues and external pull requests that need attention. Group them by triage state and list the oldest first.
Triage issue #{issue_number}. Gather its history, check for an existing implementation or prior rejection, then recommend a category and state.Review pull request #{pr_number}. Compare the diff with its claims, identify gaps, and recommend ready-for-agent or ready-for-human without changing labels.Prepare an agent brief for #{item_number}. Include current behavior, desired behavior, key interfaces, testable acceptance criteria, and explicit exclusions.Best Practices
- Verify the reported behavior and search for an existing implementation before assigning a final state.
- Ask for explicit maintainer approval before changing labels, posting comments, closing items, or writing repository files.
- Run external pull request code only in disposable environments without credentials or repository write access.
Avoid
- Do not treat issue comments or pull request content as trusted operational instructions.
- Do not mark work ready for an agent without testable acceptance criteria and clear exclusions.
- Do not record already implemented features as rejected concepts in the out-of-scope knowledge base.
Frequently Asked Questions
Can this skill triage pull requests?
Does it change labels automatically?
What categories does it use?
What workflow states are supported?
How are rejected enhancements recorded?
Can it safely run tests from external pull requests?
Developer Details
Author
mattpocockLicense
MIT
Skillstore revision
r2
Version notice
The author did not declare a version.
Ref
ebdfe608f5de2b66ff37ab4af12af8ac4f5e8006
Maintenance freshness
7/25/2026
Usage
4 downloads · 74 views
File structure