handle-security-advisory
Skill2 starsChanged 48 days agoAGPL-3.0View on GitHub
Coordinate the complete lifecycle of a confidential GitHub repository security advisory, from private vulnerability triage through isolated fixes, temporary private-fork integration, patched releases, coordinated disclosure, CVE handling, and post-publication verification. Use for GHSA reports, CVE/disclosure requests, multi-branch security backports, and advisory readiness or publication. Delegate ordinary PR review, scoped implementation, CI diagnosis, and generic release planning to their existing workflows. Never publish or merge merely because a report was reviewed.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- create-issues-and-epicsSkill
- diagnose-ci-failureSkill
- execute-issueSkill
- maintainer-inboxSkill
- repository-healthSkill
- review-pull-requestSkill
- upstream-compatibilitySkill
The file
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.