osint-investigation

Cross-reference public records to resolve entity identities and uncover hidden relationships.

1|Updated Jun 25, 2026
One-click install
npx skills add https://github.com/Signmanal/VIGIL --skill osint-investigation-signmanal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: osint-investigation
Source: https://github.com/Signmanal/VIGIL/tree/main/optional-skills/research/osint-investigation
Command: npx skills add https://github.com/Signmanal/VIGIL --skill osint-investigation-signmanal

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill solves the problem of manually cross-referencing fragmented public records to uncover hidden relationships between entities, which is extremely time-consuming and error-prone when done by hand across SEC filings, federal contracts, sanctions lists, property records, court documents, and global news archives.

Core Features & Use Cases

  • Multi-Source Entity Resolution: Normalize and match entity names across SEC EDGAR, USAspending, OFAC SDN, ICIJ Offshore Leaks, NYC ACRIS property records, OpenCorporates, CourtListener, Wikipedia/Wikidata, and GDELT news using exact, fuzzy, and token-overlap matching with explicit confidence tiers.
  • Statistical Timing Correlation: Run permutation tests to determine if event timing clusters suspiciously close together, such as lobbying filings near contract awards, producing p-values and effect sizes to distinguish signal from noise.
  • Auditable Evidence Chains: Automatically generate structured findings JSON where every claim traces back to specific source rows with confidence levels, ensuring full auditability and preventing unsupported assertions.
  • Use Case: An investigator can trace whether a federal contractor appearing in USAspending also lobbies through Senate LD disclosures, holds NYC property via ACRIS, or appears in OFAC sanctions lists, with all cross-links and timing anomalies documented in a single evidence chain.

Quick Start

Use the osint-investigation skill to investigate "Example Corp" by fetching its SEC EDGAR filings, USAspending contracts, and Senate lobbying records, resolving entities across these sources, and generating a structured findings report with evidence chains.

Frequently Asked Questions about osint-investigation

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

FAQPage Schema
How do I cross-reference public records to resolve entity identities and uncover hidden corporate relationships?

Cross-referencing public records to resolve entity identities is automated by normalizing names across SEC filings, sanctions lists, and property records using exact, fuzzy, and token-overlap matching with explicit confidence tiers.

What is the best way to detect suspicious timing between lobbying activity and federal contract awards?

Detecting suspicious timing between lobbying activity and contract awards is achieved by running permutation tests that determine if event clusters are statistically significant.

How do I build auditable evidence chains from fragmented OSINT data without external dependencies?

Building auditable evidence chains from fragmented OSINT data without external dependencies is handled by deterministic, stdlib-only Python scripts that normalize records and output structured JSON findings.

Can I use stdlib-only Python scripts to perform three-tier entity matching across SEC EDGAR and OFAC sanctions lists?

Yes, you can use stdlib-only Python scripts to perform three-tier entity matching across SEC EDGAR and OFAC sanctions lists.

What sources are supported for multi-source due diligence investigations involving offshore leaks and property records?

Multi-source due diligence investigations involving offshore leaks and property records are supported across ICIJ Offshore Leaks, NYC ACRIS, OpenCorporates, CourtListener, USAspending, and GDELT news archives.

Why does manual cross-referencing of government contracts and corporate filings fail to find hidden entity relationships?

Manual cross-referencing of government contracts and corporate filings fails to find hidden entity relationships because fragmented public records are extremely time-consuming and error-prone to process by hand.