- Shell 100%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
Teach the skill to call deployment_catalog before opening a named widget and never guess a collection. Document system collections, the auth collection, users and admins surfaces, and the difference between auth settings, users, and API rules. Add task recipes for adding users and showing collections, and note the optional counts and field metadata. |
||
| .claude-plugin | ||
| .zcode-plugin | ||
| commands | ||
| scripts | ||
| skills | ||
| .gitignore | ||
| .mcp.json | ||
| LICENSE | ||
| README.md | ||
vski
A cross-agent plugin that gives coding agents semantic access to the VSKI platform: the wiki and the canonical example repos, via the public vski-docs MCP server.
One repo, three surfaces:
| Host | Mechanism |
|---|---|
| Claude Code | native plugin (.claude-plugin/plugin.json) + marketplace |
| ZCode | native plugin (identical .zcode-plugin/plugin.json; ZCode also reads the Claude layout) |
| Harness (opencode) | plugin manager — opencode plugin install from a git URL, archive, local path, or local registry |
| Codex | installer script — MCP server in ~/.codex/config.toml + skills in ~/.agents/skills |
What you get
MCP server vski-docs (remote, streamable HTTP, no auth needed):
| Tool | Purpose |
|---|---|
search_docs |
Semantic search over the VSKI wiki. Results are canonical links (docs.vski.ai page + raw markdown on vski.sh) with section anchors and knowledge-graph related pages. |
list_docs |
Every indexed wiki page and example repo, as canonical links. |
search_code |
Semantic search over the canonical example repos. kind: "comment" searches the usage-note comments — usually the fastest path to the right example. |
get_example |
Full source of one example file with its canonical vski.sh URL. |
index_status |
Latest indexer runs (the index refreshes on a 6-hour cron). |
Skills (auto-triggered when relevant):
docs— searching/reading the wiki; the links-only policy (fetchmarkdown_urlto read a page)examples— finding canonical example code; the comment-search trickapp-dev— end-to-end workflow for building apps on VSKI (schema, plugins, pipelines, IaC)dashboard— opening VSKI dashboard surfaces through/w/...and the authenticated/connecthandoff, including signing the integrated browser in and the SQL human-in-the-loop rule
Commands: /vski:docs [query], /vski:example [what to build], /vski:status.
Install
Claude Code
claude plugin marketplace add https://vski.sh/x/vski_claude_plugin
claude plugin install vski@vski
Or in a session: /plugin marketplace add vski https://vski.sh/x/vski_claude_plugin, then install vski from the /plugin browser. Verify with /mcp — the vski-docs server should be connected.
ZCode
/plugin marketplace add https://vski.sh/x/vski_claude_plugin
then install vski from the plugin browser. Skills appear as vski:docs,
vski:examples, vski:app-dev, vski:dashboard; MCP tools as mcp__vski_vski-docs__*.
Harness (opencode fork)
Install straight from the git remote, or by name from your local registry:
opencode plugin install ssh://git@vski.sh/x/harness_plugin.git#main
# or: opencode plugin install /path/to/harness_plugin (local checkout)
# or: add the repo to ~/.vskicode/plugins/registry.json, then:
opencode plugin install vski
Skills appear as vski/docs, vski/examples, vski/app-dev, vski/dashboard; commands as
/vski:docs etc.; the MCP server registers as vski.vski-docs. Updates:
opencode plugin update vski. The harness's opencode plugin validate .
checks the layout, and opencode plugin import claude migrates a Claude Code
installation's plugins.
Codex
Codex has no plugin system, but supports remote MCP servers and the same
SKILL.md skill format. The installer wires both up:
git clone https://vski.sh/x/vski_claude_plugin
cd vski_claude_plugin
./scripts/install-codex.sh
It registers [mcp_servers.vski-docs] in ~/.codex/config.toml (via
codex mcp add when available, TOML append otherwise) and copies the skills
to ~/.agents/skills/vski-*. --uninstall removes exactly what it added.
Restart Codex afterwards.
Repo layout
.claude-plugin/plugin.json Claude Code manifest
.claude-plugin/marketplace.json single-plugin marketplace ("source": "./")
.zcode-plugin/plugin.json byte-identical copy for ZCode (its preferred location)
.zcode-plugin/marketplace.json copy for ZCode marketplace loading
.mcp.json vski-docs MCP server declaration (shared by both hosts)
skills/<name>/SKILL.md host-neutral skills (Claude, ZCode, and Codex formats agree)
commands/*.md slash commands
scripts/install-codex.sh Codex installer (MCP + skills)
The manifests omit component-path fields on purpose: both hosts auto-scan
the default skills/ and commands/ directories, and Claude requires
./-prefixed paths when declared while ZCode manifests use bare paths —
omitting them keeps the two manifests byte-identical.
Development
- The MCP server side lives in its own repo (vski_docs_mcp);
this plugin only points at the deployed
https://mcp.vski.ai/mcp. - Skills reference MCP tools by bare name (
search_docs, notmcp__…) so the same text works on every host. Keep it that way when editing. - Validate after changes (if the Claude CLI is available):
claude plugin validate . - Version bumps touch three files: both
plugin.jsoncopies and the plugin entry in bothmarketplace.jsoncopies (keep each pair byte-identical).
License
MIT — see LICENSE.