Vibevm Docs

Organization

vibevm

vibevm-docs

Use when the user asks how something in VibeVM works, what a vibe error means, or asks you to do a task the VibeVM manual describes (create a project, install or publish a package, work offline, set up a workspace, write a package of any kind). Find the page, quote the rule by its address, and take the page's prompt as your task.

Overview

Publisher	vibevm
Repository	`vibevm`
Skill name	`vibevm-docs`
Stars	285
Forks	83
Bundled files	Instructions only
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by vibevm on GitHub. Read the source before you install it.

Installation

Install the Vibevm Docs AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/vibevm/vibevm/tree/main/vibevm/vibepacks/org.vibevm.core/vibevm-docs/v1.0.0/vibevm/vibespecs/skills/vibevm-docs
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/vibevm/vibevm/tree/main/vibevm/vibepacks/org.vibevm.core/vibevm-docs/v1.0.0/vibevm/vibespecs/skills/vibevm-docs

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/vibevm/vibevm.git /tmp/vibevm
mkdir -p .claude/skills
cp -r /tmp/vibevm/vibevm/vibepacks/org.vibevm.core/vibevm-docs/v1.0.0/vibevm/vibespecs/skills/vibevm-docs .claude/skills/vibevm-docs

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Vibevm Docs in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Vibevm Docs on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Vibevm Docs is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

The VibeVM manual, for an agent {#root}

@fact:DOCS-SKILL-PURPOSE This skill leads you to the VibeVM manual — the package org.vibevm.core/vibevm-docs — and tells you how to read it with the smallest number of tokens: one page per question, one rule per claim, one prompt per task. The specifications stay the authority; the manual explains them and cites their addresses. @status:doc/work

Where the manual is {#where}

@fact:DOCS-SKILL-LOCAL Locally, when the store holds it: vibe cache list shows org.vibevm.core/vibevm-docs; then vibe explain "spec://org.vibevm.core/vibevm-docs/<page>#<anchor>" prints a page or a block, and vibe doc serve opens the reader on 127.0.0.1 for a person. If the store does not hold it and the user allows the network, vibe cache add org.vibevm.core/vibevm-docs warms it once. @status:doc/work
@fact:DOCS-SKILL-WEB On the web: https://vibevm.org/doc/llms.txt is the index with one line per page; https://vibevm.org/doc/<page>.md is any page as plain Markdown; https://vibevm.org/doc/llms-full.txt is the whole corpus, and llms-small.txt / llms-medium.txt fit smaller budgets. Prefer the index and one page over the full corpus. @status:doc/work

How to use it {#how}

@fact:DOCS-SKILL-ON-ERROR When a vibe command fails, read the rule address the message names (spec://…#…) with vibe explain, then open the page that explains it — the manual's diagnostics page maps messages to pages. Do not guess a fix from the message alone. @status:doc/work
@fact:DOCS-SKILL-ON-QUESTION When the user asks how something works, answer from one page: the first paragraph is the plain answer, the rule blocks carry the exact wording and the address you quote. Prefer a page marked official; the site marks community documentation as such. @status:doc/work
@fact:DOCS-SKILL-ON-TASK When the user asks you to do what a task page describes, take the page's prompt block as your task: substitute the user's coordinates and paths, run what it says, then run the page's assert commands — the task is done only when every assert exits zero. Ask before any step the prompt marks as irreversible (publish, delete). @status:doc/work
@fact:DOCS-SKILL-ON-CHOICE When the user must choose a package or a guide, read the catalogue lines (title, publisher, language, abstract) and prefer official documentation; name the publisher of anything from the community. @status:doc/work

@fact:DOCS-SKILL-NEVER Never restate a normative value from memory when a page quotes it; never load the full corpus when one page answers; never send the user's private package content anywhere — the local reader and the store keep it on the machine. @status:doc/work

Frequently asked questions

What does the Vibevm Docs AI skill do?

Why use Vibevm Docs on TypingMind?

Because you install it once and use it with any model. Vibevm Docs is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Vibevm Docs in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/vibevm/vibevm/tree/main/vibevm/vibepacks/org.vibevm.core/vibevm-docs/v1.0.0/vibevm/vibespecs/skills/vibevm-docs. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Vibevm Docs?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Vibevm Docs?

As many as you like. As long as a model supports skills, you can use Vibevm Docs with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Vibevm Docs AI skill free?

It is published on GitHub by vibevm. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Auto Qa

openclaw

OrganizationPopular

Run OpenClaw-wide autonomous QA and live/stress campaigns across independent subsystem lanes, with verified fixes and a resumable evidence report.

Autoreview

Structured code review when explicitly requested, preferring OpenAI/Codex before Claude.

Channel Message Flows

openclaw

OrganizationPopular

Use when running QA Lab channel message flow evidence.

Claw Score

Audit or refresh OpenClaw maturity scorecard docs from root taxonomy, maturity scores, and QA evidence artifacts without using maintainer discrawl data or committed inventory reports.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

The VibeVM manual, for an agent {#root}

Where the manual is {#where}

How to use it {#how}

Frequently asked questions

Related AI Skills

Set up your own AI workspace now