跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
法律与合规

investigate-anything

Start-here router and tradecraft baseline for any investigation into a person, company, domain, image or selector. Sets authorised scope, turns a vague request into an answerable intelligence question, writes a collection plan, picks the right workflow for the starting selector, and applies source grading and competing-hypothesis discipline. Use for "investigate this person or company", "do OSINT on X", "where do I start", or any open-source intelligence, due diligence, background or attribution task. Applies across due diligence, fraud, threat intelligence, journalism and compliance. Reference at useosint.com/skills/investigate-anything.

UseOSINT · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add UseOSINT/Skills --skill investigate-anything

技能说明


name: investigate-anything description: >- Start-here router and tradecraft baseline for any investigation into a person, company, domain, image or selector. Sets authorised scope, turns a vague request into an answerable intelligence question, writes a collection plan, picks the right workflow for the starting selector, and applies source grading and competing-hypothesis discipline. Use for "investigate this person or company", "do OSINT on X", "where do I start", or any open-source intelligence, due diligence, background or attribution task. Applies across due diligence, fraud, threat intelligence, journalism and compliance. Reference at useosint.com/skills/investigate-anything. disable-model-invocation: true

Investigate anything

The front door. Everything downstream is faster than the thinking that should precede it, which is why most bad investigations are not collection failures — they are framing failures. You can run forty tools against a name and produce a confident dossier on the wrong person. The work here is deciding what question you are answering, what would count as an answer, and what would prove you wrong.

Core vocabulary

Used across every skill in this repo, defined only here.

  • Selector — one identifiable data point: name, handle, email, phone, domain, IP, wallet, hash, plate, IMO, company number.
  • Pivot — turning one selector into new selectors (email → breach record → reused handle → forum profile → real name). An investigation is a chain of pivots. Every pivot is also a chance to jump onto a different person.

Step 1 — Authorized scope

Read ../../ETHICS.md, then write down five things:

  1. Subject — the specific entity, distinguished from anyone with a similar name. Write the discriminators you will use ("the J. Okonkwo who is a director of company 09xxxxxx", not "J. Okonkwo").
  2. Objective — see Step 2.
  3. In bounds — selector types, sources, and whether interaction is allowed.
  4. Out of bounds — the named things you will not do: logging into anything belonging to the subject, contacting them, family members, medical or religious data, and any selector unrelated to the objective.
  5. Jurisdiction — whose law governs you, the subject, and the data. In the EU/UK, aggregating scattered public facts about a living person is processing personal data and needs a lawful basis and minimisation.

If you cannot state who authorized this and on what basis, stop. Not "proceed carefully" — stop. An unauthorized investigation cannot be fixed later by a good report.

Done when all five are written down and you can name the specific action that would put you out of bounds.

Step 2 — Frame an answerable question

"Find out about X" is not an objective; it has no stopping condition, so it terminates when you get bored or when you find something that feels like a result. Rewrite the request until it has a subject, a decision it feeds, and a condition that would settle it.

VagueAnswerable
Investigate this companyDoes this supplier have an undisclosed owner subject to sanctions, and does it operate from the address on the invoice?
Who is this accountIs the operator of @handle the same person as the named ex-employee, or someone else?
Look into this domainIs example.com operated by the same party as the phishing domain, on shared infrastructure?

Then write the negative: what finding would mean no. If nothing could, the question is unfalsifiable and you will confirm it whatever you see.

Done when the objective is one sentence, and you have written what a "no" answer would look like.

Step 3 — Write the collection plan before collecting

Aimless pivoting feels productive because every pivot yields something. A collection plan is the list of questions, each mapped to the source most likely to settle it, ranked by cost and intrusiveness — so you notice when you're three hours into an interesting branch that answers nothing.

For each question: the indicator that would answer it, the source or skill that produces it, whether it is passive, and what you do if it comes back empty. Passive-first, always: exhaust archives, registries, and logs before anything that touches the subject. Plans are revised as you learn — the point is that deviations become visible.

Done when each objective question has a named source or skill and a first/fallback order.

Step 4 — Route by starting selector

Type the workflow skill's name.

You haveRun
A person's name or real identityfind-anyone
A company, brand, or invoice entityx-ray-a-company
A domain, website, or IPrecon-a-domain-passively
A username or handlehunt-a-handle
An email addresswhat-an-email-reveals
A phone numberwhose-number-is-this
A photo or video to locate or verifywhere-was-this-taken
A social profile you already attributepattern-of-life-from-socials

No clear starting point? Start with the selector that is both unique and indexed — email and domain beat name and handle, because names collide and handles are claimed by strangers.

Technique skills load themselves when you describe what you are doing. Before touching anything the subject controls, run investigate-without-getting-made. Keep the case in a graph from the first pivot: graph-the-network.

Done when the routed workflow has been run and its findings are recorded with sources.

Step 5 — Grade sources as you collect, not afterwards

Use the Admiralty (NATO-style) scheme: a letter for the source and a number for the information, graded independently, on every item.

  • Letter A–F: the source's track record and access. A = reliable history, no doubt of authenticity; F = cannot be judged.
  • Number 1–6: whether the content is confirmed by other independent sources, and whether it is logical in itself. 1
阅读完整来源 ↗