Sync .github/skills directory with azure-sdk-tools for PR 16603

[helen229]

Summary

Manually syncs .github/skills content from Azure/azure-sdk-tools#16603 ("Add environment.skills to workflow-scenario eval specs", a clean rebuild of #16380) into this repo, since the automated sync pipeline currently fails with a git am -3 "sha1 information is lacking or useless" error on azsdk-common-generate-sdk-locally/SKILL.md.

That failure is caused by two files in this repo having drifted from azure-sdk-tools main (left over from the #16380/#10150/#10165 sync-then-revert history):

• .github/skills/azsdk-common-generate-sdk-locally/SKILL.md
• .github/skills/azsdk-common-prepare-release-plan/SKILL.md

This PR brings all 10 files touched by azure-sdk-tools#16603 to match that branch's content exactly (verified via direct content diff against azure-sdk-tools main + the PR branch), which both catches up the drifted baseline and applies #16603's environment.skills changes in one step.

Files synced

• azsdk-common-apiview-feedback-resolution/evals/{eval,trigger.eval}.yaml
• azsdk-common-generate-sdk-locally/{SKILL.md,evals/eval.yaml}
• azsdk-common-pipeline-analysis/evals/trigger.eval.yaml
• azsdk-common-pipeline-fixer/evals/trigger.eval.yaml
• azsdk-common-prepare-release-plan/{SKILL.md,evals/trigger.eval.yaml}
• azsdk-common-sdk-release/{SKILL.md,evals/trigger.eval.yaml}

Related: Azure/azure-sdk-tools#16603 (supersedes Azure/azure-sdk-tools#16380).

[azure-pipelines]

Azure Pipelines:
1 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[Copilot]

Pull request overview

Syncs shared skill guidance and evaluations from azure-sdk-tools#16603.

Changes:

• Adds explicit skill environments and cross-skill routing checks.
• Improves evaluation prompts and tool assertions.
• Updates SDK generation and release workflow guidance.

Reviewed changes

Copilot reviewed 10 out of 10 changed files in this pull request and generated 7 comments.

Show a summary per file

File	Description
azsdk-common-apiview-feedback-resolution/evals/eval.yaml	Expands APIView capability evaluations.
azsdk-common-apiview-feedback-resolution/evals/trigger.eval.yaml	Adds explicit routing environments.
azsdk-common-generate-sdk-locally/SKILL.md	Adds pipeline-generation guidance.
azsdk-common-generate-sdk-locally/evals/eval.yaml	Makes local-generation scenarios actionable.
azsdk-common-pipeline-analysis/evals/trigger.eval.yaml	Strengthens analysis routing boundaries.
azsdk-common-pipeline-fixer/evals/trigger.eval.yaml	Strengthens fixer routing boundaries.
azsdk-common-prepare-release-plan/SKILL.md	Corrects release-plan creation guidance.
azsdk-common-prepare-release-plan/evals/trigger.eval.yaml	Expands release-plan routing tests.
azsdk-common-sdk-release/SKILL.md	Adds informational release triggers.
azsdk-common-sdk-release/evals/trigger.eval.yaml	Expands SDK-release routing tests.

Comments suppressed due to low confidence (1)

.github/skills/azsdk-common-generate-sdk-locally/SKILL.md:88

• This repeats the incomplete direct-tool route for all-language generation. azsdk_run_generate_sdk must be invoked once per target language after obtaining release-plan details, so this troubleshooting advice should delegate to the pipeline-generation skill rather than imply one direct call handles the workflow.

- For "generate SDK for all languages", pipeline-based generation, or when no local SDK clone exists, call `azure-sdk-mcp:azsdk_run_generate_sdk` instead of the local generate flow, and never substitute `azure-sdk-mcp:azsdk_get_sdk_pull_request_link` / `azure-sdk-mcp:azsdk_get_pull_request` for generation.