Agentdb Query
- 648 installs
- 67k repo stars
- Updated August 4, 2026
- ruvnet/ruflo
agentdb-query is a Claude Code skill that exposes 15 AgentDB MCP controller-bridge tools for hierarchical memory recall, semantic routing, causal graph edges, and pattern search for developers who need structured cross-s
About
agentdb-query is a Ruflo skill in ruvnet/ruflo that teaches coding agents to query AgentDB through the @claude-flow controller bridge using 15 agentdb_* MCP tools. The documented 7-step workflow runs health check, session start, hierarchical store and recall across working, episodic, and semantic tiers, ReasoningBank-routed pattern search, context synthesis, and causal-edge graph linking. Developers reach for agentdb-query when Claude Code or Cursor agents must persist decisions, trajectories, and learned patterns across sessions instead of flat memory_store keys. The skill covers namespace routing rules, three operational fallback modes, and CLI alternatives via npx @claude-flow/cli memory commands when the bridge is unavailable.
- Query any SQLite, PostgreSQL, or vector database from within agent sessions
- Supports natural language to SQL translation with schema awareness
- Returns structured JSON results ready for downstream agent steps
- Works with local files, remote APIs, and embedded vector indexes
- Zero-install MCP server pattern for instant agent memory
Agentdb Query by the numbers
- 648 all-time installs (skills.sh)
- +10 installs in the week ending Jul 26, 2026 (Skillselion tracking)
- Ranked #1,491 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/ruvnet/ruflo --skill agentdb-queryAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 648 |
|---|---|
| repo stars | ★ 67k |
| Last updated | August 4, 2026 |
| Repository | ruvnet/ruflo ↗ |
How do you query AgentDB hierarchical memory from agents?
Query structured knowledge bases and vector stores directly from Claude, Cursor or other agents.
Who is it for?
Developers building Claude Code or Cursor agents with Ruflo who need structured, cross-session vector memory beyond flat memory_store and memory_search.
Skip if: Developers who only need one-off key-value notes without tiers, causal graphs, or ReasoningBank pattern routing should use basic memory_* tools instead.
When should I use this skill?
Fire when an agent must store, retrieve, search, or synthesize structured knowledge across sessions using AgentDB controller-bridge MCP tools.
What you get
Persisted hierarchical memories across working/episodic/semantic tiers, ReasoningBank pattern matches, synthesized context bundles, causal graph edges, and session-scoped AgentDB controller state.
- tier-keyed hierarchical memories
- ReasoningBank pattern search results
- causal graph edge links
By the numbers
- Exposes 15 agentdb_* MCP tools through the controller bridge
- Supports 3 hierarchical memory tiers: working, episodic, and semantic
- agentdb_batch accepts up to 500 entries per call
Files
AgentDB Query
Query and manage AgentDB through the controller bridge. AgentDB exposes 15 agentdb_* MCP tools; this skill enumerates the standard usage path.
When to use
When you need to store, retrieve, or search knowledge across agent sessions. AgentDB provides hierarchical storage, causal knowledge graphs, semantic routing, and context synthesis.
Steps
1. Check health — mcp__claude-flow__agentdb_health. Sanity-check available: true. 2. Start session — mcp__claude-flow__agentdb_session-start if not already active. 3. Store knowledge — mcp__claude-flow__agentdb_hierarchical-store for structured tier-keyed data (tiers: working|episodic|semantic). 4. Recall knowledge — mcp__claude-flow__agentdb_hierarchical-recall with a query. 5. Search patterns — mcp__claude-flow__agentdb_pattern-search for learned patterns (ReasoningBank-routed). 6. Synthesize context — mcp__claude-flow__agentdb_context-synthesize to combine multiple memories. 7. Build causal graph — mcp__claude-flow__agentdb_causal-edge to link related knowledge.
Available controller groups
Call mcp__claude-flow__agentdb_controllers to list the runtime registry. Functional categories surfaced via the 15 MCP tools:
- Hierarchical —
agentdb_hierarchical-store,_recall(tier-routed) - Pattern —
agentdb_pattern-store,_search(ReasoningBank-routed) - Semantic —
agentdb_semantic-route,_context-synthesize - Causal —
agentdb_causal-edge(graph-node backend with bridge fallback) - Lifecycle —
agentdb_health,_controllers,_session-start,_session-end - Bulk —
agentdb_batch(≤500 entries),_consolidate - Quality —
agentdb_feedback
Important: namespace handling
Namespace strings apply to memory_* and embeddings_search only. The agentdb_hierarchical-*, agentdb_pattern-*, and agentdb_causal-edge tools route by tier or controller, not namespace. Don't pass namespace: 'foo' to those tools — it will be silently ignored. See plugin README "Namespace convention".
Operational fallbacks (branch on these)
controller: 'memory-store-fallback'— pattern persisted viamemory_store --namespace pattern. NOT a failure._graphNodeBackend: true— causal-edge handled by@ruvector/graph-node.success: false, error: '...Use memory_store/memory_search instead.'— bridge unavailable; switch tomemory_*tools per the README replacement table.
CLI alternative
npx @claude-flow/cli@latest memory search --query "your query" --namespace patterns
npx @claude-flow/cli@latest memory store --key "key" --value "value" --namespace patterns
npx @claude-flow/cli@latest memory list --namespace patternsRelated skills
Setup Matt Pocock SkillsScaffold the per-repo configuration that Matt Pocock’s engineering agent skills rely on so they understand the issue tracker, triage labels, and domain documentation la495k196k
Lark AppsConnect Claude, Cursor or custom agents directly to Lark (Feishu) for messaging, document automation, approval workflows and enterprise data access.402k
CavemanSlash token usage by roughly 75% while keeping every technical detail intact when working with Claude Code, Cursor or similar agents.391k94.7k
Lark Skill MakerQuickly turn any Lark/Feishu OpenAPI call or multi-step workflow into a reusable agent skill with its own SKILL.md.386k16k
Running Claude Code Via Litellm CopilotRun Claude Code at a fraction of the cost by routing requests through LiteLLM to the GitHub Copilot Chat API.270k72
Codex PetGenerate a complete Codex Pet spritesheet and metadata from one reference image without needing an OpenAI key or Codex Pro.246k10How it compares
Choose agentdb-query over flat memory_store when agents need tiered recall, ReasoningBank pattern routing, causal graph edges, or synthesized multi-memory context rather than simple key-value persistence.
FAQ
How many MCP tools does agentdb-query expose?
agentdb-query documents 15 agentdb_* MCP tools through the @claude-flow controller bridge, covering hierarchical store/recall, semantic routing, pattern search, causal edges, context synthesis, batch ops, consolidation, feedback, and session lifecycle.
What memory tiers does AgentDB hierarchical storage use?
agentdb-query routes agentdb_hierarchical-store and agentdb_hierarchical-recall by tier, not namespace. Supported tiers are working, episodic, and semantic, enabling structured short-term and long-term agent memory separation.
What happens when the AgentDB bridge is unavailable?
agentdb-query defines fallback paths: pattern-store uses memory_store under the pattern namespace, semantic routing falls back to embeddings_search, and bridge-unavailable errors direct agents to memory_store and memory_search per the plugin replacement table.