docs: point agent skills at code.pythinker.com and the canonical repo

Name the published docs site and Pythoughts-labs/pythinker-code
explicitly in gen-docs and sync-changelog instead of generic
placeholders.

Author: elkaix

.agents/skills/gen-docs/SKILL.md

@@ -7,7 +7,7 @@ description: Update Pythinker Code CLI user documentation after meaningful code
 
 ## Overview
 
-This repository maintains English user documentation under `docs/`.
+This repository (`github.com/Pythoughts-labs/pythinker-code`) maintains English user documentation under `docs/`, published at **https://code.pythinker.com**.
 
 Use this skill to update the corresponding documentation whenever the codebase has changes that affect product behavior or user experience.
 
@@ -17,7 +17,7 @@ For a **full pre-release audit** of all pages (detecting hallucinations and cove
 
 This skill depends on the following being in place. If any are missing, stop and report to the user before continuing:
 
-- `docs/` directory with documentation pages and `docs/.vitepress/config.ts` set up (VitePress site).
+- `docs/` directory with documentation pages and `docs/.vitepress/config.ts` set up (VitePress site, deployed to code.pythinker.com).
 - `docs/AGENTS.md` style guide — defines terminology, typography, and writing style.
 
 ## Workflow

.agents/skills/sync-changelog/SKILL.md

@@ -15,7 +15,7 @@ apps/pythinker-code/CHANGELOG.md
 
 This file is the **only upstream source** for the documentation-site changelog. Internal package changelogs such as `packages/*/CHANGELOG.md` do not go into the documentation site.
 
-After the release flow finishes (Release PR merged → `Version Packages` completed → npm publish succeeded), maintainers manually run this skill to copy the new CLI changelog entries into the docs site.
+After the release flow finishes (Release PR merged → `Version Packages` completed → npm publish succeeded), maintainers manually run this skill to copy the new CLI changelog entries into the docs site (published at https://code.pythinker.com).
 
 ## When To Use
 
@@ -38,7 +38,7 @@ Core rule: the English docs changelog is the source of truth for user-facing rel
 
 Before editing, confirm:
 
-- The released version exists on npm (`npm view @pythoughts/pythinker-code versions --json`) or has a matching GitHub Release tag.
+- The released version exists on npm (`npm view @pythoughts/pythinker-code versions --json`) or has a matching GitHub Release tag on `Pythoughts-labs/pythinker-code`.
 - The top of `apps/pythinker-code/CHANGELOG.md` is that new version.
 - The current branch is clean, or you are on a dedicated docs-sync branch.
 
@@ -66,7 +66,7 @@ Use upstream order: newest version first.
 Upstream entries look like this:
 
 ```markdown
-- [#317](https://github.com/...) [`2f51db4`](https://github.com/...) - Clean up lint warnings ...
+- [#317](https://github.com/Pythoughts-labs/pythinker-code/pull/317) [`2f51db4`](https://github.com/Pythoughts-labs/pythinker-code/commit/2f51db4) - Clean up lint warnings ...
 ```
 
 Keep: