diff --git a/.claude/skills/release/SKILL.md b/.claude/skills/release/SKILL.md
index e4c467b..941cbc8 100644
--- a/.claude/skills/release/SKILL.md
+++ b/.claude/skills/release/SKILL.md
@@ -16,7 +16,7 @@ description: >
 
 # Releasing pipelex-sdk-python
 
-The procedure is the workspace release play, [`docs/releasing.md`](../../../../docs/releasing.md) at the workspace root — read it first, then run it with what follows. The repo key is `pipelex-sdk-python`, the base is `dev`, and the pull request targets `main`: `guard-branches.yml`'s `gate-main` refuses any head branch but `release/vX.Y.Z` into `main`, so there is no other way in. The release worktree is `_pipelex-sdk-python--release`, made with `wt add pipelex-sdk-python release --branch release/vX.Y.Z`. The repo declares neither `.worktree.toml` nor `.worktreeinclude`, so `wt` resolves the base from `origin/dev` and provisions with the Makefile's `install` target, which is what creates the `.venv` every gate below runs out of. The distribution is `pipelex-sdk` and the import package is `pipelex_sdk`; the version number is the distribution's.
+The procedure is the workspace release play, [`docs/workspace/releasing.md`](../../../../docs/workspace/releasing.md) at the workspace root — read it first, then run it with what follows. The repo key is `pipelex-sdk-python`, the base is `dev`, and the pull request targets `main`: `guard-branches.yml`'s `gate-main` refuses any head branch but `release/vX.Y.Z` into `main`, so there is no other way in. The release worktree is `_pipelex-sdk-python--release`, made with `wt add pipelex-sdk-python release --branch release/vX.Y.Z`. The repo declares neither `.worktree.toml` nor `.worktreeinclude`, so `wt` resolves the base from `origin/dev` and provisions with the Makefile's `install` target, which is what creates the `.venv` every gate below runs out of. The distribution is `pipelex-sdk` and the import package is `pipelex_sdk`; the version number is the distribution's.
 
 ## What ships