osint-investigation

Assemble public-record evidence chains from multiple sources into normalized CSVs and findings.json.

Updated Jun 17, 2026
One-click install
npx skills add https://github.com/anilcan-kara/nozich-agent --skill osint-investigation-anilcan-kara
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: osint-investigation
Source: https://github.com/anilcan-kara/nozich-agent/tree/main/optional-skills/research/osint-investigation
Command: npx skills add https://github.com/anilcan-kara/nozich-agent --skill osint-investigation-anilcan-kara

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This framework enables investigators to collect, normalize, and correlate public-record data from diverse sources to produce traceable evidence chains.

Core Features & Use Cases

  • Workflow-driven data acquisition from SEC EDGAR, USAspending, Senate LD, OFAC SDN, ICIJ Offshore Leaks, NYC ACRIS, OpenCorporates, CourtListener, Wayback, Wikipedia/Wikidata, and GDELT.
  • Entity resolution across sources to link entities with confidence scores.
  • Output of structured findings JSON and traceable cross-links for audits or journalism.

Quick Start

Run the provided fetch and resolution scripts to begin gathering public records for a target.

Frequently Asked Questions about osint-investigation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build cross-source evidence chains from public records?

Cross-source evidence chains are built by running this framework's Python stdlib scripts to fetch public records from government filings, corporate registries, and news, then resolving entities across sources with confidence scores and outputting normalized CSVs and a findings JSON payload.

What is entity resolution in open-source intelligence investigations?

Entity resolution in open-source intelligence is the process of linking entities across diverse public-record sources like sanctions lists and corporate registries. This framework applies confidence scores to correlate and resolve these entities for traceable reporting.

Can I investigate corporate registries and sanctions lists using only Python stdlib?

Yes, you can investigate corporate registries and sanctions lists using only Python stdlib. The framework relies entirely on standard library scripts for data ingestion and resolution, requiring no external dependencies.

How do I collect public-record data from sources like SEC EDGAR and OFAC SDN?

To collect public-record data from sources like SEC EDGAR and OFAC SDN, run the provided fetch scripts. The workflow-driven acquisition gathers filings, sanctions, and lobbying data, outputting normalized CSVs for audit and journalism.

What is the best way to normalize OSINT data for audit reporting?

The best way to normalize OSINT data for audit reporting is using a framework that outputs structured findings JSON and traceable cross-links. This framework generates normalized CSVs and a findings.json payload from diverse public records.

What are the limitations of using a stdlib-only framework for public-record investigation?

A limitation of a stdlib-only framework for public-record investigation is the lack of built-in asynchronous HTTP libraries or advanced parsing modules, meaning ingestion and resolution scripts rely solely on Python's standard library components.