OSINT Methodology Framework

Problem

OSINT investigations often fail not because tools are missing, but because collection work lacks sequence: unclear target boundaries, inconsistent source prioritization, and unlinked evidence that only produces a report full of scattered links. osint-methodology turns open-source intelligence analysis into an operational checklist, helping engineers or analysts fix the question, evidence standard, and output structure before searching begins.

How It Works

The skill organizes OSINT into target definition, source selection, collection workflow, data correlation, timeline reconstruction, and reporting. When activated, it checks whether the task has a clear target, then evaluates whether available sources cover identity, behavior, relationships, and technical traces. For each step, it notes applicability, evidence gaps, and next actions, while tracking completed checklist items to reduce repeated searches and missed milestones.

It is useful for:
- Structured investigations: expanding initial clues into a verifiable timeline
- Evidence organization: grouping screenshots, posts, and domain records into linked context
- Methodology teaching: explaining how OSINT moves from hypothesis to conclusion

Note: this is a methodology framework, not a live intelligence feed; users must still assess legal authorization, platform ToS, privacy boundaries, and target legitimacy.