agentleFS
GTStaggGTStagg/project-eyas/.claude/skills/audit-remediations/SKILL.md

audit-remediations

Skill2 starsChanged 2 days agoMITView on GitHub

Use when deciding which patching scripts to add next, or auditing whether existing scripts still cover the live tenant. Hits the dev server's /vulnerabilities page, extracts every recommended-remediation string, buckets them by vendor/product, and prints uncovered remediations ranked by host count. Trigger phrases: "what scripts should we add next", "audit remediations", "what's uncovered", "which patches are surfaced".

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If the dev server isn't up, ask the user to run npm run dev (or docker compose up -d for the container path) first.

    line 15
  2. Distinctive:

    If the user wants the audit but the dev server isn't reachable (remote work, broken local stack), say so explicitly.

    line 38

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

audit-remediations

Re-pull the live Spotlight remediation surface and diff against the patching catalog.

Prerequisites

  • Dev server up at http://localhost:3000 (the /vulnerabilities?mode=newest&limit=2000 route renders the Spotlight fanout).
  • Falcon credentials valid in the running process — without them the page renders but every row is a 403.

If the dev server isn't up, ask the user to run npm run dev (or docker compose up -d for the container path) first. Don't try to start it for them.

What to run

bash .claude/skills/audit-remediations/run.sh

The script:

  1. curls the rendered HTML.
  2. Greps every Update <Vendor> <Product>... / Install patch for ... remediation string.
  3. Buckets by leading-vendor token (Mozilla, Microsoft Windows, Microsoft Office family, Notepad++, etc.).
  4. For each bucket, looks up whether a manifest entry covers it via matchRemediation (lib/eyas-tools/rtr/library.ts, called through scripts/rtr-library-cli.mjs match) on a representative string.
  5. Prints two ranked tables: covered (with the script id that handles it, host-count high-to-low) and uncovered (host-count high-to-low, candidate for next-batch curation).

Reading the output

  • High-count uncovered → strong candidates for the next /add-patch-script cycle.
  • Covered but suspicious → e.g. an app-firefox row showing thousands of hits across many version targets is fine; an app-7zip row with zero hits means the curated script may have stopped routing (vendor pattern drift) and is worth a manual check via /verify-patch.
  • Linux kernel CVE descriptions (Update the last_gc value..., Remove the xhci_initialize_ring_info()...) are noise from grepping CVE description text — the script filters obvious cases but expect a few in the uncovered list.

Note for one-off audits

If the user wants the audit but the dev server isn't reachable (remote work, broken local stack), say so explicitly. There is no offline fallback — Spotlight data is tenant-specific and not in the repo.

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.