Name: provisioning-library-generation
Rating: 77.60000000000001 (1 reviews)
Author: Azure

provisioning-library-generation

Generate new Azure.Provisioning.* libraries OR regenerate existing ones. Use when introducing a brand-new provisioning library, adding new resource types, enum values, or API versions.

Quality

96%

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

92%

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

A well-organized, actionable regeneration workflow with strong sequencing and validation, undermined only by a missing referenced file (ONBOARDING.md) that an entire workflow branch depends on.

Suggestions

Ship the referenced ONBOARDING.md (or inline the onboarding workflow) so the Workflow Selection branch resolves instead of pointing to an absent file.

Deduplicate the OrderEnum / CustomizeProperty / backward-compatible-stub guidance that appears in both Step 4 and Troubleshooting to trim redundancy.

Verify placeholder paths like sdk/{service}/Azure.Provisioning.{Service}/ and Specification file names resolve for the services this skill targets.

Dimension	Reasoning	Score
Conciseness	Lean for its scope: domain-specific guidance and executable commands throughout, with no padding about basics Claude already knows (e.g., the NuGet-vs-local-source and cspell.yaml-not-cspell.json callouts earn their place).	3 / 3
Actionability	Copy-paste-ready commands (grep, dotnet run --filter, git status/checkout) and concrete code for CustomizeProperty, OrderEnum, suppression XML, and cspell entries with placeholder patterns.	3 / 3
Workflow Clarity	A clearly sequenced 7-step process with explicit validation checkpoints (verify only target changed via git status; pre-commit checks) and an error-recovery path (capture, report, stop) for generator failures.	3 / 3
Progressive Disclosure	Offloads the onboarding branch to a one-level reference ("Read and follow ONBOARDING.md"), but ONBOARDING.md is not present in the skill directory, so the signaled navigation is broken.	2 / 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.

A strong description: third-person voice, explicit what-and-when, concrete actions, and distinct triggers tied to a clear niche. No fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists two concrete actions ("Generate new Azure.Provisioning.* libraries OR regenerate existing ones") rather than vague language, matching the multiple-concrete-actions anchor.	3 / 3
Completeness	Explicitly states both what (generate/regenerate libraries) and when ("Use when introducing a brand-new provisioning library, adding new resource types, enum values, or API versions").	3 / 3
Trigger Term Quality	Natural trigger terms a developer would say ("provisioning library", "resource types", "enum values", "API versions") are well covered in the Use-when clause.	3 / 3
Distinctiveness Conflict Risk	The Azure.Provisioning.* niche with version/resource/enum triggers is distinct and unlikely to fire for unrelated skills.	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/provisioning-library-generation/SKILL.md
Commit: fef8881

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.