Results for “knowledge graph”

Build and troubleshoot TorchDrug 0.2.1 workflows for molecular property prediction, molecule generation, protein modeling, and knowledge graph reasoning. Connect datasets, models, training tasks, and evaluation while checking version compatibility and common implementation errors.

• Training and evaluating molecular property prediction models
• Building molecule generation workflows
• Learning representations of protein sequences and structures

Find the right GitNexus tools and workflows for exploring code relationships. This reference explains available commands, graph queries, and resources, including how to check which branch an answer describes and whether its index is current.

• Find a GitNexus tool for a specific task
• Learn how to query code relationships
• Check index freshness and branch information

Review all changes in a pull request or branch against its base branch. Use a knowledge graph, a map of code relationships, to report affected files and functions, test coverage, API compatibility issues, and recommended actions.

• Reviewing all commits in a pull request
• Checking a branch's changes against its base
• Finding callers missed by public API changes

Explore an unfamiliar codebase using a graph of code relationships. Inspect its structure, find functions and classes, trace calls and imports, follow execution paths, and locate large functions for closer investigation.

• Understanding the structure of an unfamiliar codebase
• Finding functions and classes by name or keyword
• Tracing calls, imports, and execution paths

Routes requests about a codebase to the appropriate skill for mapping its structure, generating knowledge graphs, updating documentation, extracting lessons, or storing and recalling project knowledge for future planning.

• Understand the structure of an unfamiliar codebase
• Update project documentation
• Recall earlier decisions before planning

When the user wants to optimize for entity recognition, Knowledge Graph, or entity-based SEO. Also use when the user mentions "entity SEO," "entity optimization," "Knowledge Graph," "Knowledge Panel," "entity signals," "brand entity," "entity linking," "entity relationships," or "entity-first content." For structured data, use schema-markup.

The English summary is being prepared. Showing the original description.

Knowledge graph integration for token-efficient codebase understanding. Uses codebase-memory MCP for AST indexing, dependency graphs, and smart context selection. 6-71x token savings vs raw file reading.

The English summary is being prepared. Showing the original description.

Graph database implementation for relationship-heavy data models. Use when building social networks, recommendation engines, knowledge graphs, or fraud detection. Covers Neo4j (primary), ArangoDB, Amazon Neptune, Cypher query patterns, and graph data modeling.

The English summary is being prepared. Showing the original description.

Use code-review-graph for local-first CLI/MCP code knowledge graphs, graph-backed code review, structural search, and repository-analysis integrations.

The English summary is being prepared. Showing the original description.

Operate the Agriculture_KnowledgeGraph agricultural Neo4j graph, Django demo, entity labeling, crawler, and relation-extraction workflows.

The English summary is being prepared. Showing the original description.

Use when analyzing vault structure, finding orphan notes, discovering missing connections, identifying bridge concepts, or checking vault health from a graph perspective. Triggers on "vault graph", "map vault", "find orphans", "missing links", "vault structure", "knowledge graph".

The English summary is being prepared. Showing the original description.

Fires after fixing any non-trivial bug or regression. Asks: could the graph have caught this as a guarantee? Pairs with reflection-in-and-on-action — picks up after "earliest catchable signal" and asks the next question: was that signal expressible in graph? Triggers: (1) after any non-trivial bug fix is verified working, (2) after a regression report (something used to work, broke), (3) during step 6 (knowledge extraction) of the workflow, (4) when reflection-on-action surfaces a "would have been catchable" signal. Outcome is a triage decision (graph-reachable? rule expressible? rule sound?) and either a draft Linear issue + guarantee proposal, or a recorded "graph capability gap" note. Never auto-creates guarantees.

The English summary is being prepared. Showing the original description.

Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community detection, and query/path/explain tools.

The English summary is being prepared. Showing the original description.

Manage knowledge graph for autonomous coding. Use when storing relationships, querying connected knowledge, building project understanding, or maintaining semantic memory.

The English summary is being prepared. Showing the original description.

Data structures and algorithms for AI agent episodic memory. Covers vector stores (HNSW, IVF, PQ), temporal indexing, knowledge graphs with triple stores, hierarchical summarization, forgetting curves, working/long-term/ procedural memory, and memory consolidation. Deep analysis of MemGPT/Letta, Zep/Graphiti, Mem0, and the Stanford generative agents memory architecture. Teaches the CS fundamentals behind how agents remember, retrieve, and forget. Activate on: "agent memory", "episodic memory", "vector search algorithm", "HNSW", "memory retrieval", "forgetting curve", "knowledge graph memory", "MemGPT", "Letta", "Zep", "Mem0", "memory consolidation", "temporal retrieval", "agent long-term memory", "memory layer". NOT for: conversation protocol design (use agent-conversation-protocols), agent infrastructure selection (use agentic-infrastructure-2026), building RAG pipelines (use ai-engineer).

The English summary is being prepared. Showing the original description.

Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community detection, and query/path/explain tools.

The English summary is being prepared. Showing the original description.

Data structures and algorithms for AI agent episodic memory. Covers vector stores (HNSW, IVF, PQ), temporal indexing, knowledge graphs with triple stores, hierarchical summarization, forgetting curves, working/long-term/ procedural memory, and memory consolidation. Deep analysis of MemGPT/Letta, Zep/Graphiti, Mem0, and the Stanford generative agents memory architecture. Teaches the CS fundamentals behind how agents remember, retrieve, and forget. Activate on: "agent memory", "episodic memory", "vector search algorithm", "HNSW", "memory retrieval", "forgetting curve", "knowledge graph memory", "MemGPT", "Letta", "Zep", "Mem0", "memory consolidation", "temporal retrieval", "agent long-term memory", "memory layer". NOT for: conversation protocol design (use agent-conversation-protocols), agent infrastructure selection (use agentic-infrastructure-2026), building RAG pipelines (use ai-engineer).

The English summary is being prepared. Showing the original description.

Manage knowledge graph for autonomous coding. Use when storing relationships, querying connected knowledge, building project understanding, or maintaining semantic memory.

The English summary is being prepared. Showing the original description.

Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community detection, and query/path/explain tools.

The English summary is being prepared. Showing the original description.

Search and edit notes in a SiYuan knowledge base through its API. Find text, read individual content blocks, create documents, update paragraphs, rename or delete notes, and export documents as Markdown.

• Search existing notes by keyword
• Save meeting notes as a new document
• Append or update paragraphs in a note

Turn a codebase into an interactive graph of code relationships. Explore functions, call chains, related groups, and execution flows in a browser, with optional Cloudflare tunneling to share the explorer remotely.

• Explore the architecture of an unfamiliar codebase
• Trace function calls and execution flows
• Share an interactive code graph remotely

Create an onboarding guide for new project members from a knowledge graph, a map of project components. The Markdown guide covers architecture, key concepts, a suggested learning path, important files, and areas that need extra care.

• Preparing a guide for new team members
• Organizing project architecture and key files
• Planning a codebase walkthrough

Get a detailed explanation of a file, function, or module using an existing knowledge graph and its source code. It explains architectural roles, dependencies, callers, and data flow for readers who may not know the programming language.

• Understand the role of a specific file
• Trace a function’s callers and dependencies
• Follow inputs, processing, and outputs

Investigate a username, file, code identifier, URL, or concept by exploring connected entities across relevant sources. Produce a dossier with a summary, relationship diagram, source references, and a machine-readable JSON graph.

• Mapping connections around a username or concept
• Investigating references to a file or code identifier
• Tracing links to an architecture decision record