docs(skills): document auto-created GitHub Release after pipeline succeeds (#1403)

The official build pipeline now creates a published GitHub Release automatically
on successful run (PR #1399's tooling change). Update both skills so contributors
know to look for the release at /releases/tag/v<version> after their PR ships:

- create-pr SKILL.md: Step 4 prompt now mentions the auto-release URL and what to
  do if it doesn't appear (token scope / SSO check).
- pac-cli-update SKILL.md: Step 9 final summary now includes the same guidance.

Author: jbujula

.claude/skills/create-pr/SKILL.md

@@ -162,4 +162,14 @@ When queuing, set these pipeline variables:
   - AZ_DevOps_Read_PAT      PAT to read from the AzDO DPX-Tools-Upstream feed
   - isEsrpEnabled           true
   - PUBLISH_TO_MARKETPLACE  true
+
+When the pipeline succeeds, the build automatically:
+  - Pushes a v<version> tag (e.g. v2.0.147) to the repo
+  - Signs and publishes the VSIXs to the VS Marketplace
+  - Creates a published GitHub Release with all 4 signed VSIXs attached, marked Latest
+
+Verify the release at:
+  https://github.com/microsoft/powerplatform-build-tools/releases/tag/v<version>
+
+If no GitHub Release shows up after a successful build, inspect the "Create GitHub release with VSIX assets" task in the ADO build logs — most likely cause is the GITHUB_TOKEN pipeline variable being missing, expired, or lacking `repo` scope / SSO authorization for `microsoft`.
 ```

.claude/skills/pac-cli-update/SKILL.md

@@ -204,6 +204,29 @@ Print:
 4. **Release PR:** URL
 5. **Restore verified:** yes / no (did `gulp restore` download the new pac CLI successfully?)
 
+Then tell the user what to do after both PRs merge:
+
+```
+Once both PRs merge, queue the official build to sign, publish to Marketplace, and create the GitHub Release:
+  https://dev.azure.com/dynamicscrm/OneCRM/_build?definitionId=21491
+
+Pipeline variables to set when queuing:
+  - GITHUB_TOKEN            GitHub PAT (repo scope, SSO enabled for 'microsoft' org)
+  - AZ_DevOps_Read_PAT      PAT to read from the AzDO DPX-Tools-Upstream feed
+  - isEsrpEnabled           true
+  - PUBLISH_TO_MARKETPLACE  true
+
+On success, a published GitHub Release will appear automatically at:
+  https://github.com/microsoft/powerplatform-build-tools/releases/tag/v<new-extension-version>
+
+That release will include:
+  - All 4 signed VSIXs (LIVE, BETA, DEV, EXPERIMENTAL) as assets
+  - Release notes extracted from `extension/overview.md`'s `{{NextReleaseVersion}}:` block
+  - Latest tag
+
+If the release does not appear, check the "Create GitHub release with VSIX assets" task in the build log — usually GITHUB_TOKEN scope or SSO authorization is the issue.
+```
+
 ---
 
 ## Hard rules