Vector Setup
Skill Verified ActiveFirst-run setup for ruvector@0.2.25 — installs ONNX/Brain/SONA add-ons, registers the MCP server, and verifies the install via `doctor`
To streamline the first-run setup of ruvector, ensuring all necessary add-ons are installed and verified, thereby saving users time and preventing dependency-related errors.
Features
- Automated installation of ruvector add-ons (ONNX, Brain, SONA)
- Verification of installation via `doctor` and `info` commands
- Registration of the MCP server for ruvector
- Optional `--full` flag for leaner installs
- Clear steps for generating pi identity
Use Cases
- Setting up ruvector for the first time on a new project.
- Ensuring all optional ruvector add-ons are installed correctly.
- Quickly preparing a development environment for ruvector.
Non-Goals
- Installing the native Rust toolchain for ruvector.
- Installing platform-specific native bindings (handled by `@ruvector/core`).
- Installing the native `@ruvector/sona` binding (relies on JS fallback).
- Troubleshooting complex build or runtime errors beyond initial setup.
Installation
First, add the marketplace
/plugin marketplace add ruvnet/ruflo/plugin install ruflo-ruvector@rufloQuality Score
VerifiedTrust Signals
Similar Extensions
Setup
99Detects your Python environment and guides you through installing plugin dependencies. Use on first-time setup or when MCP server fails to start.
Dependency Management
98Manage third-party libraries, runtimes, and SaaS dependencies. Use this skill when setting an update cadence, responding to security advisories, dealing with deprecated dependencies, evaluating new dependencies, auditing what's installed, or unblocking a dependency upgrade. Triggers on dependency, package update, security patch, lockfile, deprecated, breaking change, supply chain, dependency audit, npm audit, dependabot, renovate. Also triggers when a build breaks after an update or when an advisory is published for a used package.
Update Deps
98Audit and update npm/Bun dependencies with supply chain integrity checks — verifies maintainers, publish age, tarball diffs, and provenance before bumping. Defers risky packages to ~/.supply-chain/notes/.
Dependency Check
95Scan project dependencies for known vulnerabilities and CVEs
Cleanup Cycles
100Detect and untangle circular dependencies. Runs madge/skott (TS), pycycle (Py), or compiler-only checks (Go/Rust). Auto-fixes leaf-extractable cycles; reports core cycles for human review. Use when the user asks to find circular imports, fix dependency cycles, or untangle module graph. Example queries — "find circular imports", "fix dependency cycles", "untangle our module graph", "why is madge complaining".
Audit Dependency Versions
100Audit project dependencies for version staleness, security vulnerabilities, and compatibility issues. Covers lock file analysis, upgrade path planning, and breaking change assessment. Use before a release to ensure dependencies are current and secure, during periodic maintenance reviews, after receiving a security advisory, when upgrading to a new language version, before submitting to CRAN or npm, or when inheriting a project to assess its dependency health.