context-graph

Design and audit multi-graph context architectures for AI-coding workspaces.

1|Updated May 6, 2026
One-click install
npx skills add https://github.com/jacob-balslev/skill-graph --skill context-graph-jacob-balslev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-graph
Source: https://github.com/jacob-balslev/skill-graph/tree/main/marketplace/skills/context-graph
Command: npx skills add https://github.com/jacob-balslev/skill-graph --skill context-graph-jacob-balslev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents large AI-coding workspaces from becoming disconnected piles of skills and docs where agents cannot reliably discover, load, or trust the right context.

Core Features & Use Cases

  • Defines a four-graph context architecture: skill knowledge graph, document routing graph, memory index, and script/command registry, including the cross-graph edges that enable end-to-end propagation.
  • Enforces edge-type discipline with health metrics: models and caps adjacent, boundary, and verify_with relations to avoid hub-and-spoke degeneration and reduce orphaned/unreachable skills.
  • Provides deterministic graph-synthesis signals and propagation discipline: specifies reproducible inputs (frontmatter relations, routing bundle co-membership, explicit labels/keywords) and a checklist to trace a single change across docs, skills, memory, and scripts.
  • Covers anti-patterns and remediation prioritization: flags edge inflation, one-way edges, AI-inferred rebuild drift, and ignored cross-graph edges, then remediates orphans in blast-radius order.

Quick Start

Use context-graph when auditing your workspace’s multi-graph context topology to diagnose orphan risk, connectivity failures, and change-propagation gaps.

Frequently Asked Questions about context-graph

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

FAQPage Schema
How do I detect orphaned skills and unreachable context in an AI coding workspace?

To detect orphaned skills in an AI coding workspace, audit the multi-graph context topology using health metrics that identify unreachable nodes and connectivity failures. This flags orphan risk and remediates nodes in blast-radius order.

What is a multi-graph context architecture for managing AI agent memory and skills?

A multi-graph context architecture structures an AI workspace into a skill knowledge graph, document routing graph, memory index, and script registry. It enforces typed relations and cross-graph edges to keep context navigable, consistent, and change-propagating.

How do I prevent stale documentation and silent change propagation failures across my coding agent workspace?

Prevent stale documentation and silent change propagation failures by applying a deterministic propagation checklist that traces a single change across docs, skills, memory, and scripts, ensuring cross-graph edges are explicitly modeled and updated.

Does my workspace need typed relation discipline and edge-type caps to avoid hub-and-spoke degeneration?

Typed relation discipline with per-edge caps is required to avoid hub-and-spoke degeneration in large skill libraries. Modeling and capping adjacent, boundary, and verify_with relations reduces edge inflation and maintains graph health.

When do I need to audit cross-graph edges during a workspace refactor or PR review?

Audit cross-graph edges during workspace refactors or PR review when diagnosing stale propagation obligations and ensuring edge-type caps remain correct. This prevents ignored cross-graph edges and AI-inferred rebuild drift.

What are the limitations of using AI-inferred graph synthesis signals for workspace context routing?

AI-inferred graph synthesis signals risk rebuild drift and ignored cross-graph edges if not deterministic. Limitations include edge inflation and one-way edges, requiring reproducible inputs like frontmatter relations and explicit labels to maintain graph health.