enrichment
Skill1 starsChanged 3 months agoMITView on GitHub
1 other project uses a version of this.
Adopted by
Most recently taken up by
- stevehansen/eidettheir own version, first seen Sep 24, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- stevehansen/eidet★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository50 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- agent-safetySkill
- ai-llmSkill
- apiSkill
- asset-graphSkill
- authSkill
- auto-researchSkill
- binary-analysisSkill
- business-logicSkill
- campaignSkill
- cicd-securitySkill
- cloudSkill
- cors-csrfSkill
- coverageSkill
- cross-accountSkill
- domain-modelSkill
- evaluation-harnessSkill
- file-uploadSkill
- graphql-auditSkill
- http-protocolSkill
- identity-domainSkill
- impact-verifierSkill
- meme-coin-auditSkill
- mobileSkill
- modern-browserSkill
- nuclei-scannerSkill
- oob-infraSkill
- osintSkill
- personaSkill
- plannerSkill
- privescSkill
- program-memorySkill
- race-conditionSkill
- rceSkill
- reconSkill
- reportingSkill
- sastSkill
- scope-managerSkill
- skill-scientistSkill
- sqliSkill
- ssrfSkill
- standard-catalogSkill
- technique-kbSkill
- traffic-corpusSkill
- triage-validationSkill
- vuln-intelSkill
- web3-auditSkill
- xssSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
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
- Very specific: line 14
Start with enrich to run a post-script on the next unenriched finding.
- Very specific: line 15
Use supplemental to re-run a different post-script on previously enriched findings (additive, history preserved).
- Very specific: line 16
Use list-enrichments to inspect existing enrichments without running anything.
- Very specific: line 28
Keep post_script name, prompt template, and output JSON in $OUTDIR/enrichment/enrichments.jsonl (and .bb/enrichments.jsonl if you use that …
≈ “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.
Files
Enrichment
Overview
Post-processing that enriches verified findings with report drafts, proof-of-concept diffs, and triage chips. Inspired by Kritt's post-scripts: each enrichment is a focused prompt that receives a single finding's context (vulnerability fields, trigger flow, file path) plus scan context, and produces typed output that is stored separately from the finding itself.
Quick Reference
- Skill:
enrichment - Severity range:
info,low,medium,high,critical - Required tools:
python3,jq - Expected input files:
output/*/impact-verifier/verified.jsonlorreports/ranked.jsonl - Scope check: passive enrichment (local file transformation, no network unless
--llmis set).
Workflow Selection
- Start with
enrichto run a post-script on the next unenriched finding. - Use
supplementalto re-run a different post-script on previously enriched findings (additive, history preserved). - Use
list-enrichmentsto inspect existing enrichments without running anything. - Runbooks:
runbooks/and select the closest phase when workflow names do not map 1:1.
Available Workflows
| Workflow | Purpose | Script paths | Primary outputs | Evidence |
enrich | Run a post-script on the next unenriched finding | .claude/skills/enrichment/scripts/enrich.py | $OUTDIR/enrichment/enrichments.jsonl | $OUTDIR/enrichment/evidence/ |
supplemental | Re-run a post-script on a previously enriched finding (additive) | .claude/skills/enrichment/scripts/enrich.py | $OUTDIR/enrichment/enrichments.jsonl | $OUTDIR/enrichment/evidence/ |
list-enrichments | List enrichments and their status | .claude/skills/enrichment/scripts/list_enrichments.py | stdout | — |
Evidence Required
- Store the finding's original
bounty_rankandvulnerability_typealongside the enrichment - Keep
post_scriptname, prompt template, and output JSON in$OUTDIR/enrichment/enrichments.jsonl(and.bb/enrichments.jsonlif you use that path via symlink) _reserved_reportoutput is markdown for the report tab;_reserved_pocis a git diff for the PoC tab;_chip_*outputs are short tags aggregated from all enrichments- Redact tokens and PII before sharing enrichments; evidence stays local-only
References
- Source of truth:
skill.yaml - Runbooks:
runbooks/ - Kritt post-scripts:
open-krittdocs-site/post-scripts/*.mdx(reserved keys, supplemental runs)
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.

