Skip to content

donaldfilimon/abi / .agents/skills/opencode/plugins/wdbx

WDBX vector store operations superpower. Includes insert, query, stats, compaction, secure demos, and REST API.

FileKindSize
SKILL.mdskill md1.7 KB
---
name: wdbx
description: WDBX vector store operations superpower. Includes insert, query, stats, compaction, secure demos, and REST API.
superpower:
  command: "execute"
  parameters:
    - name: "action"
      type: "string"
      enum: ["insert", "query", "stats", "compact", "benchmark", "secure", "cluster", "api"]
      description: "WDBX action to perform"
    - name: "path"
      type: "string"
      description: "Database path"
    - name: "query"
      type: "string"
      description: "Query text for semantic search"
    - name: "keep"
      type: "integer"
      description: "Segments to keep during compaction"
---

# WDBX Superpower Plugin

Core WDBX capabilities for OpenCode within the ABI framework.

## Capabilities

- WDBX subsystem integration
- Plugin framework registration
- Runtime lifecycle management
- Configuration and settings management
- Status monitoring and reporting

## Integration Points

- ABI's WDBX subsystem integration
- OpenCode plugin framework integration
- Runtime lifecycle management
- Configuration and settings management

## Actions

### insert
Insert vectors/blocks into store.

### query
Semantic/persona-scoped retrieval.

### stats
Show store statistics.

### compact
Retain newest segments.

### benchmark / secure / cluster / api
As per WDBX superpower.

## Implementation

Maps to:
- `../wdbx/crates/abi-wdbx/src/store.rs`
- `../wdbx/crates/abi-wdbx/src/segments.rs`
- `../wdbx/crates/abi-wdbx/src/rest.rs`
- `../wdbx/crates/abi-wdbx/src/cluster_rpc.rs`

## Build and runtime boundary

`abi-wdbx` is a normal Rust workspace crate; there is no `feat-wdbx` switch.
Use the real `abi wdbx` subcommands shown by `abi wdbx help`, with scratch
stores for tests.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall