diff --git a/AGENTS.md b/AGENTS.md
index 6ef53b0..e904ab1 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -12,5 +12,10 @@ before changing a skill and [CONTRIBUTING.md](CONTRIBUTING.md) before adding one
 - Bump the skill's version in `marketplace.json` when you change it.
 - A new skill needs a cover for whimsical.com/skills: follow
   [docs/covers/README.md](docs/covers/README.md), then render and look at it.
+- A release isn't done when the tag is pushed. whimsical.com/skills only shows a release
+  once the website is redeployed, which doesn't happen on its own. After pushing a tag,
+  tell the person you're working with that the website needs redeploying, and keep
+  reminding them until they say it's done; otherwise the site falls behind the skills.
+  Tag from an up-to-date `main` (`git pull` first), so the release has what was merged.
 - Don't run a skill against real Whimsical boards, Mobbin or customer data unless the
   person you're working with asks you to.
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 837edbb..e7a6a5d 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -58,15 +58,18 @@ If you have Claude Code, also run `claude plugin validate .`.
 
 A release publishes a zip of every skill, for the Claude apps and for agents without a
 skills installer. Links to `releases/latest/download/<name>.zip` always point to the
-newest one. After merging to `main`, tag the date and push the tag:
+newest one. After merging to `main`, update your local `main`, then tag the date and push
+the tag:
 
 ```sh
+git checkout main && git pull
 git tag v2026.11.06 && git push origin v2026.11.06
 ```
 
 Add a suffix for a second release on the same day, like `v2026.11.06.2`. Users of the
 Claude Code marketplace get updates from `main` without a release.
 
-[whimsical.com/skills](https://whimsical.com/skills) shows the skills as they are in the
-latest release, from the website's next deploy. Redeploy the website after a release to
-publish it there.
+Then redeploy the website. [whimsical.com/skills](https://whimsical.com/skills) shows the
+skills as they are in the latest release, but only from the website's next deploy, and a
+release doesn't trigger one. Until it's redeployed, the site still shows the previous
+release.