LogoAwesome Skills
  • Search
  • Category
  • Tag
  • Blog
LogoAwesome Skills
LogoAwesome Skills

Discover Open-Source Agent Skills for AI Coding Assistants

Product

  • Search
  • Category
  • Tag
  • Blog

Resources

  • Claude Skill Docs
  • Antigravity Skills Docs

Tools

  • Claude Code
  • OpenCode
  • Cursor
  • Codex
  • Antigravity

Company

  • Privacy Policy
  • Terms of Service
  • Sitemap

©2026 Awesome Skills. All rights reserved.

Privacy PolicyTerms
Back to Skills

hunt-a-handle

Enumerate a username across hundreds of platforms with sherlock, maigret and WhatsMyName, then correlate and confirm which accounts genuinely belong to the same person. Use for username OSINT and handle enumeration, "find all accounts for this username", cross-platform account correlation, nickname and screen-name pivots, or turning a handle into a real name. Applies to fraud and synthetic-identity investigation, recruitment and marketplace scam checks, trust-and-safety enforcement, insider-thre

13stars1forksUpdated 8/13/2026
Developer Tools#identity-correlation#trust-and-safety#osint#privacy#investigation#username-enumeration

Security Assessment

Medium Risk(60/100)

Detected risks:

Account Correlation / Unmasking(The skill enumerates a username across hundreds of platforms and correlates the accounts to a single real person, a dual-use capability that can be used to unmask or profile individuals against their wishes., The risk is partly mitigated by a required authorized-scope step, a companion ethics document, and an explicit prohibition on interacting with the subject by logging in, messaging, or requesting follows.)
Security Score60/100

About hunt-a-handle

hunt-a-handle is an OSINT skill for username and handle investigation: enumerating a screen name across hundreds of platforms with tools like sherlock, maigret, and the WhatsMyName data set, then correlating and confirming which accounts genuinely belong to the same person. Its guiding thesis is that enumeration is the cheap half and confirmation is the real work — existence checks are HTTP heuristics that produce candidates, not identities, and pasting a tool's hit list into a report is the mistake that ruins these investigations.

The workflow starts with a required authorized-scope step (subject, objective, in-bounds selectors, out-of-bounds actions, jurisdiction) and a companion ethics document. It then guides enumerator choice (sherlock for breadth, maigret for parsed profile fields, WhatsMyName for readable match rules), systematic handle-variant generation (separator swaps, truncations, number suffixes, leetspeak, gamer-tag morphology), and a rigorous confirm-or-reject grading step using strong evidence (matching avatars verified against reverse image search, near-identical bios, self-declared cross-links, shared contact selectors) over weak signals. It documents common false positives — soft 404s, catch-all profile pages, CAPTCHA interstitials, squatted and impersonation accounts — and the collision problem where common handles map to many unrelated people.

It targets fraud and synthetic-identity investigators, recruitment and marketplace scam checkers, trust-and-safety teams, insider-threat analysts, and people auditing their own exposure. It explicitly forbids resolving ambiguity by logging in, messaging, or requesting follows. Despite these guardrails, the capability — correlating scattered accounts into a single real person — is dual-use and can be used to unmask or profile individuals, warranting elevated scrutiny.

FAQ

Which enumeration tools does it use?

sherlock for the largest fast existence sweep, maigret when you need parsed profile fields (display name, bio, IDs, location), the WhatsMyName detection list to see exactly why a hit fired, and manual visits for a known platform.

Why isn't a tool hit enough to confirm identity?

Enumerators only perform HTTP existence checks, which produce false positives from soft 404s, catch-all pages, CAPTCHA interstitials, and squatted or impersonation accounts; a hit is a candidate that must be confirmed with independent evidence like matching verified avatars or self-declared cross-links.

What are the scope restrictions?

It requires a written authorized-scope note and forbids interacting with the subject — no logging in, messaging, or requesting follows — because that is out of scope and reveals the investigator's presence.

What is the main limitation?

Handle collision: common or dictionary-word handles belong to many unrelated people, so confidence must scale with the handle's distinctiveness, and a bare handle match is the hypothesis being tested rather than evidence.

All Files

3 files
SKILL.md9.8 KB
View
reference/platform-leakage.md5.1 KB
View
reference/variant-patterns.md4.5 KB
View

Install hunt-a-handle

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill

Repository

useosint/osint-skills

Related Skills

dbt-sf-to-bq-translator

21,076

build-models

102

html-prototype

3,588

doc

448