knowledge-graph-management

Monitors knowledge graph health and answers codebase queries via PowerShell graph scripts.

2|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/jay-steenbergen/MSSAMentorAgent --skill knowledge-graph-management-jay-steenbergen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: knowledge-graph-management
Source: https://github.com/jay-steenbergen/MSSAMentorAgent/tree/main/.github/skills/knowledge-graph-management
Command: npx skills add https://github.com/jay-steenbergen/MSSAMentorAgent --skill knowledge-graph-management-jay-steenbergen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintaining a repository knowledge graph manually is error-prone: dangling edges, orphan nodes, and unclustered nodes accumulate silently, and answering questions like "what uses this module" requires tedious manual searching. This Skill automates health checks, gap analysis, and natural-language graph queries. ## Core Features & Use Cases - Health Monitoring: Runs health checks and gap analysis on the merged graph layer, reporting dangling edges, duplicate node IDs, stub nodes, orphan nodes, and unclustered nodes in a formatted summary. - Interactive Repair Workflow: Presents actionable options (auto-fix dangling edges, discover orphan connections, assign clusters, full rebuild) and loops until issues are resolved or skipped. - Natural Language Graph Queries: Answers questions like "show me the call flow for X", "what depends on X", or "what skills load for this intent" by routing to the appropriate query script. - Use Case: After refactoring skills or agents in a repository, ask to "check the graph" to detect broken edges, then auto-fix them and verify the graph returns to a healthy state. ## Quick Start Ask the agent to check the knowledge graph health and show any dangling edges or orphan nodes that need attention.

Frequently Asked Questions about knowledge-graph-management

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

FAQPage Schema
How do I check knowledge graph health in a repository?▼

Ask to "check the graph" and the skill runs health.ps1 and gap-analysis.ps1 against the merged layer. It reports node, edge, and cluster counts plus dangling edges, duplicate IDs, and stub nodes in a formatted summary.

How to find what depends on a module in a codebase?▼

Ask "what uses X" or "what depends on X" and the skill calls Get-Dependents.ps1 with the node name. For reverse lookups, "what does X use" routes to Get-Dependencies.ps1, and call flows use Get-CallFlow.ps1.

Can dangling edges in a knowledge graph be fixed automatically?▼

Yes. When dangling edges are detected, the skill offers an Auto-fix option that runs fix-dangling-edges.ps1, then re-runs the health checks to verify the repair. Fixes only execute after explicit user selection.

Does this skill modify graph files directly?▼

No. The skill delegates all modifications to existing build pipeline scripts such as rebuild-if-stale.ps1 and fix-dangling-edges.ps1. Health checks are read-only, and write operations occur only on explicit user action.

What are the limitations of knowledge graph health checks?▼

Checks depend on the existing build pipeline scripts and the merged graph layer being present. Orphan node connection discovery requires a full rebuild, and cluster assignment for unclustered nodes is guided manually rather than fully automated.