recon
Skill18 starsChanged 4 days agoMITView on GitHub
Walk an application portal without submitting to collect every question, word limit, upload slot, file rule and extra field, and save reusable notes (a playbook) for that platform. Use "/recon <opportunity id>" before tailoring or applying.
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
- lohi-ai/babysittheir own version, first seen Nov 14, 2026
- hejdujir/docker-claude-codetheir own version, first seen Nov 11, 2026
Used with
Projects with it also use reporting, osint and 3 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
SentrySkillcreate-pr
Create pull requests following Sentry conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review. Follows Sentry's code review guidelines.
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
- sophonfinance-wq/finance-automation-portfolio★ 16same name
- blamechris/chroxy★ 8same name
- g-baskin/recon★ 8same name
- franco-bianco/claude-skills★ 4same 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.
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 27 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
- Distinctive: line 8
Read CLAUDE.md first. Use Sonnet.
- Very specific: line 11
Read the platform playbook if one exists: playbooks/<platform>.md (platform from the record, or the portal's domain, e.g.
- Very specific: line 13
Read the anthropic-skills:chrome-browser skill, load the Chrome tools in one ToolSearch call, open apply_url in a new tab.
- Distinctive: line 21
every question: prompt verbatim, limit, unit (words/characters), required or optional
- Distinctive: line 22
every upload slot: label, required, accepted formats, max MB, max pages, which document type it maps to
- Very specific: line 37
Create or update playbooks/<platform>.md with portal mechanics only — no personal data: navigation, autosave and session timeout, odd …
“Common” is measured: kept by at least 6 in 10 of the 27 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
Portal recon
Read CLAUDE.md first. Use Sonnet. Nothing is submitted during recon.
python -m scholar opp show <id>andpython -m scholar app prepare <id>.- Read the platform playbook if one exists:
playbooks/<platform>.md(platform from the record, or the portal's domain, e.g.varbi,jobbnorge,universityadmissions). - Read the
anthropic-skills:chrome-browserskill, load the Chrome tools in one ToolSearch call, openapply_urlin a new tab. - Login or account creation needed → tell the applicant: "Please sign in (or create the account) at
<host>in the Chrome tab and tell me when you're done." Never type passwords or codes. - Move through the form with the portal's own Next/Save buttons. Saving a draft is fine; never press the final Submit. Don't fill fields, except a choice that reveals later pages (e.g. picking the programme) — ask the applicant first.
- Collect:
- every question: prompt verbatim, limit, unit (words/characters), required or optional
- every upload slot: label, required, accepted formats, max MB, max pages, which document type it maps to
- other fields that need information not in the profile
- declarations/consent text, any payment step, how referees are handled (does entering a referee email them immediately?), the deadline and time zone shown in the portal
- Save to the record — write
data/tmp/patch.json:{"application": {"questions": [{"prompt": "...", "limit": 300, "unit": "words", "required": true, "category": "motivation"}], "upload_rules": [{"slot": "CV", "type": "cv", "formats": ["pdf"], "max_mb": 2, "max_pages": 2, "required": true}], "requires_account": true, "platform": "varbi", "referee_process": "Referees are emailed when you press Save on page 4", "extra_fields": ["How did you hear about the programme?"]}}python -m scholar opp patch <id> data/tmp/patch.jsonQuestioncategory: motivation, career_goals, research, leadership, challenge, impact, why_country, academic, diversity, other. - Create or update
playbooks/<platform>.mdwith portal mechanics only — no personal data: navigation, autosave and session timeout, odd widgets (date pickers, searchable dropdowns), upload behaviour, when referee emails go out, where the final Submit is. - Report to the applicant: the questions, information you still need from them, the documents
required, and that
/tailor <id>is next.
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.

