Name: azsdk-common-generate-sdk-locally
Rating: 68.8 (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

85%

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

70%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.

The body is well-structured with a clear, validated workflow and concrete tool guidance, but it is dragged down by redundancy with the frontmatter description and by referenced bundle files that are missing from the repository.

Suggestions

Remove or condense the Triggers section — it restates the frontmatter description's WHEN/USE FOR/DO NOT USE FOR verbatim — and state the "Without MCP, use npx tsp-client" fallback once instead of three times.

Add the missing references/sdk-repos.md, references/detailed-workflow.md, and references/customization-workflow.md files (or remove the links), since the body relies on them for repo details, config-file paths, commit checkpoints, and the customization workflow.

Show the exact invocation shape (key arguments) for the MCP tools in the Steps or MCP Tools table so the guidance is copy-paste ready rather than only naming the tool.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and action-oriented, but the Triggers section duplicates the frontmatter description's WHEN/USE FOR/DO NOT USE FOR verbatim, and "Without MCP, use npx tsp-client" is repeated three times (Rules, MCP Tools, Troubleshooting).	3 / 5
Actionability	Provides concrete MCP tool names with purposes and a numbered step sequence referencing specific tool calls (e.g. "Run `azure-sdk-mcp:azsdk_package_generate_code` with the config file path"), with only minor gaps in exact invocation syntax/arguments.	4 / 5
Workflow Clarity	An 11-step sequence with explicit validation checkpoints (verify setup at step 4, run check + tests at step 9), a build-fail feedback loop (step 6 → customize at step 7), and commit checkpoints at steps 8 and 11.	5 / 5
Progressive Disclosure	References are clearly signaled and one level deep (references/sdk-repos.md, detailed-workflow.md, customization-workflow.md), but the referenced files do not exist in the bundle — navigation is broken, so the structure does not deliver on its intent.	3 / 5
	Total	15 / 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.

The description is exemplary: concrete actions, comprehensive natural trigger phrases, explicit what/when/when-not guidance, and a distinct niche. It earns the top anchor on every dimension.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — "Generate, build, and test Azure SDKs locally from TypeSpec with automatic customization" — giving comprehensive coverage of what the skill does.	5 / 5
Completeness	Explicitly answers what (generate/build/test/customize locally from TypeSpec), when (concrete WHEN trigger phrases), and when-not (DO NOT USE FOR), matching the top anchor.	5 / 5
Trigger Term Quality	The WHEN clause enumerates many natural phrases a user would say ("generate SDK locally", "build SDK", "run SDK tests", "fix SDK build errors", "rename SDK client", etc.) with strong synonym coverage.	5 / 5
Distinctiveness Conflict Risk	A clear niche (local single-language SDK generation from TypeSpec) plus a DO NOT USE FOR clause distinguishing it from publishing, CI config, and API review minimizes conflict risk.	5 / 5
	Total	20 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 8 missing	Warning
referenced_paths_exist	Referenced path issues: 8 missing	Warning

	Total	14 / 16 Passed

Repository: Azure/azure-rest-api-specs
Path: .github/skills/azsdk-common-generate-sdk-locally/SKILL.md
Commit: c20bf55

Reviewed: 15 hours 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.