diff --git a/skills/using-vds-ops/SKILL.md b/skills/using-vds-ops/SKILL.md
new file mode 100644
index 0000000..63fb9a9
--- /dev/null
+++ b/skills/using-vds-ops/SKILL.md
@@ -0,0 +1,21 @@
+---
+name: using-vds-ops
+version: 0.1.0
+description: "Use when diagnosing docker containers on the Rusonyx VDS — the `vds-ops` HTTP MCP server (https://opsmcp.vds.kzntsv.site/mcp) exposes 4 read-only tools — `ops.docker.ps`, `ops.docker.logs`, `ops.docker.inspect`, `ops.docker.stats` — all routed through tecnativa `vds-docker-proxy-ro` with `POST=0` (write-ops return 403). Triggers on VDS container names (`traefik`, `portainer`, `gitea`, `verdaccio`, `registry`, `joxit-ui`, `ntfy`, `postgres`, `mariadb`, `mongo`, `redis`, `vds-ops-mcp`, `vds-docker-proxy-ro`), on VDS-domain words («на VDS», «VDS», «vds.kzntsv.site», «vds-ops», «opsmcp.vds», «Rusonyx», «облачный VDS»), or on incident phrases («падает», «restart-loop», «не стартует», «unhealthy», «посмотри логи», «git.kzntsv не открывается», «verdaccio лежит», «registry медленно», «ntfy не приходит») when VDS-context. Read-only by design — no per-session grant needed. Disambiguation: `traefik` exists on both VDS and NAS — ask «на VDS или на NAS?» before tool call when ambiguous. Skip for non-VDS hosts (NAS `modulair-*` → using-synology-ops), write-ops, mentions without incident signal."
+---
+
+# using-vds-ops
+
+Read-only diagnostic access to docker containers on the Rusonyx VDS via the `vds-ops` HTTP MCP server. Mirror of `using-synology-ops` for the VDS host. Skeleton — body to be filled in a follow-up pass.
+
+## When to use
+
+## Inputs
+
+## Steps
+
+## Failure modes
+
+## Side effects
+
+## What NOT to do