magpie-security-issue-sync

Synchronize security issues across GitHub, mailing lists, and pull requests.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill synchronizes security issues across GitHub, mailing lists, and pull requests, ensuring that all relevant information is up-to-date and consistent.

Core Features & Use Cases

  • Issue Synchronization: Synchronize security issues from a tracker with GitHub discussions, mailing lists, and PRs.
  • State Proposals: Propose label, milestone, assignee, and field updates based on current state.
  • Next Step Recommendations: Provide recommendations on the next steps in handling the issue, including CVE allocation and advisory publication.
  • Bulk Mode: Sync multiple issues in parallel for efficient triage.

Quick Start

Run the skill by entering 'magpie-security-issue-sync [issue-number]' where '[issue-number]' is the number of the security issue you want to sync.

Frequently Asked Questions about magpie-security-issue-sync

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

FAQPage Schema
How do I synchronize security issues between GitHub and mailing lists?

You can sync security issues by running the skill with a specific issue number to automatically synchronize data across GitHub, mailing lists, and pull requests.

What is the best way to automate vulnerability management across multiple issue trackers?

Automating vulnerability management across trackers is handled by bulk syncing multiple security issues in parallel, proposing label, milestone, and assignee updates based on the current state.

Do I need the gh CLI to sync security issues and pull requests?

Yes, the gh CLI is required for GitHub API access and Python is needed for script execution to run security issue synchronization between trackers and pull requests.

Can I propose label and assignee updates when synchronizing security issues?

Yes, the synchronization process proposes label, milestone, assignee, and field updates based on the current state of the security issue across connected systems.

How does security issue synchronization handle next steps like CVE allocation?

Security issue synchronization provides recommendations on next steps for handling issues, including guidance on CVE allocation and advisory publication based on the proposed state updates.

Does security issue synchronization work for bulk triage of multiple vulnerabilities?

Yes, security issue synchronization supports a bulk mode that syncs multiple issues in parallel, enabling efficient triage and consistent state updates across connected systems.

Related Skills