knowledge-graph-agentsAdd a knowledge graph layer to an AI agent for relationship reasoning and multi-hop recall. Use when agents need to answer "who works with whom", "what's con...
Install via ClawdBot CLI:
clawdbot install vnesin-sarai/knowledge-graph-agentsGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Generated May 19, 2026
A sales team uses a knowledge graph to answer multi-hop queries like 'who at Acme Corp works with Alice?' or 'which accounts use our product and have a referral from Bob?'. This enables account mapping and warm introductions that flat search cannot provide.
An IT operations agent uses a graph to traverse dependencies between servers, databases, and microservices. For example, 'what services are on the production server?' or 'which applications depend on PostgreSQL?'. This aids in outage impact analysis and change management.
A research assistant extracts entities (authors, institutions, methods) from papers and creates co-occurrence edges. Queries like 'which papers use Graph Neural Networks and cite work by Jane Smith?' yield multi-hop results, enabling literature review acceleration.
A legal AI ingests contracts and case law, extracting parties, jurisdictions, and clauses. Users ask 'which contracts involve Acme Corp and mention force majeure?' or 'which cases reference this precedent?'. Graph traversal finds connections missed by keyword search.
A recruiting agent builds a graph of candidates, companies, and skills from resumes and job postings. Queries like 'who worked at Google as a data scientist and knows Kubernetes?' return candidates via skill/company edges, improving matching accuracy.
Offer the knowledge graph layer as a premium feature on top of existing search or agent platforms. Charge per query or per node, with pricing tiers based on graph size and traversal depth.
Provide professional services to build and tune the graph layer for enterprise clients, including entity extraction pipelines, ontology design, and hybrid search integration. Recurring maintenance contracts follow.
Expose the graph querying capability as a REST API (e.g., 'GET /graph/traverse?entity=Alice&hops=2'). Charge per API call or via monthly subscription with rate limits. Ideal for developers embedding graph reasoning into their own agents.
💬 Integration Tip
Start with the SQLite backend and heuristic entity extraction to validate the approach before migrating to Neo4j or adding LLM-based extractors. Embed the graph layer as a separate module that can be toggled on/off for debugging.
Scored May 19, 2026
Structured reasoning through sequential thinking — break complex problems into steps, solve each independently, verify consistency, synthesize conclusions wi...
LLM-driven epistemic reasoning engine. Evaluates claims against evidence, outputs calibrated confidence and structured belief state (VERIFIED/CONTESTED/UNCER...
Loads and manages company context for all C-suite advisor skills. Reads ~/.claude/company-context.md, detects stale context (>90 days), enriches context duri...
Turn scattered local sources into a source-constrained evidence notebook for incident, release, and maintainer decisions.
三级记忆管理系统 (Three-Tier Memory Management)。用于管理 AI 代理的短期、中期、长期记忆。包括:(1) 滑动窗口式短期记忆,(2) 自动摘要生成中期记忆,(3) 向量检索长期记忆 (RAG)。当需要管理对话历史、优化上下文、构建个人知识库、或实现记忆持久化时使用此 Skill。
Store secrets, long-term memory, daily logs, and anything custom in your Convex backend instead of local files