'knowledge graph' 검색 결과

Use when the user asks a question about how things in the codebase or wiki relate — what connects two things, how something works end to end, what depends on what, or what a concept means in this repo. Answers from the knowledge graph in graphify-out/graph.json, with source-location citations. Trigger on "/graph-query", "ask the graph", "what connects X to Y", "trace how X works", "explain <concept> from the graph", "shortest path between".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Ask questions about a codebase using a knowledge graph, a map of its components and relationships. Get explanations tied to specific files, functions, dependencies, and architectural layers, with warnings when the graph may be outdated.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Understanding how a feature works
• Finding callers and dependencies
• Locating code related to a concept

Explore code structure and history using an index of code relationships and meaning-based search. Trace calls, assess change impact, find likely bug locations, generate architecture reports, and review pull requests for risk and conflicts.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Tracing function calls and change impact
• Investigating code locations related to a GitHub issue
• Generating architecture reports and class diagrams

Explore relationships between functions and files using a prebuilt code graph, a map of code dependencies. Trace bugs, inspect callers and execution paths, and assess the impact of refactoring or proposed changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Explore callers and dependencies in unfamiliar code
• Trace a bug across multiple files
• Assess the impact of renaming or removing code

Design a dark slide deck for AI products, knowledge graphs, or developer tool launches. Combine a graph-based cover, glowing blurred shapes, gradient section titles, highlighted code or command-line examples, and frosted-glass-style cards.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Prepare slides introducing an AI product
• Present a knowledge graph project
• Create a developer tool launch deck

Build structured knowledge graphs from unstructured text by extracting entities, mapping relationships, generating graph triples, and visualizing the result. Use when the user requests knowledge graph creation or provides relevant inputs for this workflow.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design, build, evaluate, or teach graph-based systems. Use for knowledge graphs, ontology/schema design, entity/relation/event extraction, entity resolution and fusion, GraphRAG or graph memory, and agent/task dependency graphs with concurrency, joins, failure handling, verification, or human gates.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Entity and relation tracking skill using MCP memory server patterns and local knowledge graph storage. Build persistent knowledge graphs of entities, relationships, and observations across agent sessions. Covers the MCP memory server (@modelcontextprotocol/server-memory), local JSON-based graphs, and entity-relation querying patterns for long-running agents.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when needing global or relational understanding of codebases or knowledge corpora. Keywords: GraphRAG, knowledge graph, entity extraction, community summarization, graph traversal, Microsoft GraphRAG.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Obsidian Claw is an ontology-building skill that transforms chaotic notes, raw ideas, voice dumps, and meeting transcripts into a structured, interlinked knowledge base inside Obsidian. Use this skill whenever the user wants to: add new notes to their Obsidian vault and auto-link them to existing ones, build a concept graph or knowledge map, surface forgotten related discussions ("you talked about this with investor X 3 months ago"), extract entities and relationships from unstructured text, or turn scattered thoughts into wiki-style atomic notes. Also trigger when the user mentions "second brain", "Zettelkasten", "PKM", "personal knowledge management", "note graph", "knowledge graph", "link my notes", "organize my vault", "connect ideas", or asks Claude to "remember" something across sessions using Obsidian. If the user is doing anything with Obsidian notes and wants intelligence layered on top, use this skill.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

A persistent, compounding knowledge base combining Karpathy's LLM Wiki pattern with a structured knowledge graph. Ingest documents once — the LLM writes wiki pages, extracts entities/relations into the graph, and stores raw content for evidence retrieval. Knowledge accumulates and cross-references; it is never re-derived from scratch. Use when building a knowledge base from many documents that should accumulate and cross-reference over time instead of being re-read each session.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Analyze project code, configuration, and documentation to build a graph for interactive architecture exploration. It maps components and dependencies, supports Japanese descriptions, and can update the analysis based on changes since the previous analyzed commit.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Understand the structure of an unfamiliar project
• Explore dependencies between components
• Generate architecture descriptions in Japanese

Extract classes, functions, modules, and their relationships from source code or documentation into AgentDB. Build a knowledge graph, a map of connected entities, to understand code structure, dependencies, and potential change impacts.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Understanding a codebase's structure
• Investigating dependencies between modules
• Assessing the impact of code changes

Explore a knowledge graph, a network of entities and relationships, from a chosen starting point. Rank relevant paths and summarize dependencies or indirect connections to help understand code structure and assess the impact of changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Assessing the impact of changing a component
• Tracing dependency chains
• Discovering indirect connections between entities

Define custom entities and relationships in cognee, a memory system for AI applications. This skill guides model design, identity matching, searchable fields, and troubleshooting when entities are duplicated or relationships are missing.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Designing custom entities and relationships
• Preventing duplicate entities across imports
• Investigating missing search results or relationships

Provides authoritative guidance on Amazon Neptune Database and Neptune Analytics for graph, knowledge-graph, and relationship-heavy workloads — fraud detection / fraud rings, agentic memory / chatbot context across sessions, recommendations, identity resolution, Gremlin / openCypher / SPARQL queries, supernode / slow traversal, Neo4j to Neptune migration / APOC compatibility, Neptune Database vs Analytics engine selection, PageRank / community detection, GraphRAG, and connectivity from Lambda / EC2 / applications. Creates and modifies Neptune Database clusters/instances and Neptune Analytics graphs on explicit user confirmation; blocks destructive operations (delete, reset-graph, failover, major upgrade) and redirects to change-control.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Reference for querying the Atlas knowledge graph through its MCP tools — the SECONDARY enrichment/comparison layer that adds best-practice context to systems you have ALREADY scanned from your real sources (`az`, repos, dirs). Use when you need to look up nodes, edges, kinds, clusters, stats, or wiki pages in Atlas to compare against your real inventory. (atlas graph, query atlas, atlas mcp, search the graph, graph neighbors, atlas record, atlas kinds, enrichment layer)

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use `graphify-dotnet` to generate codebase knowledge graphs, architecture snapshots, and exportable repository maps from .NET or polyglot source trees, with optional AI-enriched semantic relationships. USE FOR: graphify commands; graph JSON, HTML, SVG, Cypher, Markdown, and Obsidian exports; repository map and architecture snapshot generation. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Analyze indexed codebases via graph database (neug) and vector index (zvec). Covers call graphs, dependencies, dead code, hotspots, module coupling, architecture reports, semantic search, impact analysis, bug root cause from GitHub issues, class diagrams (UML), and PR review (risk scoring, conflict detection, auto-merge candidates, labeling). Also covers creating, inspecting, and repairing a CodeScope index. Use for: code structure, who calls what, why something changed, similar functions, module boundaries, bug tracing, class relationships, PR risk/conflicts, or any question benefiting from a code knowledge graph. Applies when a `.codegraph` index exists in the workspace, or when the user wants to create one.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user brings an external source worth keeping — a URL, a paper, a tweet/thread, a blog post, a docs page — and wants it pulled into the second brain. Fetches the source into the git-ignored capture inbox, admits it to the committed wiki through the admission policy, then refreshes the knowledge graph so it joins the rest of your thinking. Trigger on "/graph-ingest", "ingest this url", "add this paper to my knowledge", "add this tweet/page to my knowledge", "capture this source".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Query the Precision Medicine Knowledge Graph (PrimeKG) for multiscale biological relationships across genes and proteins, drugs, diseases, phenotypes, pathways, biological processes, exposures and anatomy. Use this skill to search entities by name, pull direct neighbours and their evidence types, summarise the local network around a disease, and find direct or two-hop drug-disease connections for repurposing hypotheses. Also trigger on PrimeKG, kg.csv, Harvard Dataverse knowledge graph, disease_protein, drug_protein, indication and contraindication edges, or network pharmacology over a biomedical knowledge graph.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guides implementation of agent memory systems, compares production frameworks (Mem0, Zep/Graphiti, Letta, LangMem, Cognee), and designs persistence architectures for cross-session knowledge retention. Use when the user asks to "implement agent memory", "persist state across sessions", "build knowledge graph for agents", "track entities over time", "add long-term memory", "choose a memory framework", or mentions temporal knowledge graphs, vector stores, entity memory, adaptive memory, dynamic memory or memory benchmarks (LoCoMo, LongMemEval).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build charts and interactive data visualizations with D3.js, a JavaScript library for drawing data graphics. Examples across chart types support reports, dashboards, explanatory graphics, and prototypes that let readers explore data.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Exploring sales data with a zoomable treemap
• Showing relationships in a force-directed network graph
• Displaying daily patterns in a calendar heatmap

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