One-click install
npx skills add https://github.com/aaronjmars/aeon --skill disclosure-tracker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: disclosure-tracker
Source: https://github.com/aaronjmars/aeon/tree/main/skills/disclosure-tracker
Command: npx skills add https://github.com/aaronjmars/aeon --skill disclosure-tracker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents CRITICAL and HIGH vulnerability disclosure drafts from silently aging past responsible-disclosure timelines by auditing the pending vulnerability disclosure queue every day.

Core Features & Use Cases

  • Daily backlog scanning: Reads draft advisory files in memory/pending-disclosures/ to summarize queue state and age.
  • Accurate escalation classification: Determines whether items are truly pending by checking status hints and cross-referencing existing PR outcomes in memory/topics/pr-status.md when available.
  • Actionable notifications: Sends an urgent escalation message when items exceed age thresholds, otherwise sends a daily digest including cleanup candidates and any operator-only blockers.
  • Audit logging: Appends a structured daily entry to memory/logs/${today}.md to support traceability across runs.

Quick Start

Use the disclosure-tracker skill to produce a daily notification summarizing pending vulnerability disclosure drafts and escalating only those that have exceeded severity thresholds.

Frequently Asked Questions about disclosure-tracker

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

FAQPage Schema
How do I track pending vulnerability disclosure drafts to prevent stale security advisories?

Track pending vulnerability disclosure drafts by running daily audits that parse local advisory files in memory/pending-disclosures/ to summarize queue state and flag aged items. This prevents critical drafts from silently exceeding responsible disclosure timelines.

What is the best way to monitor security advisory age against responsible disclosure thresholds?

Monitoring security advisory age involves computing draft age against severity thresholds and cross-referencing GitHub PR status in memory/topics/pr-status.md. This determines if items remain truly pending or already have merged fixes in the repository.

How do I automate escalation alerts for high severity vulnerability disclosures?

Automate escalation alerts by applying deterministic notification logic via ./notify based on computed counts and age. Urgent escalation messages trigger only when drafts exceed severity thresholds, otherwise daily digests report cleanup candidates.

Can I audit pending security disclosures without manual checklist reviews?

Audit pending security disclosures automatically by scanning the memory/pending-disclosures/ backlog daily. The process classifies status hints, identifies aged drafts, and appends structured entries to memory/logs/ for traceability across runs.

Does responsible disclosure tracking work with existing GitHub PR status files?

Responsible disclosure tracking optionally cross-references existing PR outcomes in memory/topics/pr-status.md. This integration validates whether pending drafts already have corresponding fixes in the repository before triggering escalation notifications.

Why are my vulnerability disclosure drafts not getting escalated past responsible disclosure timelines?

Vulnerability disclosure drafts may not escalate if status hints indicate resolution or PR status cross-reference shows existing fixes. Escalation requires drafts to genuinely age past severity thresholds while remaining truly pending in the backlog.