agentleFS
markmhendricksonmarkmhendrickson/neotoma/.claude/skills/advisory/SKILL.md

advisory

Skill38 starsChanged 2 months agoMITView on GitHub

File, maintain, and close security advisories. Keeps docs/security/advisories/, docs/security/practices.md, and GitHub Security Advisories (GHSA) in sync. Two modes — new (file advisory) and close (mark fixed).

  • Commits and pushes

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

15 rules. About 0 are common, 11 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈11

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to manage the full security advisory lifecycle.

    line 16
  2. Distinctive:

    MUST: commit advisory files, README update, and practices.md update atomically in a single commit.

    line 39
  3. Very specific:

    MAY: use SKIP_TESTS=1 on commit *only* when pre-existing, unrelated test failures on the branch would otherwise block the pre-commit hook …

    line 40
  4. Distinctive:

    If any field is unclear, ask before proceeding.

    line 62
  5. Very specific:

    Create docs/security/advisories/<slug>.md using this structure:

    line 66
  6. Very specific:

    Add a row to the index table in docs/security/advisories/README.md:

    line 141
  7. Distinctive:

    For each gate the advisory reveals a gap in: add a row to that gate's "Known gaps" section describing the gap and referencing the advisory …

    line 151
  8. Distinctive:

    For each gate extension the advisory motivates: add a row to that gate's "History" table with the date, change description, and advisory …

    line 153
  9. Distinctive:

    In the "Advisory → hardening linkage" section: add a bullet for the new advisory linking it to the specific gate work it motivated (or a …

    line 155
  10. Very specific:

    If the API call fails due to token scope, instruct the user to open manually at: https://github.com/<owner>/<repo>/security/advisories/new

    line 205
  11. Distinctive:

    Use when a fix has shipped in a release and the advisory record needs to be closed.

    line 228
  12. Distinctive:

    Add the fix release date to the Disclosure Timeline table

    line 244
  13. Distinctive:

    Update the "Advisory → hardening linkage" bullet to show the gate work as completed

    line 255
  14. Distinctive:

    Add a closure comment on each:

    line 264
  15. Distinctive:

    If the GHSA is open, update it to reflect the fix and set it to published if disclosure is appropriate:

    line 272

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Advisory

Use this skill to manage the full security advisory lifecycle. It enforces atomicity — advisory files, the README index, practices.md, GitHub issues, and the GHSA are updated together so nothing drifts.

Two modes:

  • /advisory new — File a new advisory for a discovered vulnerability
  • /advisory close <slug> <version> — Mark an existing open advisory fixed in a release

When to Use

  • A vulnerability has been identified and needs a disclosure record
  • A fix has shipped for an open advisory and the record needs to be closed out
  • practices.md is out of date with the current advisory set

Invoke with /advisory new or /advisory close <slug> <version>.


Constraints (apply throughout)

  • MUST NOT include attack vector specifics, exploit steps, or payload details in any repo markdown file (docs/security/advisories/, practices.md, GitHub issues). Those belong in the GHSA, which is private until coordinated disclosure.
  • Sanitized content describes: what category of bug, what prerequisites, what data is accessible, what the severity is, and what the fix entails — without explaining how to perform the access.
  • MUST commit advisory files, README update, and practices.md update atomically in a single commit.
  • MAY use SKIP_TESTS=1 on commit only when pre-existing, unrelated test failures on the branch would otherwise block the pre-commit hook for this docs-only change. Do not skip tests when your change could plausibly affect them.

Mode: /advisory new

Step 1: Gather inputs

Collect the following before writing anything:

FieldNotes
Slug<YYYY-MM-DD>-<short-kebab-description> — date is discovery date
CVE classCategory of vulnerability (e.g., tenant isolation bypass, auth middleware gap)
Affected version(s)Which released tag(s) contain the bug
PrerequisitesWhat the attacker needs — be specific but sanitized
ImpactWhat data/functionality is exposed — no exploit steps
SeverityLow / Medium / High with reasoning
Remediation approachWhat the fix entails — high level
Tracking issuesGitHub issue numbers for fix and gate gaps (create if they don't exist)
Gate gapWhich security gate(s) failed to catch this and why

If any field is unclear, ask before proceeding.

Step 2: Draft the advisory file

Create docs/security/advisories/<slug>.md using this structure:

# Advisory: <Title>

**Advisory ID:** <slug>
**Date:** <YYYY-MM-DD>
**Severity:** <Low|Medium|High> (<brief rationale>)
**Status:** <Fixed in vX.Y.Z | Open — fix tracked in #N, #M>

---

## CVE Class

<One paragraph: vulnerability category, what makes it exploitable, regression class if known.>

---

## Affected Versions

- vX.Y.Z

<Fixed in / Not yet fixed.>

---

## Prerequisites

<Numbered list of what an attacker needs. Sanitized — no exploit steps.>

---

## Impact

<What data or functionality is exposed. Sanitized — no exploit steps.>

---

## Severity

**<Low|Medium|High>** <reasoning paragraph>

<Escalation condition if applicable.>

---

## Remediation

<Fix approach. Reference tracking issues. No exploit details.>

---

## Disclosure Timeline

| Date | Event |
|------|-------|
| <date> | Vulnerability identified |
| <date> | Advisory filed |
| TBD | Fix released |

---

## Tracking Issues

- **#N** — <description>

---

## Gate Gap

<Which gate(s) did not catch this. Why. What the extension entails. Reference tracking issue for gate fix.>

Step 3: Update the advisories README index

Add a row to the index table in docs/security/advisories/README.md:

| [<slug>](./<slug>.md) | <Short title> | vX.Y.Z | <Severity> (<rationale>) | <Open — fix tracked in #N | Fixed in vX.Y.Z> |

Step 4: Update practices.md

Open docs/security/practices.md and make the following updates:

  1. For each gate the advisory reveals a gap in: add a row to that gate's "Known gaps" section describing the gap and referencing the advisory slug.
  2. For each gate extension the advisory motivates: add a row to that gate's "History" table with the date, change description, and advisory slug.
  3. In the "Advisory → hardening linkage" section: add a bullet for the new advisory linking it to the specific gate work it motivated (or a waiver if no gate change is needed).
  4. If the advisory introduces an escalation condition (e.g., single-tenant assumption): update the "Cross-cutting practices" section to document it.

The practices.md update must reflect the current state — pending gate work is noted as "Pending, tracked in #N", not omitted.

Step 5: File sanitized GitHub issues

For each required fix and gate gap that doesn't already have a tracking issue:

gh issue create \
  --title "<sanitized title>" \
  --body "<sanitized description — no attack vector details>" \
  --label "security"

Issues describe what to fix (add per-user scoping, extend gate coverage) without explaining how the vulnerability works.

Step 6: Commit atomically

Stage all changed files and commit:

git add docs/security/advisories/<slug>.md \
        docs/security/advisories/README.md \
        docs/security/practices.md

SKIP_TESTS=1 git commit -m "docs(security): file advisory <slug>

<one-line summary of what the vulnerability is>

Advisory covers: <CVE class>. Affected: <version>. Severity: <level>.
Fix tracked in #N. Gate gap tracked in #M.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>"

Step 7: Open a GitHub Security Advisory (GHSA)

This is where full technical details can go — the GHSA is private until coordinated disclosure.

gh api repos/{owner}/{repo}/security-advisories --method POST \
  --field summary="<title>" \
  --field description="<full technical description including prerequisites and exploit details>" \
  --field severity="<low|medium|high|critical>" \
  --field vulnerabilities='[{"package":{"ecosystem":"npm","name":"neotoma"},"vulnerable_version_range":"= X.Y.Z"}]'

If the API call fails due to token scope, instruct the user to open manually at: https://github.com/<owner>/<repo>/security/advisories/new

and provide the full content to paste.

Record the GHSA URL in the advisory file's Disclosure Timeline once it's created.

Step 8: Push and open a PR

git push origin <branch>
gh pr create \
  --title "docs(security): file advisory <slug>" \
  --base main \
  --body "Files sanitized advisory <slug> (category: <vuln class>, affected: <versions>, severity: <level>). No attack-vector specifics, exploit steps, or payloads — those live in the private GHSA. See docs/security/advisories/<slug>.md."

The PR description must not expose attack vector details either — treat it as public.


Mode: /advisory close <slug> <version>

Use when a fix has shipped in a release and the advisory record needs to be closed.

Step 1: Verify the fix is released

gh release view <version>

Confirm the release tag exists and the fix commits are included.

Step 2: Update the advisory file

In docs/security/advisories/<slug>.md:

  • Change **Status:** Open — fix tracked in #N to **Status:** Fixed in <version>
  • Fill in the Remediation section with what was actually done (commits, approach)
  • Add the fix release date to the Disclosure Timeline table

Step 3: Update the README index

Change the Status cell for the advisory row from Open — fix tracked in #N to Fixed in <version>.

Step 4: Update practices.md

For each gate extension that was implemented as part of the fix:

  1. Move pending items from "Known gaps" to the "History" table with the date they landed
  2. Update the "Advisory → hardening linkage" bullet to show the gate work as completed

Step 5: Close tracking issues

gh issue close <fix-issue-number> --reason completed
gh issue close <gate-gap-issue-number> --reason completed

Add a closure comment on each:

gh issue comment <number> --body "Fixed in <version>. Advisory: docs/security/advisories/<slug>.md"

Step 6: Update the GHSA

If the GHSA is open, update it to reflect the fix and set it to published if disclosure is appropriate:

gh api repos/{owner}/{repo}/security-advisories/<ghsa-id> --method PATCH \
  --field state="published"

Step 7: Commit and push

git add docs/security/advisories/<slug>.md \
        docs/security/advisories/README.md \
        docs/security/practices.md

SKIP_TESTS=1 git commit -m "docs(security): close advisory <slug> — fixed in <version>

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>"

git push origin <branch>
gh pr create --title "docs(security): close advisory <slug>" --base main

File and gate reference

FilePurposeUpdated by this skill
docs/security/advisories/README.mdIndex of all advisoriesEvery invocation
docs/security/advisories/<slug>.mdPer-vulnerability recordnew and close
docs/security/practices.mdLiving gate posture and hardening historyEvery invocation
scripts/security/protected_routes_manifest.jsonRoute auth manifestOnly if fix touches manifest
tests/security/auth_topology_matrix.test.tsAuth-topology testOnly if gate gap fix lands

Checklist before committing

  • Advisory file has no attack vector details (prerequisites and impact are sanitized)
  • README index row added/updated
  • practices.md updated: gate gaps noted, history rows added, hardening linkage bullet present
  • GitHub issues filed for fix and gate gap (if not pre-existing)
  • All three docs staged in the same commit
  • GHSA opened or queued for manual creation
  • PR description is sanitized (public-safe)

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.