pvr-watchlist

Detect GitHub private vulnerability reporting enablement on watchlisted repositories.

626|225|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/aaronjmars/aeon --skill pvr-watchlist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pvr-watchlist
Source: https://github.com/aaronjmars/aeon/tree/main/skills/pvr-watchlist
Command: npx skills add https://github.com/aaronjmars/aeon --skill pvr-watchlist

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, curl, grep, ls, tr.

What problem does it solve?

It prevents lost, time-sensitive private vulnerability reporting opportunities by regularly checking the security watchlist for when private vulnerability reporting (PVR) becomes enabled and then acting immediately.

Core Features & Use Cases

  • Weekly PVR probing of a security watchlist: Checks each repo for the GitHub private vulnerability reporting setting and detects status flips.
  • Automated advisory submission when possible: If a pending disclosure draft exists and the skill has the required permissions, it auto-submits; otherwise it escalates for manual submission.
  • Recoverability handling when drafts are lost: If PVR is enabled but the draft is missing, it flags the entry for re-research and triggers targeted re-scanning guidance.

Quick Start

Ask the system to run the pvr-watchlist skill once, optionally passing an owner/repo target to probe on demand instead of the full watchlist.

Frequently Asked Questions about pvr-watchlist

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

FAQPage Schema
How do I monitor GitHub private vulnerability reporting enablement across a security watchlist?

Monitor GitHub private vulnerability reporting by probing repositories via GitHub APIs to detect PVR status flips, then triggering follow-up actions like advisory submission or re-research escalation. This unattended weekly workflow ensures time-sensitive disclosure opportunities are not lost when settings change.

What happens if private vulnerability reporting is enabled but my advisory draft is missing?

When private vulnerability reporting is enabled but the draft is missing, the system flags the watchlist entry for re-research and triggers targeted re-scanning guidance. This recoverability handling prevents lost disclosure opportunities by escalating urgent re-research needs for manual recovery.

Can I auto-submit GitHub security advisories when private vulnerability reporting becomes enabled?

Auto-submitting GitHub security advisories requires a pending disclosure draft and the necessary GitHub API permissions. If both conditions are met, the advisory payload is constructed and submitted automatically; otherwise, the workflow escalates for manual submission to ensure timely disclosure readiness.

How does automated advisory submission handle permissions for private vulnerability reporting?

Automated advisory submission checks for required GitHub API permissions before attempting payload submission. If permissions are insufficient, the workflow escalates the pending disclosure draft for manual submission rather than failing silently, ensuring no private vulnerability reporting opportunity is missed.

Do I need GitHub CLI tools to run private vulnerability reporting checks on a watchlist?

Running private vulnerability reporting checks requires the gh CLI tool along with curl, grep, ls, and tr. These dependencies support probing GitHub APIs, reading and updating local memory watchlist state, and processing repository metadata to detect PVR enablement flips.

Why does my private vulnerability reporting workflow require local memory watchlist state?

Local memory watchlist state is required to track PVR status changes across weekly probes and detect enablement flips. Maintaining this state allows the workflow to compare previous and current GitHub API responses, identify when private vulnerability reporting becomes newly enabled, and recover staged disclosure drafts.