VisExtension Center

Skills

A skill is a folder with a SKILL.md file that tells Vis how to do a specific kind of task. Vis lists every skill it finds in the system prompt and reads the full instructions only when a task needs them.

Skills written for Claude Code, pi, opencode or the agent skills standard work without changes.

Write a skill

.vis/skills/release-checklist/
├── SKILL.md
└── scripts/
    └── verify.sh

---
name: release-checklist
description: Use when the user requests a release. Verifies, tags and publishes.
---

# Release checklist

1. Run `scripts/verify.sh`.
2. Update the version in `VERSION`.
3. Tag and push.

Vis reads name and description from the frontmatter. State when the skill should be used in description; the model uses it to select a skill. If name is missing, Vis uses the folder name.

Bundled files (scripts, templates, references) are read with ordinary file tools when the skill is used.

Where Vis looks

Vis searches these sources in order. The first skill with a given name is used; later matches are ignored.

Location Scope
.vis/skills Project
.claude/skills Project
.pi/skills Project
.agents/skills Project
.opencode/skills, then .opencode/skill Project
Nested projects using those same locations When the session is at the Git root
~/.claude/skills User
~/.claude/plugins/cache/**/skills Installed Claude Code plugins
~/.pi/agent/skills User
~/.agents/skills User
~/.config/opencode/skills, then ~/.config/opencode/skill User
Registered extension packages Qualified package/skill names

Project locations are also searched in parent directories up to the Git root. Local file changes are loaded without restarting Vis. Package skills come from the admitted snapshot: /reload updates them with their extension, and a failed reload keeps the last working version. An ordinary skill with the exact qualified name overrides a package skill without affecting its tools.

See bundled skills to ship a procedure and its resources with an extension. Installing a package or reading doc(name) does not execute its skill or grant permission for actions described by it.

Use a skill explicitly

The model chooses skills on its own. To name one yourself, type /skill:<name> followed by an optional task:

/skill:release-checklist
/skill:release-checklist for the 2.1 branch

Skills are hidden from the initial / list but appear when you search by name.

See also

BlocketherEdit on GitHub ↗