void-graph

Analyzes the installed harness graph to report dead, underused, or token-expensive components.

Updated May 29, 2026
One-click install
npx skills add https://github.com/voidcorp-core/void-harness --skill void-graph-voidcorp-core
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: void-graph
Source: https://github.com/voidcorp-core/void-harness/tree/main/packages/core/skills/void-graph
Command: npx skills add https://github.com/voidcorp-core/void-harness --skill void-graph-voidcorp-core

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Installed skills, agents, and hooks accumulate over time, and nobody knows which ones actually fire, which sit dead, or which consume tokens out of proportion to their value. This Skill reads the harness as a graph and correlates it with real usage events to answer those questions with evidence. ## Core Features & Use Cases - Audit reports: Runs void-harness graph audit to flag dead, dead-hook, underused, and low-yield components against observed session events. - Cost analysis: Runs void-harness graph cost to show token weight per component, and graph behavior to compare what fired against what was declared. - Live studio: Serves a local, offline graph studio on localhost via void-harness graph live for interactive exploration. - Use Case: After months of running void-harness, you suspect half your skills never trigger. Run the audit to see which components were never observed in the current window, then decide with a human what to trim. ## Quick Start Ask the assistant to run a void-harness graph audit and summarize which installed components are dead, underused, or expensive.

Frequently Asked Questions about void-graph

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

FAQPage Schema
How do I audit which installed skills and hooks are actually being used?

Run `void-harness graph audit` through the CLI, or `npx voidharness graph audit` when the binary is not on PATH. It correlates the installed components with this project's events under .void/machine/runs and reports dead, dead-hook, underused, and low-yield entries.

How do I measure token cost per skill or agent in void-harness?

Run `void-harness graph cost` to print token weight per component in a terminal report. Combine it with `graph behavior` to compare what actually fired against what was declared.

Does the graph audit require network access or an account?

No. Everything is local: no npm fetch, no network, no account. The analyzer reads the installed model and correlates it with the project's own event logs.

Why does the graph report say insufficient data?

The activation meter needs enough sessions before absence of a component means anything. You can preview with `--min-sessions 1 --min-events 1` on a single session, but label it as a preview since the evidence base is thin.

Should I remove components the audit flags as dead?

Not automatically. Dead means not observed within the current window, which is a statement about the observation period, not the component's worth. Every finding is advisory; removal is a human decision made with the reason the component exists.