Loading...
Loading...
Found 59 Skills
Knowledge graph specialist for entity and causal relationship modelingUse when "knowledge graph, graph database, falkordb, neo4j, cypher query, entity resolution, causal relationships, graph traversal, graph-database, knowledge-graph, falkordb, neo4j, cypher, entity-resolution, causal-graph, ml-memory" mentioned.
Build a graph-structured dossier on a seed entity via parallel fan-out + recursive expansion across web, memory, knowledge-graph, codebase, ADR index, and git intel
Inspect and debug KGF (Knowledge Graph Framework) specs — tokenize, parse, and extract edges from source files. Use when the user wants to debug language parsing, inspect how indexion processes a file, or verify KGF spec behavior.
This skill should be used when the user asks to "implement agent memory", "persist state across sessions", "build knowledge graph", "track entities", or mentions memory architecture, temporal knowledge graphs, vector stores, entity memory, or cross-session persistence.
Advanced RAG with Self-RAG, Corrective-RAG, and knowledge graphs. Use when building agentic RAG pipelines, adaptive retrieval, or query rewriting.
Manage Draxarp Intelligence — projects, tasks, specs, docs, memories, sprints, knowledge graph, context captures, and task decomposition via orbit CLI
Use when you need to generate an onboarding guide for new team members joining a project
Inspect and edit the workspace's git-backed context repository (the GTM knowledge base of markdown/MDX files) and its runtime sandbox using the Cargo CLI. Use when the user wants to browse/read/write/edit context files, run a command in the sandbox, or inspect the context knowledge graph.
Synthesize multiple media analyses into cross-source patterns and insights. Use when you need to cross-reference analyses, find patterns across sources, or perform meta-analysis of media content.
Use when you need to ask questions about a codebase or understand code using a knowledge graph
Use when you need to analyze git diffs or pull requests to understand what changed, affected components, and risks
Use when designing database schemas, need to model domain entities and relationships clearly, building knowledge graphs or ontologies, creating API data models, defining system boundaries and invariants, migrating between data models, establishing taxonomies or hierarchies, user mentions "schema", "data model", "entities", "relationships", "ontology", "knowledge graph", or when scattered/inconsistent data structures need formalization.