agentdb-query
- Repo stars 54,444
- Author updated Live
- Author repo ruflo
- Domain
- AI
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @ruvnet · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- macOS · Linux · Windows
- Runtime requirements
- Node.js
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: agentdb-query
description: Query AgentDB through the controller bridge -- semantic routing, hierarchical recall, causal gra…
category: ai
runtime: Node.js
---
# agentdb-query output preview
## PART A: Task fit
- Use case: Query AgentDB through the controller bridge -- semantic routing, hierarchical recall, causal graphs, context synthesis, pattern store/search Query and manage AgentDB through the controller bridge. AgentDB exposes 15 agentdb_* MCP tools; this skill enumerates the standard usage path. runs entirely locally; runs on Node.js. Works with Claude Code, Cursor, C….
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “When to use / Steps / Available controller groups” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Query AgentDB through the controller bridge -- semantic routing, hierarchical recall, causal graphs, context synthesis, pattern store/search Query and manage AgentDB through the controller bridge. AgentDB exposes 15 agentdb_* MCP tools; this skill enumerates the standard usage path. runs entirely locally; runs on Node.js. Works with Claude Code, Cursor, C…”.
- **02** When the source has headings, the agent prioritizes “When to use / Steps / Available controller groups” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “When to use / Steps / Available controller groups”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: agentdb-query
description: Query AgentDB through the controller bridge -- semantic routing, hierarchical recall, causal gra…
category: ai
source: ruvnet/ruflo
---
# agentdb-query
## When to use
- Query AgentDB through the controller bridge -- semantic routing, hierarchical recall, causal graphs, context synthesis…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “When to use / Steps / Available controller groups” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "agentdb-query" {
input -> user goal + target files + boundaries + acceptance criteria
context -> When to use / Steps / Available controller groups
rules -> SKILL.md triggers / order / output contract
runtime -> Node.js | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}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
- Check health —
mcp__claude-flow__agentdb_health. Sanity-checkavailable: true. - Start session —
mcp__claude-flow__agentdb_session-startif not already active. - Store knowledge —
mcp__claude-flow__agentdb_hierarchical-storefor structured tier-keyed data (tiers:working|episodic|semantic). - Recall knowledge —
mcp__claude-flow__agentdb_hierarchical-recallwith a query. - Search patterns —
mcp__claude-flow__agentdb_pattern-searchfor learned patterns (ReasoningBank-routed). - Synthesize context —
mcp__claude-flow__agentdb_context-synthesizeto combine multiple memories. - Build causal graph —
mcp__claude-flow__agentdb_causal-edgeto 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 patterns
Decide Fit First
Design Intent
How To Use It
Boundaries And Review