graphify-status

Report knowledge-graph community label coverage across all graphify-enabled projects on a machine.

3|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/bravros/bravros --skill graphify-status-bravros
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: graphify-status
Source: https://github.com/bravros/bravros/tree/main/plugins/tools/skills/graphify-status
Command: npx skills add https://github.com/bravros/bravros --skill graphify-status-bravros

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Knowledge-graph community labels silently decay as re-clustering renumbers community ids, leaving queries returning placeholders like "Community 417" instead of real names. This Skill scans every graphify-enabled project on the machine and reports exactly which graphs are stale, unlabelled, or degraded. ## Core Features & Use Cases - Coverage Table: Scans project roots for graphify-out/graph.json and prints a per-project table of communities, labels, and the percentage of nodes still rendering as "Community NN". - Automatic Fix Prompts: For each degraded project, generates a self-contained, paste-ready relabelling prompt in /tmp/graphify-label/ with sample node labels inlined, plus a MODE verdict (inline vs. external handoff). - Additive Merge: Merges externally produced label JSON back into community-labels.json and graph.json without ever overwriting existing names, with --dry-run and --force options. - Use Case: After a large refactor, run the scanner to discover that one project's graph is 53% uncovered, then follow the generated prompt to relabel only the missing communities and merge the results safely. ## Quick Start Ask the agent to run /graphify-status to show label coverage for every graphify project on this machine.

Frequently Asked Questions about graphify-status

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

FAQPage Schema
How do I check which graphify knowledge graphs have missing community labels?▼

Run the graphify-status.py scanner with uv, which walks your project roots (default ~/Code and ~/Sites) and prints a table of communities, labels, and the percentage of nodes still showing the Community NN placeholder for each project.

How do I fix a degraded graphify graph with unnamed communities?▼

The scan auto-generates a paste-ready labelling prompt in /tmp/graphify-label/ per degraded project. Name the communities yourself for small gaps (25 or fewer), or paste the prompt into an external agent, then merge the returned JSON with merge-missing-labels.py.

Why does my graph show 100% uncovered even though labels equal communities?▼

graphify renamed the node field from community_label to community_name, and a graph carries whichever key was current when built. A reader checking only one key misreports a healthy graph; confirm which key your graph.json uses before relabelling anything.

Can I use collate-labels.py to fill in missing community labels?▼

No. collate-labels.py rebuilds the labels file from only the current run's results and stamps Community NN over everything else, destroying existing labels during a partial relabel. Use merge-missing-labels.py, which is additive and never overwrites without --force.

Does label coverage guarantee the community names are correct?▼

No. Coverage is not correctness: a community can be fully labelled but wrong after the underlying code is refactored, and parallel labelling agents can produce duplicate names. Only a fresh full relabel fixes drifted labels, since gap-fill passes never revisit existing names.