recon
Skill0 starsChanged 3 days agoMITView on GitHub
Evaluate an external repository, library, or tool against the current project. Use for adoption decisions, architecture comparisons, or requests to explore and borrow from another project.
32 other projects use a version of this.
Adopted by
Most recently taken up by
- brennantim/claude-skillstheir own version, first seen Nov 16, 2026
- moiz-73/glassboxtheir own version, first seen Nov 16, 2026
- Sn4kyGit/qa-agent-blueprinttheir own version, first seen Nov 16, 2026
- Birdiz/skillstheir own version, first seen Nov 16, 2026
- rafaym1/scholarship-desktheir own version, first seen Nov 16, 2026
- hejdujir/docker-claude-codetheir own version, first seen Nov 11, 2026
Used with
Projects with it also use reporting, osint and 2 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.
GitHubSkillreporting
Report formatting guidelines for gh-aw workflows (header levels, collapsible details, run-ID links)
Also in 3 projects that use this
JosBen74Skillosint
OSINT-sökning och informationsinhämtning från öppna källor för Länsstyrelsen VG
Also in 4 projects that use this
samklee1Skillweb-pentest
Orchestrates authorized web app pentesting on Kali Linux using Opus sub-agents with difficulty-aware planning (TDA/EGATS), browser-first exploration, iterative verification, two-layer review (per-sub-agent + phase-level), optional cross-model gap audit (GPT/codex via codex-plugin-cc), and enforced KB updates. Trigger on: pentesting, penetration testing, web app security assessment, vulnerability assessment, OWASP testing, PTES, attack surface mapping, API security testing, pentest reporting, or 'help me test this app'. NOT for network-only pentesting, malware analysis, reverse engineering, or CTFs.
Also in 3 projects that use this
NVIDIASkillresearch
Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.
Also in 3 projects that use this
Other versions32 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 32
- codexstar69/bug-hunter★ 546same name
- briiirussell/cybersecurity-skills★ 489same name
- gavraz/recon★ 263same name
- skyf0xx/gambit★ 29same name
- wycats/ai-plugin★ 19same name
- wycats/vscode-ai-plugin★ 19same name
- rafaym1/scholarship-desk★ 18same name
- sophonfinance-wq/finance-automation-portfolio★ 16same name
- blamechris/chroxy★ 8same name
- g-baskin/recon★ 8same name
22 more not listed
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 repository30 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- agent-first-docsSkill
- analytics-reviewSkill
- architectSkill
- autopilotSkill
- browseSkill
- create-prSkill
- design-uiSkill
- foremanSkill
- harness-auditSkill
- humanizer-viSkill
- image-genSkill
- implementSkill
- investigateSkill
- marketing-videoSkill
- perf-auditSkill
- plan-draftSkill
- qaSkill
- release-prdSkill
- releaseSkill
- review-prSkill
- semantic-decisionSkill
- setup-projectSkill
- teamSkill
- telemetry-reviewSkill
- testSkill
- token-auditSkill
- triageSkill
- ui-auditSkill
The file
Files
recon
Evaluate the external target against the local project's concrete problem —
primary sources only (source code, official docs, releases, license) — and
recommend copy, refactor, rebuild, or pass, accounting for
maintenance, security, dependency, and migration cost. Separate attractive
ideas from code worth importing; preserve attribution and license
obligations. Implement only when the user requested adoption and the
recommendation is clear.
Output
STATUS: DONE | DONE_WITH_CONCERNS | NEEDS_CONTEXT
VERDICT: STEAL(<approach>) | PASS
SUMMARY: <fit, costs, recommendation>
NEXT: <implementation action or none>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.

