Security Advisory
Take a privately reported vulnerability through this repo's security advisory flow: board it as a draft card, check whether the code is this repo's server or the SDK underneath, accept or reject, fix it in the private fork, release, publish, then turn the card into public tracking. Use when a vulnerability is reported privately; when deciding whether an advisory is ours to fix or belongs to an SDK; when looking up or creating its private fork; when answering a reporter; or when a GHSA-titled board card needs handling.
Install
npx skills add modelcontextprotocol/servers --skill security-advisorygit clone --depth 1 https://github.com/modelcontextprotocol/servers.git /tmp/servers
mkdir -p ~/.claude/skills
cp -r /tmp/servers/.claude/skills/security-advisory ~/.claude/skills/security-advisoryPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Handling a security advisory Private vulnerability reporting is enabled on this repository and [`SECURITY.md`](../../../SECURITY.md) routes every report to it. A report therefore arrives as a **repository security advisory**, never as an issue, and for most of its life it must **not** become one: a public issue would disclose the vulnerability before a fix exists. Two steps in this flow are **outward-facing, and both stay human-only**: **accepting** an advisory (the reporter sees it) and **publishing** it (it becomes public, and there is no unpublish). Closing one as invalid, and every reply to a reporter, is outward-facing too. **An agent never takes any of these steps**: not once, not in bulk, not because a checklist said to. It investigates, prepares a recommendation, and a maintainer acts on it. Everything else here is mechanics. ⚠️ **Keep advisory details out of every public place**: issues, PRs, commit messages, branch names, and comments. Until an advisory is published, the only things safe to say in public about the backlog are **aggregate counts** (how many are in each state). A branch named after the bug, or a commit message that describes it, discloses it as surely as an issue would. Related: `/board-ops` holds the board IDs and the draft-card recipes, `/issue-create` gives the converted issue its labels and milestone (step 5), and `/pr-flow` opens the public PR that brings the fix to `v2/main` (step 5).
Details
- Skill name
security-advisory- Repository
- modelcontextprotocol/servers
- Path
.claude/skills/security-advisory/SKILL.md- Repo updated
- 18 November 2026
- Listed in
- heilcheng/awesome-agent-skills
FAQ
What does the Security Advisory skill do?
Take a privately reported vulnerability through this repo's security advisory flow: board it as a draft card, check whether the code is this repo's server or the SDK underneath, accept or reject, fix it in the private fork, release, publish, then turn the card into public tracking. Use when a vulnerability is reported privately; when deciding whether an advisory is ours to fix or belongs to an SDK; when looking up or creating its private fork; when answering a reporter; or when a GHSA-titled board card needs handling.
How do I install the Security Advisory skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add modelcontextprotocol/servers --skill security-advisory. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Security Advisory popular?
It lives in modelcontextprotocol/servers, which has 92,088 GitHub stars and 11,978 forks, and is included in 1 curated skill list.
Related skills
Board Ops
92kmodelcontextprotocol/servers
gh recipes for the Servers V2 project board (#43): add an issue's card, move its Status, set or change its Priority, delete a card, and recover from a deleted single-select option. Use when moving a card between columns; when setting Status or Priority; when an option ID is rejected; before editing a board field's options; or when cards lost their Status or Priority.
Client Smoke
92kmodelcontextprotocol/servers
Drive a locally built server with a real client: the Inspector CLI (scripted), the Inspector web UI (through Playwright) and an LLM client. Use when smoke-testing a server change; when calling a tool, reading a resource or getting a prompt from the command line; when choosing a protocol era; or when the Inspector CLI will not connect to, or misreads, a server command.
Issue Create
92kmodelcontextprotocol/servers
Create a tracked issue in this repo end to end — duplicate check, v2 label, type label, server-scope label, milestone, board card, Status and Priority. Use when asked to file, create, open or raise an issue; when picking its labels or its milestone; when checking whether one already exists; or when work discovered mid-task needs an issue of its own.
Persona It Admin
32kgoogleworkspace/cli
Administer IT — monitor security and configure Workspace.
Gstack
142kgarrytan/gstack
Picks the gstack skill that fits a request: planning, review, QA, shipping, docs, security or design. Use for: gstack, which gstack skill, route this with gstack. (gstack)
Security Threat Model
7.2ktech-leads-club/agent-skills
Repository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, and writes a concise Markdown threat model. Use when the user asks to threat model a codebase or path, enumerate threats or abuse paths, or perform AppSec threat modeling. Do NOT use for general architecture summaries, code review, security best practices (use security-best-practices), or non-security design work.
Browse the most popular Claude skills, all security skills, or write your own with the skills generator.