From graphiti-context-hub
Deep exploration of Graphiti knowledge graph. Use when investigating connections, tracing decisions, or understanding architectural evolution.
npx claudepluginhub geojaz/graphiti-context-hub --plugin graphiti-context-hubThis skill is limited to using the following tools:
**Deep graph exploration:**
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Retrieves current documentation, API references, and code examples for libraries, frameworks, SDKs, CLIs, and services via Context7 CLI. Ideal for API syntax, configs, migrations, and setup queries.
Uses ctx7 CLI to fetch current library docs, manage AI coding skills (install/search/generate), and configure Context7 MCP for AI editors.
Deep graph exploration:
Step 1: Find starting point
source "$HOME/.config/claude/graphiti-context-hub.conf" 2>/dev/null
GROUP_ID="${GRAPHITI_GROUP_ID:-main}"
REPO_NAME=$(git remote get-url origin 2>/dev/null | sed 's/.*\///' | sed 's/\.git$//' || basename "$PWD")
# Find starting nodes
starting_nodes = mcp__graphiti__search_nodes({
"query": "authentication architecture",
"group_ids": [GROUP_ID],
"max_nodes": 5
})
Step 2: Explore relationships
# Get facts related to the topic
facts = mcp__graphiti__search_memory_facts({
"query": "authentication dependencies relationships",
"group_ids": [GROUP_ID],
"max_facts": 30
})
# Analyze fact patterns
for fact in facts.get('facts', []):
print(f"Relationship: {fact.get('fact')}")
print(f" From: {fact.get('source_node_uuid')}")
print(f" To: {fact.get('target_node_uuid')}")
Step 3: Get episode context
# Get episodes (chronological context)
episodes = mcp__graphiti__get_episodes({
"group_ids": [GROUP_ID],
"max_episodes": 20
})
# Look for evolution over time
for ep in episodes.get('episodes', []):
if 'authentication' in ep.get('name', '').lower():
print(f"{ep.get('created_at')}: {ep.get('name')}")
Pattern 1: Trace a decision's evolution
Pattern 2: Understand component dependencies
Pattern 3: Find reusable patterns
Present findings as:
## Exploration: [Topic]
### Central Entities
- Entity 1: Description
- Entity 2: Description
### Key Relationships
- Entity A → Entity B: Relationship type
- Entity B → Entity C: Relationship type
### Evolution Timeline
- [Date]: Initial decision
- [Date]: Refinement
- [Date]: Current state
### Insights
- Pattern discovered
- Dependency identified
- Trade-off understood
❌ Exploring without a clear starting query ❌ Looking only at nodes without checking facts ❌ Ignoring temporal context (episode chronology) ❌ Not synthesizing findings into actionable insights