discovery-graph

Captures raw host, network, service, storage, runtime, journal and repository discovery data into a SQLite-backed graph with entities, relations and evidence for reproducible audits.

2|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/metric-space-ai/ctox --skill discovery-graph
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: discovery-graph
Source: https://github.com/metric-space-ai/ctox/tree/main/skills/system/knowledge_bootstrap/discovery-graph
Command: npx skills add https://github.com/metric-space-ai/ctox --skill discovery-graph

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Build or refresh a concrete infrastructure inventory from real host, network, service, storage, runtime, journal, and repo discovery commands. Use when CTOX needs to inspect a machine or repo, gather raw discovery evidence, translate it into the shared SQLite discovery model, and leave behind explicit entities, relations, evidence, and rerunnable discovery runs instead of ad hoc shell output.

Core Features & Use Cases

  • Inspect a host or repo, gather raw discovery evidence, and persist a normalized graph in SQLite.
  • Reuse and patch local helper resources to capture, persist, and query discoveries with a durable run_id.
  • Enable full-sweep discovery with inactive-removal semantics and evidence-backed relations for reproducible audits.

Quick Start

Run a full discovery sweep using the included linux_collect and capture_run helpers to generate and persist a replayable normalized discovery graph.

Frequently Asked Questions about discovery-graph

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

FAQPage Schema
How do I build an infrastructure inventory from raw host and network discovery data?▼

Build an infrastructure inventory by capturing raw host, network, service, storage, and repository discovery data, then translating the evidence into a durable SQLite graph with explicit entities, relations, and rerunnable discovery runs.

What is the best way to store discovery evidence in SQLite for reproducible audits?▼

Store discovery evidence in SQLite by running a full discovery sweep that captures raw host and service data, normalizes it into a shared discovery model, and persists a replayable graph with a durable run_id for inactive-removal and evidence-backed audits.

Do I need Python scripts to automate infrastructure discovery and graph building?▼

Automating infrastructure discovery requires raw-capture and persistence helpers like linux_collect.py, capture_run.py, discovery_store.py, and normalize_minimum.py to gather evidence, normalize it, and persist a concrete graph in SQLite.

Can I inspect machines and repos to generate a normalized infrastructure graph?▼

Inspect machines and repos by executing discovery commands that gather raw evidence, then apply bootstrap normalization tooling to translate the captured data into a shared SQLite discovery model with entities and relations.

Why use a SQLite discovery model instead of ad hoc shell output for infrastructure mapping?▼

A SQLite discovery model replaces ad hoc shell output by translating raw discovery evidence into durable entities, relations, and rerunnable discovery runs, leaving behind explicit evidence-backed graph data for reproducible audits.

Does a full discovery sweep support inactive-removal semantics for infrastructure tracking?▼

A full discovery sweep supports inactive-removal semantics by capturing fresh evidence, normalizing it into the SQLite discovery model, and updating the graph to reflect active and inactive infrastructure relations accurately.