Rename shared skills with azsdk-common- prefix for sync pipeline

Rename 5 shared skills to use the azsdk-common- prefix so the
sync-.github.yml pipeline can pattern-match and distribute them to all
subscribed Azure SDK language repos.

Renames:
  generate-sdk-locally → azsdk-common-generate-sdk-locally
  apiview-feedback-resolution → azsdk-common-apiview-feedback-resolution
  pipeline-troubleshooting → azsdk-common-pipeline-troubleshooting
  prepare-release-plan → azsdk-common-prepare-release-plan
  sdk-release → azsdk-common-sdk-release

Updated:
- SKILL.md name: fields in all 5 skills
- All eval.yaml and trigger_tests.yaml skill/name references
- .github/skills/README.md links and naming convention docs
- sensei SKILL.md example reference
- 8 instruction files in eng/common/instructions/azsdk-tools/ with
  Related Skill cross-references pointing to new skill paths
- copilot/sdk-release.instructions.md with skill cross-reference

Relates to #15049

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: 2 people

eng/common/instructions/azsdk-tools/check-package-readiness.instructions.md

@@ -1,6 +1,10 @@
 ---
 description: 'This prompt is designed to check the release readiness of a SDK package.'
+related_skill: "azsdk-common-sdk-release"
 ---
+
+> **Related Skill:** See `.github/skills/azsdk-common-sdk-release/SKILL.md` for the full release workflow including readiness checks and pipeline triggering.
+
 ## Goal
 Check the release readiness of an SDK package by collecting the required information from the user and executing the readiness check.
 

eng/common/instructions/azsdk-tools/check-package-validation.instructions.md

@@ -1,6 +1,10 @@
 ---
 description: 'Run the package validation checks for the SDK package.'
+related_skill: "azsdk-common-generate-sdk-locally"
 ---
+
+> **Related Skill:** See `.github/skills/azsdk-common-generate-sdk-locally/SKILL.md` — package validation is Step 5 of the generate-build-test workflow.
+
 ## Goal
 Run the validation checks for the SDK package by collecting the required information from the user and executing the `azsdk_package_run_check` tool.
 

eng/common/instructions/azsdk-tools/create-release-plan.instructions.md

@@ -1,3 +1,5 @@
+> **Related Skill:** See `.github/skills/azsdk-common-prepare-release-plan/SKILL.md` for the high-level release plan workflow and MCP tool reference. This instruction file provides the detailed step-by-step interaction flow.
+
 > **CRITICAL INSTRUCTIONS FOR LLM**
 > 1. Backend processes may use Azure DevOps work item data as needed. However, do **not** mention or display the work item link/URL, or any reference to Azure DevOps work item resources directly in conversation with the user.
 > 2. All manual updates to an existing release plan must be made through the [Release Planner Tool](https://aka.ms/sdk-release-planner) to ensure proper tracking and validation.

eng/common/instructions/azsdk-tools/local-sdk-workflow.instructions.md

@@ -1,7 +1,10 @@
 ---
 description: "Guide the user to generate and build SDKs locally for a TypeSpec based API spec"
+related_skill: "azsdk-common-generate-sdk-locally"
 ---
 
+> **Related Skill:** See `.github/skills/azsdk-common-generate-sdk-locally/SKILL.md` for the high-level workflow, MCP tool reference, and customization guidance. This instruction file provides the detailed step-by-step interaction flow.
+
 # Goal
 
 Help the user generate and build SDKs locally from TypeSpec API specifications using the `azure-sdk-mcp` tools.

eng/common/instructions/azsdk-tools/sdk-details-in-release-plan.instructions.md

@@ -1,6 +1,10 @@
 ---
 description: 'Identify languages configured in the TypeSpec project and add it to release plan'
+related_skill: "azsdk-common-prepare-release-plan"
 ---
+
+> **Related Skill:** See `.github/skills/azsdk-common-prepare-release-plan/SKILL.md` — SDK details update is Step 5 of the release plan workflow. See also `references/release-plan-details.md` for additional context.
+
 # Step 1: Find the list of languages and package names
 **Goal**: Identify languages configured in the TypeSpec project and generate the json object with language and package name.
 1. Identify the language emitter configuration in the `tspconfig.yaml` file in the TypeSpec project root.

eng/common/instructions/azsdk-tools/typespec-to-sdk.instructions.md

@@ -1,6 +1,16 @@
 ---
 description: 'Generate SDKs from TypeSpec'
+related_skills:
+  - "azsdk-common-generate-sdk-locally"
+  - "azsdk-common-prepare-release-plan"
+  - "azsdk-common-sdk-release"
 ---
+
+> **Related Skills:** This orchestration workflow references multiple shared skills:
+> - `.github/skills/azsdk-common-generate-sdk-locally/SKILL.md` — SDK generation, build, and test
+> - `.github/skills/azsdk-common-prepare-release-plan/SKILL.md` — Release plan creation and management
+> - `.github/skills/azsdk-common-sdk-release/SKILL.md` — Release readiness checks and publishing
+
 Your goal is to guide the user through the process of generating SDKs from TypeSpec projects. **Before starting**, show all the high level steps to the user and ask: 
 
 > "Would you like to begin the SDK generation process now? (yes/no)"

eng/common/instructions/azsdk-tools/verify-namespace-approval.instructions.md

@@ -1,6 +1,10 @@
 ---
 description: 'Verify SDK namespace approval for management plane'
+related_skill: "azsdk-common-prepare-release-plan"
 ---
+
+> **Related Skill:** See `.github/skills/azsdk-common-prepare-release-plan/SKILL.md` — namespace approval is Step 6 of the release plan workflow (management plane only).
+
 This task is required only for management plane API spec and only if a release plan exists for the API spec pull request.
 
 ## Step 1: Check if release plan exists and it is for management plane SDK

eng/common/instructions/azsdk-tools/verify-setup.instructions.md

@@ -1,7 +1,10 @@
 ---
 description: 'Verify Setup'
+related_skill: "azsdk-common-generate-sdk-locally"
 ---
 
+> **Related Skill:** See `.github/skills/azsdk-common-generate-sdk-locally/SKILL.md` — environment verification is Step 1 of the generate-build-test workflow.
+
 ## Goal
 This tool verifies the developer's environment for SDK development and release tasks. It returns what requirements are missing for the specified languages and repo, or success if all requirements are satisfied. It can help install supported requirements.
 

eng/common/instructions/copilot/sdk-release.instructions.md

@@ -1,5 +1,7 @@
 # SDK release
 
+> **Related Skill:** See `.github/skills/azsdk-common-sdk-release/SKILL.md` for the complete release workflow with step-by-step guidance and troubleshooting.
+
 There are two tools to help with SDK releases:
 - Check SDK release readiness
 - Release SDK