Social Media Profile Finder
Overview
Identify the most likely public Facebook and Instagram profiles that belong to a person when the user supplies (1) a photo from social media, (2) a name, and (3) a location. Combines reverse-image search, face search, and name-location Google dorks. Public data only.
Inputs
- Photo or photo URL / description of a face-forward image
- Full name or closest known name
- City, region, or country
If any of the three is missing, ask for it before running the full workflow. A name-only or photo-only search is allowed but must be labeled lower confidence.
Workflow
Run these steps in order. Do not skip the photo step when a photo exists.
Prepare the image
- Prefer the original file over a screenshot.
- If multiple faces, crop mentally or describe the target face.
- Note lighting, angle, distinctive features, clothing, background landmarks.
Reverse image and face search
- Exact-file engines first — Google Lens / Google Images, Yandex Images, TinEye.
- Face engines second — FaceCheck.ID, PimEyes, similar public face indexes.
- Record every URL where the same face or same file appears (profile pics, tagged photos, news, forums).
- Pixel match finds copies of a file. Face match finds the same person in different photos. You usually need both.
Name + location search
Use web_search and open_page with queries such as
"Full Name" "City" site:facebook.com"Full Name" "City" site:instagram.com"Full Name" instagram City"Full Name" facebook City- common username stems of the name plus city
Also search the name without quotes and with middle initial / nickname variants.
Cross-check
A candidate only counts if at least two of these align
- Face match (same person, not a lookalike)
- Name or close alias
- Location consistency (current city, hometown, check-ins, language, friends from that area)
- Photo reuse across platforms
Rank High / Medium / Low. Common names without a face match stay Low.
Output (strict)
- Highest-confidence Facebook URL + evidence
- Highest-confidence Instagram URL + evidence
- Other candidates ranked
- Confidence per result
- What could not be confirmed (private account, common name, no indexed photos)
- Exact searches that were run
Do not invent profiles. If nothing solid appears, say so and list the searches.
Tool use
- web_search and open_page for dorks and result pages
- search_images only when you need additional public photos of a candidate
- x_keyword_search / x_user_search if an X handle surfaces as a pivot
- Do not claim access behind logins. Do not scrape private accounts.
Limits
- Private Instagram and locked Facebook profiles will not resolve.
- Face tools have false positives. Require a second signal.
- Paid face engines (PimEyes, FaceCheck.ID) may only be describable, not callable from this sandbox. Tell the user to run those themselves if needed and then feed results back.
- This skill is for public OSINT, catfish checks, and self-audit. It is not a stalking kit.
Version
1.0 — 2026-09-05. Initial skill from user prompt (photo + name + location → Facebook / Instagram).
1---2name: social-media-profile-finder3description: Find public Facebook and Instagram profiles from a photo plus a name and location using reverse image search, face search, and name-location dorks. Triggered by find Facebook Instagram from photo, OSINT social profiles, identify account from picture name city, reverse face search socials, or when the user supplies a social photo plus name plus location.4---56# Social Media Profile Finder78## Overview910Identify the most likely public Facebook and Instagram profiles that belong to a person when the user supplies (1) a photo from social media, (2) a name, and (3) a location. Combines reverse-image search, face search, and name-location Google dorks. Public data only.1112## Inputs1314- Photo or photo URL / description of a face-forward image15- Full name or closest known name16- City, region, or country1718If any of the three is missing, ask for it before running the full workflow. A name-only or photo-only search is allowed but must be labeled lower confidence.1920## Workflow2122Run these steps in order. Do not skip the photo step when a photo exists.23241. Prepare the image25 - Prefer the original file over a screenshot.26 - If multiple faces, crop mentally or describe the target face.27 - Note lighting, angle, distinctive features, clothing, background landmarks.28292. Reverse image and face search30 - Exact-file engines first — Google Lens / Google Images, Yandex Images, TinEye.31 - Face engines second — FaceCheck.ID, PimEyes, similar public face indexes.32 - Record every URL where the same face or same file appears (profile pics, tagged photos, news, forums).33 - Pixel match finds copies of a file. Face match finds the same person in different photos. You usually need both.34353. Name + location search36 Use web_search and open_page with queries such as37 - `"Full Name" "City"` site:facebook.com38 - `"Full Name" "City"` site:instagram.com39 - `"Full Name" instagram` City40 - `"Full Name" facebook` City41 - common username stems of the name plus city42 Also search the name without quotes and with middle initial / nickname variants.43444. Cross-check45 A candidate only counts if at least two of these align46 - Face match (same person, not a lookalike)47 - Name or close alias48 - Location consistency (current city, hometown, check-ins, language, friends from that area)49 - Photo reuse across platforms50 Rank High / Medium / Low. Common names without a face match stay Low.51525. Output (strict)53 - Highest-confidence Facebook URL + evidence54 - Highest-confidence Instagram URL + evidence55 - Other candidates ranked56 - Confidence per result57 - What could not be confirmed (private account, common name, no indexed photos)58 - Exact searches that were run5960Do not invent profiles. If nothing solid appears, say so and list the searches.6162## Tool use6364- web_search and open_page for dorks and result pages65- search_images only when you need additional public photos of a candidate66- x_keyword_search / x_user_search if an X handle surfaces as a pivot67- Do not claim access behind logins. Do not scrape private accounts.6869## Limits7071- Private Instagram and locked Facebook profiles will not resolve.72- Face tools have false positives. Require a second signal.73- Paid face engines (PimEyes, FaceCheck.ID) may only be describable, not callable from this sandbox. Tell the user to run those themselves if needed and then feed results back.74- This skill is for public OSINT, catfish checks, and self-audit. It is not a stalking kit.7576## Version77781.0 — 2026-09-05. Initial skill from user prompt (photo + name + location → Facebook / Instagram).
Stijnman