graph-context

name

graph-context

description

Fetch relevant context from the workspace knowledge graph for lazy context loading. Use when answering questions about projects, tasks, deadlines, people, or any topic covered by the knowledge graph (02_distill/). Replaces eager-loading of full USER.md, TOOLS.md, and other large files. Triggers on any query that needs project context, task status, collaborator info, or cross-cluster connections. Also use at session start to load minimal relevant context instead of reading entire workspace files.

Graph Context — Lazy Knowledge Loading

Pull only the relevant slice of the knowledge graph into context, instead of loading everything at startup.

When to Use

• User asks about a project, task, deadline, or collaborator
• Session startup: load compact context index instead of full files
• Cross-cluster queries ("how does seo relate to knowledge_mgmt?")
• Any question where 02_distill/ cards hold the answer

Usage

Quick context fetch (by cluster)

python3 skills/graph-context/scripts/graph_context.py --cluster knowledge_mgmt

Search by query (keyword match across titles, tags, content)

python3 skills/graph-context/scripts/graph_context.py --query "дедлайн навчальна сесія"

Full index (compact summary of all nodes — for orientation)

python3 skills/graph-context/scripts/graph_context.py --index

Get specific node by ID

python3 skills/graph-context/scripts/graph_context.py --node task_ai_assistant_prototype

Output Format

The script outputs compact markdown optimized for retrieval-first routing:

• node title, type, cluster, tags
• summary when present
• retrieval_hints when present
• canonical_artifacts when present
• source_kind / sensitivity when present
• fallback to a short raw-content preview only when retrieval metadata is absent

For --node it returns the full card content plus retrieval metadata fields.

Clusters Reference

Cluster	Domain
knowledge_mgmt	Centralized knowledge base, Notion sync, RAG pipeline
seo	SEO analysis, marketing, promotion strategy
finance	Financial monitoring, budgeting, forecasting
legal	Legal documentation, compliance, contracts
confidential	Restricted / sensitive data

When NOT to Use

• Simple greetings or chitchat (no graph needed)
• Questions already answered in current conversation context
• File operations that don't need project context