Pathfinder traversal of the knowledge graph starting from a seed entity
How this skill is triggered — by the user, by Claude, or both
Slash command
/swarmdo-knowledge-graph:kg-traverse <entity> [--depth N]<entity> [--depth N]This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Perform pathfinder graph traversal starting from a seed entity. Expands outward through causal edges, scores paths by relevance, and prunes low-similarity branches.
Perform pathfinder graph traversal starting from a seed entity. Expands outward through causal edges, scores paths by relevance, and prunes low-similarity branches.
When you need to explore the knowledge graph starting from a specific entity -- finding what depends on it, what it depends on, or discovering indirect relationships. Useful for impact analysis, dependency chains, and understanding code structure.
mcp__swarmdo__agentdb_hierarchical-recall to look up the target entity by namemcp__swarmdo__agentdb_causal-edge to find all edges connected to the seed entity, then recursively expand outward to the specified depth (default: 3)cumulative_score = product(edge_weight * keyword_similarity(query, node)) using mcp__swarmdo__agentdb_pattern-search (the semanticRouter controller is enabled: false in current AgentDB builds; pattern-search is the available substitute and works fine for entity-name + relation-type keyword matches — see upstream/swarmdo#2049). For higher-fidelity semantic similarity, callers can fall back to mcp__swarmdo__embeddings_generate + manual cosine, but that's not required for step 3 to function.mcp__swarmdo__agentdb_context-synthesize to combine the top paths into a coherent summarynpx @swarmdo/cli@latest memory search --query "relations for ENTITY_NAME" --namespace knowledge-graph
Guides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Implements work from a spec or tickets using TDD at agreed seams, with regular typechecking and test runs, followed by code review.
npx claudepluginhub swarmdo/swarmdo --plugin swarmdo-knowledge-graph