Skip to content
Development
Skill

/vsql-docs

Answer a VillageSQL question from the published documentation at villagesql.com/docs. Use when the user asks how a VillageSQL feature, extension, SQL statement, system variable, or error message works.

From plugin
villagesql
53 skills

Claude Code

$ npx -y skills add villagesql/villagesql-skills --skill vsql-docs --agent claude-code

SKILL.md

vsql-docs.SKILL.md
name: vsql-docs
description: >
  Answer a VillageSQL question from the published documentation at
  villagesql.com/docs. Use when the user asks how a VillageSQL feature,
  extension, SQL statement, system variable, or error message works.
argument-hint: "[question or keyword]"

VillageSQL Docs

Answer from the docs, not from memory. VillageSQL changes every release, and names carried over from MySQL or PostgreSQL are often wrong here.

1. **Pick the docs version.** If a server is already connected, run `SELECT VERSION();`. `8.4…` means `8.4`, `9.7…` means `9.7`, and `-dev` in the version means `dev`; otherwise `stable`. With no server, use `8.4` and `stable`, and say so.

2. **Search.** Use the VillageSQL docs search tool if you have it. Its name contains `search_village_sql_server_for_my_sql`. Server pages live under `en/<8.4|9.7>/<stable|dev>/`; ignore results under a different one. Pages under `en/extensions/`, `en/sdk/`, `en/guides/`, and `en/tutorial/` apply to every version. They describe the latest release, and a note that starts "Changed in <version>-dev" says what differs on a `dev` server.

Without that tool, read <https://villagesql.com/docs/llms.txt> and the guide list it links to, and pick the pages from them.

3. **Read the whole page** before answering. Take the page address, remove any `#anchor`, and add `.md`, for example <https://villagesql.com/docs/en/extensions/install.md>. Do not use the docs file tool for this: its copies of long pages are incomplete.

4. **Answer.** Link each page you used. Copy commands and error messages exactly from the page. Say which docs version you used. If nothing answers the question, say that the search found nothing. Do not say the feature does not exist.

Read more
@villagesql
Ships withvillagesql

Agent skills for working with VillageSQL. Skills run in Claude Code, agy, Codex, Cursor, Amp, Kiro, OpenCode, and OpenClaw.

Stars on GitHub

Momentum

stars in total
5
Star history of villagesql/villagesql-skills on GitHub, a chart by star-history.com

Other skills on villagesql.

vsql-install-server

vsql-install-server

Get a working VillageSQL server on this machine and prove it works — choose an install path (installer, Docker, or source), start…

More skills from other plugins.

brainstorming
Auto-invoked

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…

@obra@obraInstall Skill
ask-matt

ask-matt

Ask which skill or flow fits your situation. A router over the skills in this repo.

skills11d309k
@mattpocock@mattpocockInstall Skill
accessibility
Auto-invoked

accessibility

Design, implement, and audit accessible UI to WCAG 2.2 Level AA across Web, iOS, and Android — semantic ARIA roles and labels,…

ecc12d293k
@affaan-m@affaan-mInstall Skill
compiler-commit

compiler-commit

Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits…

react2d252k
@facebook@facebookInstall Skill

Questions about vsql-docs.

Which coding agents can use vsql-docs?
vsql-docs installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.