pattern-of-life-from-socials
Deep-dive a subject's social media presence — profile metadata, follower and mutual network, content analysis, and posting-time pattern of life across Instagram, Facebook, X/Twitter, TikTok, LinkedIn, Reddit, Telegram and Discord. Use when profiling a social account, mapping someone's associates, inferring a subject's timezone or routine from their posts, or archiving a profile before it is deleted. Applies to threat assessment and executive protection, insider-threat investigation, pre-litigation research, and personal exposure audits — with explicit limits on profiling uninvolved third parties. Reference at useosint.com/skills/pattern-of-life-from-socials.
UseOSINT · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add UseOSINT/Skills --skill pattern-of-life-from-socials技能说明
name: pattern-of-life-from-socials description: >- Deep-dive a subject's social media presence — profile metadata, follower and mutual network, content analysis, and posting-time pattern of life across Instagram, Facebook, X/Twitter, TikTok, LinkedIn, Reddit, Telegram and Discord. Use when profiling a social account, mapping someone's associates, inferring a subject's timezone or routine from their posts, or archiving a profile before it is deleted. Applies to threat assessment and executive protection, insider-threat investigation, pre-litigation research, and personal exposure audits — with explicit limits on profiling uninvolved third parties. Reference at useosint.com/skills/pattern-of-life-from-socials. disable-model-invocation: true
Pattern of Life from Socials
Pattern-of-life analysis turns scattered public posts into a model of where someone is, when, and with whom. It is the most abusable technique in this repo: the same method produces a due-diligence report and a stalking dossier. The difference is authorization and scope, not tradecraft. The beginner error is collecting posts instead of analysing them — screenshots of a feed are not intelligence. Work four layers: account metadata, network, content, temporal behaviour. The first and last are the two everyone skips, and the two the subject can't curate.
Step 1 — Authorized scope
Read ../../ETHICS.md, then write down before opening a single profile:
- Subject — the account(s) and the real-world entity you believe is behind them.
- Objective — the question that ends the investigation. "Pattern of life" is not one. "Does this vendor's EU lead actually live in the EU" is.
- In / out of bounds — explicitly. Minors, uninvolved family, home address, health, religion, sexuality and immigration status are out unless the objective requires them and you can defend that.
- Posture — observation only, or authorized interaction. Following, liking, messaging and viewing stories are all interaction.
- Jurisdiction — yours, the subject's, the platform's.
- Stop condition — you stop when the objective is answered, when the trail lands on an uninvolved third party, or when the only question left is "where do they sleep."
Done when all six are recorded in the case file.
Step 2 — Choose a viewing identity, then preserve
Logged-out leaks less and sees less; logged-in sees more and leaks more.
Platforms variously report story views and profile visits to the subject, and
recommendation systems surface accounts that look at each other — so merely
viewing can put your research account in the subject's suggestions. Decide the
tradeoff using investigate-without-getting-made; never browse a subject from
a personal or employer account.
Then capture before you analyse. Accounts get locked or scrubbed
mid-investigation, often because someone noticed. Archive the profile and every
post you may cite via read-deleted-pages, and pull older snapshots — they
routinely show a previous bio, link, or handle. Save media locally.
Done when the viewing identity is recorded and everything you intend to cite exists as an archive URL or a local file with a capture timestamp.
Step 3 — Layer one: account metadata
Go after what the subject never chose. Full per-platform behaviour is in the platform disclosure matrix.
- Creation date. Shown outright on some platforms, derivable on others. Snowflake-style 64-bit IDs encode a millisecond timestamp in their high bits, offset from a platform-specific epoch — the ID is the signup time. Plain sequential IDs give registration order, so you can bracket a date against accounts of known age.
- The numeric ID. It survives handle changes, so it — not the handle — is the durable selector. Record it.
- Handle history. Seldom a feature, usually recoverable from old mentions, inbound links, archived snapshots and abandoned cross-posts. A freed handle can be reclaimed by a stranger, so an old link proves nothing about current control.
- Verification and linked accounts. Whether a badge is paid or identity-checked changes what it's worth. Linked sites and business-account contact fields expose emails and phone numbers the personal profile wouldn't.
Done when ID, creation date, handle history and every linked selector are recorded with sources.
Step 4 — Layer two: network
A subject's OPSEC is nearly irrelevant if their relatives tag them.
- Early followers. The first accounts to follow a personal account are overwhelmingly family, school friends and coworkers — it spread by word of mouth before it had reach. Where follower ordering is observable, the oldest tail is the highest-value segment on the page.
- Mutual-follow clusters. Reciprocal edges map real-world communities: employer, school cohort, hometown, club. The cluster is the finding; a single edge isn't.
- Tag direction. Who the subject tags is curated. Who tags the subject is not. Inbound tags from an open-book cousin routinely deliver the birthday, the house, the car and the workplace the locked-down subject withheld.
- Reply latency. Accounts that reliably comment within minutes are the inner circle, regardless of follower counts.
Build this in graph-the-network, not as a list.
Done when the inner circle, one real-world cluster, and the third parties who leak about the subject are identified and graded.
Step 5 — Layer three: content
Read past the subject of each photo to the accidental content: reflections in windows, mirrors, glasses and dark screens; laptop and phone displays in frame; paperwork such as boarding passes, parcel labels and event badges; vehicles, plates, dealer frames and parking permits. Repeated backgrounds are what upgrade a room from "somewhere" to "home" or "workplace" — count occurrences and note the date span.
Run `sec
阅读完整来源 ↗