magpie-security-issue-triage

Automate initial security tracker issue triage into six disposition classes.

79|76|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/apache/magpie --skill magpie-security-issue-triage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: magpie-security-issue-triage
Source: https://github.com/apache/magpie/tree/main/skills/security-issue-triage
Command: npx skills add https://github.com/apache/magpie --skill magpie-security-issue-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, mcp, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the initial triage of security tracker issues, significantly reducing the time spent by security team members on this process.

Core Features & Use Cases

  • Automated Issue Triage: Categorizes security issues into six disposition classes: VALID, DEFENSE-IN-DEPTH, INFO-ONLY, INVALID, PROBABLE-DUP, and FIX-ALREADY-PUBLIC.
  • User Confirmation Required: Ensures human oversight by requiring explicit confirmation before posting any triage-proposal comments.
  • Integration with Other Skills: Complements other Magpie security skills like security-issue-import, security-cve-allocate, security-issue-invalidate, and security-issue-deduplicate.

Quick Start

To triage all open issues with the label 'needs triage', simply run the command 'magpie-security-issue-triage triage'.

Frequently Asked Questions about magpie-security-issue-triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate security issue triage on GitHub?

Automate security issue triage by running the 'magpie-security-issue-triage triage' command to categorize open GitHub issues labeled 'needs triage' into six disposition classes, requiring explicit user confirmation before posting proposals.

What security issue classifications are used during automated triage?

Automated security triage classifies issues into six categories: VALID, DEFENSE-IN-DEPTH, INFO-ONLY, INVALID, PROBABLE-DUP, and FIX-ALREADY-PUBLIC, identifying security model violations, duplicates, and misframed reports.

Do I need the gh CLI to handle security issue workflows?

Yes, you need the 'gh' CLI for GitHub access and the Gmail MCP for reporter follow-up checks to execute the security issue triage workflow and verify issue dispositions.

Can I post triage comments automatically without human oversight?

No, automated security issue triage requires explicit user confirmation before posting any triage-proposal comments to ensure human oversight of the security workflow.

How does automated triage handle duplicate or invalid security reports?

Automated triage identifies duplicates as PROBABLE-DUP and misframed issues as INVALID, streamlining security workflows by filtering out invalid reports and issues with public fixes before team review.

Related Skills