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%Weight 40%Scale 1-5

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

A well-structured, actionable skill body with strong workflow sequencing, validation checkpoints, and clean progressive disclosure into real reference files. The main weakness is redundancy between the Triggers/Examples/Troubleshooting sections and the frontmatter description, which costs tokens without adding guidance.

Suggestions

Remove or shrink the Triggers section — it duplicates the frontmatter WHEN/USE FOR/DO NOT USE FOR content verbatim and adds no new information.

Trim the 13-item Examples list to 4-5 representative cases; the WHEN triggers already cover the same surface area.

Collapse the Troubleshooting bullets that restate Guardrails (manual editing, run_generate_sdk for all-languages) and keep only genuinely new diagnostics.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and action-oriented, but the Triggers section fully restates the frontmatter WHEN/USE FOR/DO NOT USE FOR content and the 13-item Examples list plus parts of Troubleshooting restate Guardrails rules — minor padding that could be trimmed.	4 / 5
Actionability	The MCP Tools table and numbered Steps name exact tool identifiers and order them concretely (e.g. 'Run azure-sdk-mcp:azsdk_package_generate_code with the config file path'), but exact argument syntax/flags are not given, leaving minor execution gaps.	4 / 5
Workflow Clarity	An 11-step sequence includes explicit validation (run_check + run_tests at step 9), commit checkpoints (steps 8 and 11), and a build-fail feedback loop into the customization step (6→7), satisfying the validation-checkpoint requirement for this batch generation workflow.	5 / 5
Progressive Disclosure	Clear sectioned overview (Triggers, Rules, MCP Tools, Steps, Guardrails, Examples, Troubleshooting) with well-signaled, one-level-deep references to the three real files in references/ (sdk-repos.md, detailed-workflow.md, customization-workflow.md), linked inline and again at the bottom for easy navigation.	5 / 5
	Total	18 / 20 Passed

Description

100%Weight 40%Scale 1-5

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

A high-quality description: concrete capabilities, comprehensive natural trigger phrases, explicit what/when guidance, and clear boundary disambiguation against related skills. No meaningful gaps to address.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Generate, build, and test Azure SDKs locally from TypeSpec with automatic customization' plus changelog/metadata/version updates, renames, and customization fixes — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers both 'what' (Generate, build, and test Azure SDKs locally from TypeSpec with automatic customization) and 'when' via concrete WHEN trigger phrases, plus a DO NOT USE FOR boundary.	5 / 5
Trigger Term Quality	The WHEN clause supplies comprehensive natural phrases users would actually say ('generate SDK locally', 'build SDK', 'fix SDK build errors', 'rename SDK client', 'hide operation from SDK') with strong synonym coverage.	5 / 5
Distinctiveness Conflict Risk	The niche is tightly scoped to local Azure SDK generation from TypeSpec, and the DO NOT USE FOR clause (publishing, CI pipeline config, API design review) plus INVOKES tool list make conflict with sibling skills minimal.	5 / 5
	Total	20 / 20 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-rest-api-specs
Path: .github/skills/azsdk-common-generate-sdk-locally/SKILL.md
Commit: 120cdc9

Reviewed: 1 day 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.