agentleFS
Geoffe-GaGeoffe-Ga/well-worn-tools/.claude/skills/cve-remediation/SKILL.md

cve-remediation

Skill0 starsChanged 5 months agoNo licenceView on GitHub

Remediate dependency vulnerability scanner failures by verifying live package registry data and upgrading instead of suppressing. Use when an SCA / CVE tool fails or files an alert: npm audit, pnpm audit, yarn audit, pip-audit, safety, Snyk, Dependabot, Trivy, Grype, OSV-Scanner, audit-ci, cargo audit, govulncheck, bundler-audit, Renovate, or any CI step reporting a CVE / GHSA / OSV advisory. The first action is ALWAYS to look up the latest published version on the live registry — training data is months stale and almost never knows the current version. Suppression, ignore, or allowlist entries are the absolute last resort, only after upgrade and override paths are proven unavailable; surrounding GitHub issues and justification docs do not by themselves count as remediation. Do NOT use for vulnerabilities in your own application code (use security skill), general linter or type checker bypasses (use max-quality-no-shortcuts skill), or unrelated CI failures (use ci-debugging skill).

  • Installs packages

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

11 rules. 0 are common, 9 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 9

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

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.