Back to Skills

graph-the-network

Build an entity-relationship link-analysis graph of an investigation — nodes, typed edges carrying source and confidence, aliases, and temporal validity — to expose shared infrastructure, bridging nodes and the real principal behind a frontman. Covers Maltego, Neo4j and Cypher, Gephi, centrality and community detection, and entity resolution. Use when an investigation has outgrown a list and needs a graph, or when asked how a set of people, companies and domains connect. Applies to fraud-ring an

13stars1forksUpdated 8/13/2026

Security Assessment

Low Risk(85/100)

Detected risks:

Dual-Use Investigative Reconnaissance(The skill is analytical link-analysis methodology for OSINT investigations and contains no exploit code or attack automation, but its stated goal of exposing shared infrastructure and identifying the real principal behind a frontman is dual-use reconnaissance that could support surveillance or deanonymization of individuals., It references and chains into other reconnaissance skills such as domain ownership lookup, subdomain enumeration, and exposed-server discovery to populate the graph, which are infrastructure-mapping activities.)
Security Score85/100

About graph-the-network

This skill is a methodology guide for building entity-relationship link-analysis graphs during an OSINT investigation. It solves the problem that a flat list of selectors hides shared connections a human can see instantly in a graph layout, and it teaches how to model an investigation as nodes and typed edges that carry source, confidence, aliases, and temporal validity, so the graph becomes the case's working memory rather than a final picture.

It sets out concrete practices: one node per real-world thing (treating aliases as attributes and recording evidence-based merges) with a closed, direction-consistent vocabulary of edge types; putting source, retrieval timestamp, source grade, and confidence on every edge and rendering confidence visually (solid/dashed/dotted) with a confirmed-only view; and adding valid_from/valid_to so an untimed graph does not falsely assert that everything coexisted. It explains what the graph reveals, shared infrastructure, bridging nodes, the difference between degree and betweenness centrality, community detection, and collection gaps, while warning that centrality measures your collection as much as reality. A tool comparison covers plain node/edge CSVs with Graphviz or Gephi, Neo4j with Cypher for path queries, Gephi for layout and metrics, and Maltego for automated transform-based pivoting.

It targets OSINT analysts, investigative journalists, and fraud, AML, and sanctions-evasion practitioners doing shell-network and corporate-structure work. It is analytical and read-only guidance rather than an exploit tool, but it is dual-use reconnaissance methodology aimed at deanonymizing the real principal behind a frontman, so it warrants a light security note.

FAQ

When should I reach for a graph instead of a list?

When an investigation has outgrown a list, or when the question is how a set of people, companies, and domains connect. The skill argues the graph should be built from the first pivot as the case's working memory, not drawn at the end for a report.

What are the core modeling rules?

One node per real-world thing with aliases as attributes and recorded evidence-based merges, and a small closed set of direction-consistent edge types defined at the top of the case file. It also models a person and their account as separate nodes.

Why put source and confidence on edges?

Because the claim lives in the relationship, not the node. Each edge should carry source, retrieval timestamp, source grade, and confidence, rendered visually, so a weak inferred link is not mistaken for a confirmed one.

What tools does it recommend?

For most work, two CSVs (nodes and edges) plus a renderer like Graphviz or Gephi. Neo4j with Cypher for path queries, Gephi for layout and metrics, and Maltego for automated transform-based pivoting when licensing and scale justify it.

How should centrality metrics be interpreted?

As pointers to where to look, never as conclusions. Betweenness often surfaces the controlling party better than degree, but centrality reflects how thoroughly you collected data as much as reality.

All Files

3 files
SKILL.md12.6 KB
View
reference/tool-comparison.md6.9 KB
View
reference/schema-starter.md5.7 KB
View

Install graph-the-network

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill