auto-research
Skill1 starsChanged 3 months agoMITView on GitHub
This is a thin human-facing router. Use skill.yaml as the source of truth for exact commands, inputs, outputs, and workflow chaining.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- dzhng/skillstheir own version, first seen Nov 15, 2026
- dzhng/jevgreptheir own version, first seen Nov 11, 2026
- thistleknot/skillstheir own version, first seen Nov 8, 2026
- Buddhilive/buddhi-clitheir own version, first seen Nov 1, 2026
- dzhng/yaptheir own version, first seen Oct 15, 2026
- transitive-bullshit/skillstheir own version, first seen Oct 13, 2026
Used with
Projects with it also use marketing-pages, close-spec and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
dzhngSkillmarketing-pages
Best-practice rulebook for a marketing site's pages, organized by page class — campaign landers, product pages, programmatic SEO trees, editorial. Use when writing or updating a landing/marketing page, wiring a campaign lander to an attribution identifier, changing site-wide nav/footer links, touching sitemap/robots/agent-readable surfaces, or auditing a public site's indexing, reachability, and conversion setup.
Also in 4 projects that use this
dzhngSkillclose-spec
When a spec under specs/<feature>/ is done shipping (a write-spec build, or any planned task that produced a spec), archive it to specs/done/ and rewrite it from a build-plan into a durable rationale — the why, the principles, the invariants — pointing back to the real code for the how. Use when implementation has landed and the plan no longer matches what shipped, or the user says a feature/spec is finished. Pairs with [write-spec](../write-spec/SKILL.md) (the plan this closes) and [review](../review/SKILL.md) (run before closing).
Also in 4 projects that use this
transitive-bullshitSkillcompare-screenshots
Compare screenshots against the intended design, distinguishing approved references from historical baselines. Use for iterative implementation matching, before/after visual review, objective image telemetry, or checking a lone capture for flat, empty, or badly framed content.
Also in 5 projects that use this
LucasMatuszewskiSkillaudit-agents
Audit and maintain agent configuration files (.claude/agents, AGENTS.md, CLAUDE.md, agent-memory). Checks for duplicates, outdated info, naming conflicts, wrong technical facts, and files over 200 lines. Fixes all issues and commits.
Also in 4 projects that use this
- +8 more from dzhng
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- dzhng/jevgrep★ 3.2ksame name
- dzhng/skills★ 1.5ksame name
- huytieu/COG-second-brain★ 1.3ksame name
- dzhng/yap★ 118same name
- maystudios/claude-skills★ 21same name
- transitive-bullshit/skills★ 5same name
- christyjacob4/claude-tricks★ 2same name
- Buddhilive/buddhi-cli★ 1same name
- braincandy-parallel/tamarindos-workflow-kit★ 0same name
- thistleknot/skills★ 0same 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
- binary-analysisSkill
- business-logicSkill
- campaignSkill
- cicd-securitySkill
- cloudSkill
- cors-csrfSkill
- coverageSkill
- cross-accountSkill
- domain-modelSkill
- enrichmentSkill
- 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
6 rules. 0 are common, 3 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 17
Start with scan to check all sources for changes since last scan.
- Very specific: line 18
Run batch for the full pipeline: scan -> extract -> deduplicate -> review.
- Very specific: line 19
Run review to score and filter extraction candidates.
- Distinctive: line 21
If a workflow has no script reference, treat it as a manual or tool-native workflow.
- Distinctive: line 31
Not applicable — this skill produces candidate data, not vulnerability findings.
- Distinctive: line 33
All candidates are traceable to their origin source for provenance.
“Common” is measured: kept by at least 6 in 10 of the 10 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.
Files
Auto Research
Overview
Imports and normalizes public security knowledge into the technique knowledge base. Watches public sources (OWASP WSTG, ASVS, nuclei-templates, CISA KEV, PayloadsAllTheThings, HackTricks, SecLists, PortSwigger Research, Bugcrowd VRT, and more), extracts candidate improvements, normalizes them into Technique KB schema, and proposes skill updates. Nothing goes live without validation. Everything is attributed.
This is a thin human-facing router. Use skill.yaml as the source of truth for exact commands, inputs, outputs, and workflow chaining.
Quick Reference
- Skill:
auto-research - Severity range:
info - Required tools:
python3,jq - Expected input files: none
- Scope check: not applicable — imports public data into local KB.
- Redaction: imported research and the source cache are local-only and must never be committed; keep the
cache/directory in.gitignoreand sanitize any captured tokens or credentials before sharing.
Workflow Selection
- Start with
scanto check all sources for changes since last scan. - Run
batchfor the full pipeline: scan -> extract -> deduplicate -> review. - Run
reviewto score and filter extraction candidates. - Runbooks: use
runbooks/. - If a workflow has no script reference, treat it as a manual or tool-native workflow.
Available Workflows
| Workflow | Purpose | Script paths | Primary outputs | Evidence |
scan | Scan all sources for new content since last check. | .claude/skills/auto-research/scripts/source_scanner.py | .claude/skills/auto-research/cache/scan_result.json | $OUTDIR/auto-research/evidence/ |
batch | Run full import pipeline scan extract deduplicate review. | .claude/skills/auto-research/scripts/batch_importer.py | .claude/skills/auto-research/cache/pipeline_log.json | $OUTDIR/auto-research/evidence/ |
review | Review pipeline output candidates. | .claude/skills/auto-research/scripts/candidate_reviewer.py | .claude/skills/auto-research/cache/batch_review.json | $OUTDIR/auto-research/evidence/ |
Evidence Required
- Not applicable — this skill produces candidate data, not vulnerability findings.
- Attribution is embedded in each candidate record (source_id, source_type, extracted_at, content_hash).
- All candidates are traceable to their origin source for provenance.
References
- Source of truth:
skill.yaml - Runbooks:
runbooks/ - OWASP WSTG: https://github.com/OWASP/wstg
- OWASP ASVS: https://github.com/OWASP/ASVS
- Nuclei Templates: https://github.com/projectdiscovery/nuclei-templates
- PayloadsAllTheThings: https://github.com/swisskyrepo/PayloadsAllTheThings
- HackTricks: https://github.com/HackTricks-wiki/hacktricks
- CISA KEV: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- PortSwigger Research: https://portswigger.net/research
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.

