Database dashboard

Kinic Wiki

CLI

Open npm

kinic-vfs-cli is the npm-distributed operator CLI for Kinic Wiki databases and Skill Registry packages. Use this page as the canonical setup and agent workflow reference.

Install

The npm package downloads the matching release binary and verifies its SHA-256 checksum.

npm install -g kinic-vfs-cli

First Check

Confirm the installed binary, then inspect the command index before connecting it to a database.

kinic-vfs-cli --version
kinic-vfs-cli --help

Connect

Pass --database-id for one command, run database link once for a workspace, or set VFS_DATABASE_ID for scripts.

kinic-vfs-cli --database-id <database-id> status --json
kinic-vfs-cli database link <database-id>
VFS_DATABASE_ID=<database-id> kinic-vfs-cli status --json

Agent Read Workflow

Search first, read exact paths next, then request context when link relationships matter. Agents should use --json.

kinic-vfs-cli search-remote "query text" --prefix /Wiki --top-k 10 --json
kinic-vfs-cli read-node --path /Wiki/page.md --json
kinic-vfs-cli read-node-context --path /Wiki/page.md --json

Agent Write Workflow

Read the node first, keep its etag, mutate with --expected-etag, then read again to verify the stored content.

kinic-vfs-cli read-node --path /Wiki/page.md --json
kinic-vfs-cli edit-node --path /Wiki/page.md --old-text before --new-text after --expected-etag <etag> --json
kinic-vfs-cli read-node --path /Wiki/page.md --json

Skill Registry Workflow

Agents and operators should discover a skill, inspect the package, use it, then record run evidence.

kinic-vfs-cli skill find "contract review" --json
kinic-vfs-cli skill inspect legal-review --json
kinic-vfs-cli skill record-run legal-review --task "review contract" --outcome success --notes-file ./notes.md --json

Safety Notes

  • Public reads can run with --identity-mode anonymous when the database grants anonymous reader access.
  • Writes, database grants, archive operations, and private Skill Registry writes require identity mode.
  • Non-Internet Identity credentials require the explicit --allow-non-ii-identity opt-in.
  • Agents should request JSON output and use etag guards before mutating existing nodes.