$npx -y skills add AlexAI-MCP/hermes-CCC --skill sherlockOSINT username search across 400+ social networks using the Sherlock Project.
| 1 | # Sherlock |
| 2 | |
| 3 | ## Purpose |
| 4 | |
| 5 | - Use this skill to search for username presence across many public social platforms and web services. |
| 6 | - Sherlock is useful for OSINT, account enumeration, alias correlation, and open-source reconnaissance. |
| 7 | - It is a reconnaissance utility, not a guarantee of identity resolution. |
| 8 | |
| 9 | ## Install |
| 10 | |
| 11 | ```bash |
| 12 | pip install sherlock-project |
| 13 | ``` |
| 14 | |
| 15 | Alternative source install: |
| 16 | |
| 17 | ```bash |
| 18 | git clone https://github.com/sherlock-project/sherlock |
| 19 | cd sherlock |
| 20 | python -m pip install -r requirements.txt |
| 21 | python sherlock.py username |
| 22 | ``` |
| 23 | |
| 24 | ## Basic Search |
| 25 | |
| 26 | ```bash |
| 27 | sherlock username |
| 28 | ``` |
| 29 | |
| 30 | - This searches a broad set of supported sites for a single username. |
| 31 | - Output normally shows which sites likely contain a matching profile. |
| 32 | - Results are only a starting point and should be verified manually. |
| 33 | |
| 34 | ## Multiple Usernames |
| 35 | |
| 36 | ```bash |
| 37 | sherlock user1 user2 user3 |
| 38 | ``` |
| 39 | |
| 40 | - Use this when comparing handles across several candidate aliases. |
| 41 | - Batch searching is useful when the target uses variations of the same naming pattern. |
| 42 | - Keep the candidate list short enough to review carefully. |
| 43 | |
| 44 | ## Output to a File |
| 45 | |
| 46 | ```bash |
| 47 | sherlock username --output results.txt |
| 48 | ``` |
| 49 | |
| 50 | - Save results when you need an audit trail or want to compare scans over time. |
| 51 | - Text output is convenient for quick archival, case notes, and manual review. |
| 52 | |
| 53 | ## CSV Output |
| 54 | |
| 55 | ```bash |
| 56 | sherlock username --csv |
| 57 | ``` |
| 58 | |
| 59 | - CSV output is useful for spreadsheet triage and bulk analysis. |
| 60 | - This is the better option when integrating results into reporting or other tooling. |
| 61 | |
| 62 | ## Restrict Search to Specific Sites |
| 63 | |
| 64 | ```bash |
| 65 | sherlock username --site twitter github |
| 66 | ``` |
| 67 | |
| 68 | - Site filtering is useful when you only care about a narrow platform set. |
| 69 | - Restricting sites speeds up focused investigations and reduces noise. |
| 70 | - Use it for targeted checks like developer handles, gaming handles, or creator profiles. |
| 71 | |
| 72 | ## Timeout Control |
| 73 | |
| 74 | ```bash |
| 75 | sherlock username --timeout 10 |
| 76 | ``` |
| 77 | |
| 78 | - Increase the timeout on slow or unstable networks. |
| 79 | - Decrease it when you want faster but less patient scans. |
| 80 | - Timeouts affect coverage and speed, so tune them to the environment. |
| 81 | |
| 82 | ## Tor Support |
| 83 | |
| 84 | ```bash |
| 85 | sherlock username --tor |
| 86 | ``` |
| 87 | |
| 88 | - This requires Tor to be installed and available. |
| 89 | - Use Tor only when your environment and policy allow it. |
| 90 | - Expect slower requests and occasional site behavior differences. |
| 91 | |
| 92 | ## Print All Results |
| 93 | |
| 94 | ```bash |
| 95 | sherlock username --print-all |
| 96 | ``` |
| 97 | |
| 98 | - This includes not-found results in addition to matches. |
| 99 | - It is useful when you want a full per-site record rather than only positive hits. |
| 100 | - Full output is better for documentation and reproducible analysis. |
| 101 | |
| 102 | ## Practical Workflow |
| 103 | |
| 104 | 1. Start with a single username search. |
| 105 | 2. Save results to a file or CSV. |
| 106 | 3. Filter to high-value platforms for deeper review. |
| 107 | 4. Manually verify candidate profiles. |
| 108 | 5. Correlate bios, avatars, links, timestamps, and naming patterns. |
| 109 | |
| 110 | ## Verification Guidance |
| 111 | |
| 112 | - A found username is not proof that the account belongs to the same person. |
| 113 | - Check profile metadata such as avatar reuse, linked websites, self-descriptions, and posting patterns. |
| 114 | - Compare account creation dates, geographic references, and cross-links. |
| 115 | - Treat weak matches as leads, not conclusions. |
| 116 | |
| 117 | ## Good Use Cases |
| 118 | |
| 119 | - Brand protection checks |
| 120 | - Public alias discovery |
| 121 | - Security research on exposed usernames |
| 122 | - Reconnaissance for incident response |
| 123 | - Confirming whether a handle is broadly reused |
| 124 | |
| 125 | ## Limitations |
| 126 | |
| 127 | - Site behavior changes can break detection. |
| 128 | - Some platforms throttle or block automated requests. |
| 129 | - False positives and false negatives both happen. |
| 130 | - Private or suspended accounts may not appear reliably. |
| 131 | |
| 132 | ## Output Handling |
| 133 | |
| 134 | - Keep raw outputs with timestamps when the result matters. |
| 135 | - Store CSV when the data will be joined with other OSINT sources. |
| 136 | - Re-run focused scans rather than assuming old results are still valid. |
| 137 | |
| 138 | ## Ethical Use |
| 139 | |
| 140 | - Use Sherlock only for authorized research, defensive security work, or lawful OSINT. |
| 141 | - Do not use it to harass, dox, stalk, or profile individuals without authorization. |
| 142 | - Respect the legal and policy boundaries of your organization and jurisdiction. |
| 143 | |
| 144 | ## Summary |
| 145 | |
| 146 | - Install with `pip install sherlock-project` or from the upstream GitHub repo. |
| 147 | - Search one handle with `sherlock username`. |
| 148 | - Search several with `sherlock user1 user2 user3`. |
| 149 | - Save results with `--output results.txt` or `--csv`. |
| 150 | - Restrict sites with `--site twitter github`. |
| 151 | - Tune network behavior with `--timeout 10` and optionally `--tor`. |
| 152 | - Use `--print-all` when a complete site-by-site record is needed. |