agentdb-setup-diagnostics
/agentdb-setup-diagnostics
Konfiguruje wtyczkę AgentDB i jej serwer MCP oraz sprawdza profil, bazę i połączenie, gdy narzędzia nie działają.
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 11.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Konfiguruje wtyczkę AgentDB i jej serwer MCP oraz sprawdza profil, bazę i połączenie, gdy narzędzia nie działają.
Wyzwalacze z opisu
Oryginalny opis (EN)
Set up and diagnose the agentdb plugin and its MCP server — which profile and database are in use, whether the server is connected, what it holds, and why a tool is missing or refused. Use when AgentDB tools are missing, a call is refused, the user asks "is agentdb working", or wants to change the profile or database path.
Jak działa
- 1. Is the server connected?
- 2. What is it running on?
- 3. What does it hold?
- 4. Why is a tool missing?
- 5. Why was a call refused?
- 6. Change settings
Podgląd SKILL.md
--- name: agentdb-setup-diagnostics description: Set up and diagnose the agentdb plugin and its MCP server — which profile and database are in use, whether the server is connected, what it holds, and why a tool is missing or refused. Use when AgentDB tools are missing, a call is refused, the user asks "is agentdb working", or wants to change the profile or database path. allowed-tools: - mcp__plugin_agentdb_agentdb__agentdb_capabilities - mcp__plugin_agentdb_agentdb__agentdb_stats - mcp__plugin_agentdb_agentdb__db_stats - mcp__plugin_agentdb_agentdb__agentdb_pattern_stats - mcp__plugin_agentdb_agentdb__learning_metrics - Bash(claude mcp list) - Bash(claude plugin details agentdb) --- # AgentDB setup and diagnostics ## 1. Is the server connected? Run `/agentdb-guard status`: it reports the guard's modes and how many `agentdb` tools are connected. No tools means the server did not start; check `claude mcp list` for `plugin:agentdb:agentdb` and its error. The server runs `npx -y agentdb@<plugin version> mcp start`, so the first start downloads the package and needs network access and Node 18 or later. ## 2. What is it running on? `agentdb_capabilities()` (read-only, agentdb 3.1.0) reports the native accelerator capabilities and the backend in use: the vector backend (ruvector native, rvf or stub), the SQL driver, and the embedding model and dimension. A `stub` vector backend or a fallback SQL driver explains slow or low-quality search. ## 3. What does it hold? - `agentdb_stats(detailed: true)`: table counts, storage, performance. - `db_stats()`: record counts. - `agentdb_pattern_stats()`: patterns, success rates, top task types. - `learning_metrics()`: RL session success rates and rewards. An empty database is normal on first use. Data lives in `AGENTDB_PATH` (the `db_path` option), else `./agentdb.db` in the directory Claude Code started the server from, so a different project directory means a different database. ## 4. Why is a tool missing? The server only lists the tools its profile allows (`mcp_profile` option, env `AGENTDB_MCP_PROFILE`): | Profile | Tools | |---|---| | `readonly` / `retrieval` | search, stats, recall, predict | | `learning` (default, also when empty) | the above plus memory writes, reflexion, skills, causal edges, RL and pattern/skill feedback, `agentdb_capabilities` | | `admin` | everything, including `agentdb_init`, `agentdb_delete`, `agentdb_delete_batch`, `agentdb_clear_cache` | `mcp_allow` adds named tools to a profile (an admin-only tool named there is exposed too); `mcp_deny` removes them in any profile. A hidden tool called anyway returns "not permitted by the active AgentDB capability policy". An unknown profile name stops the server from starting. ## 5. Why was a call refused? The plugin's mod refuses, before the server sees them: - memory writes that hold what looks like a secret (`secret_guard`: `enforce` default, `notify`, `off`). `/agentdb-guard scan <text>` names the rule a text trips, never the value. - the destructive tools above, and `agentdb_init` with `reset: true` (it drops every table in the open database), unless `allow_destructive` is on. Using them takes both exposing them (`mcp_profile=admin`, or naming them in `mcp_allow`) and `allow_destructive`. ## 6. Change settings `/plugin configure agentdb@agentdb` (or `claude plugin configure agentdb`), then restart the session so the server restarts with the new environment.
Wersje
W bazie nie ma innych skilli o nazwie agentdb-setup-diagnostics.
Migawka bazy z 13.11.2026 · wersja paczki 6510ca3786b2 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100agentdb-init
Inicjalizuje w projekcie kontener AgentDB Cognitive Container (plik .rvf): magazyn, konfigurację embeddera i serwer MCP agentdb. - 95agentdb-vector-memory
Zapisuje i przywołuje pamięć agenta przez serwer MCP AgentDB, czyli fakty, wzorce rozumowania i sprawdzone odtworzenia. - 81mcp-setup
Instaluje, konfiguruje i diagnozuje serwer MCP dla wybranego narzędzia, gdy jego narzędzia nie działają lub brakuje. - 90AgentDB Memory Patterns
Wdraża w agentach AI trwałą pamięć w AgentDB: pamięć sesji, uczenie wzorców i zarządzanie kontekstem. - 90AgentDB Memory Patterns
Wdraża wzorce trwałej pamięci dla agentów AI w AgentDB: pamięć sesji, długoterminowe przechowywanie i zarządzanie kontekstem. - 90AgentDB Memory Patterns
Wdraża trwałe wzorce pamięci agentów AI z AgentDB: pamięć sesji, długoterminowe przechowywanie, uczenie wzorców i zarządzanie kontekstem.