Name: azsdk-common-generate-sdk-locally
Rating: 75.2 (1 reviews)
Author: Azure

azsdk-common-generate-sdk-locally

Generate, build, and test Azure SDKs locally from TypeSpec with automatic customization. WHEN: "generate SDK locally", "build SDK", "run SDK tests", "run CI checks", "validate package", "run checks", "update changelog", "fix SDK build errors", "fix breaking changes", "resolve SDK generation errors", "customize TypeSpec", "rename SDK client", "rename SDK model", "hide operation from SDK", "fix analyzer errors", "resolve customization drift", "create subclient", "update metadata", "update version". DO NOT USE FOR: publishing to package registries, CI pipeline configuration, API design review. INVOKES: azsdk_verify_setup, azsdk_package_generate_code, azsdk_package_build_code, azsdk_package_run_check, azsdk_package_run_tests, azsdk_customized_code_update, azsdk_package_update_changelog_content, azsdk_package_update_metadata, azsdk_package_update_version.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured, actionable, and cleanly splits detail into one-level references with a clear validated workflow. Its main weakness is redundancy between the Triggers/intro/Troubleshooting sections and the frontmatter and Guardrails.

Suggestions

Remove or condense the Triggers section since the frontmatter description already carries the WHEN/USE FOR/DO NOT USE FOR triggers, eliminating duplication.

Trim the opening paragraph that restates the description, keeping only any new framing not already in the frontmatter.

Merge the Troubleshooting section into Guardrails/Steps, since both currently repeat the 'do not manually edit generated code; retry the customization tool' guidance.

Dimension	Reasoning	Score
Conciseness	The Triggers section duplicates the frontmatter WHEN/USE FOR/DO NOT USE FOR content, the intro restates the description, and Troubleshooting repeats the Guardrail about not manually editing generated code, so it could be tightened despite being mostly efficient.	2 / 3
Actionability	Each step names the exact MCP tool to call (e.g. azsdk_package_generate_code), specifies config file paths (tspconfig.yaml, tsp-location.yaml), and cites concrete analyzer codes (AZC0030, AZC0012), giving copy-paste-ready instruction-only guidance.	3 / 3
Workflow Clarity	Eleven numbered steps are clearly sequenced with validation checkpoints (verify setup, run check, run tests), a build-to-customize feedback loop, and explicit commit checkpoints, matching the clear-sequence-with-validation anchor.	3 / 3
Progressive Disclosure	The body is an overview pointing to three real one-level-deep reference files (sdk-repos.md, detailed-workflow.md, customization-workflow.md) with clearly signaled links and a navigation line, splitting content appropriately.	3 / 3
	Total	11 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, trigger-rich, and complete with clear what/when guidance and exclusion boundaries, all in third person. It is a strong, low-conflict description.

Dimension	Reasoning	Score
Specificity	"Generate, build, and test Azure SDKs locally from TypeSpec with automatic customization" lists multiple concrete actions (generate, build, test, customize, rename, hide, update changelog/metadata/version), matching the anchor for listing multiple specific concrete actions.	3 / 3
Completeness	It explicitly states what the skill does and provides explicit WHEN triggers plus a DO NOT USE FOR boundary, clearly answering both what and when.	3 / 3
Trigger Term Quality	The WHEN clause supplies many natural phrases a user would say ("generate SDK locally", "build SDK", "run SDK tests", "fix SDK build errors", "update changelog"), giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	The narrow TypeSpec-to-Azure-SDK local generation niche with distinct triggers and an explicit DO NOT USE FOR list makes it unlikely to fire for the wrong skill.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Azure/azure-sdk-for-net
Path: .github/skills/azsdk-common-generate-sdk-locally/SKILL.md
Commit: 2f47f87

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.