Name: provisioning-library-generation
Rating: 67.2 (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

80%

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

78%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 regeneration workflow is highly actionable, well-sequenced, and token-efficient, with strong worked examples and a useful Key Files table. The main gap is progressive disclosure: the onboarding workflow is handed off to ONBOARDING.md, which is not present in the bundle.

Suggestions

Add the missing ONBOARDING.md reference file (or inline the onboarding workflow) so the 'Read and follow ONBOARDING.md' instruction resolves to actual content.

Add an explicit build/compile verification step between generation (Step 3) and commit (Step 7), e.g. 'dotnet build' on the target library, to strengthen the validation feedback loop.

Trim a few framing prose lines (e.g., the opening 'This skill covers two related generation workflows' restatement) to push conciseness toward the top anchor.

Dimension	Reasoning	Score
Conciseness	The body is dense with actionable specifics and assumes Claude's competence (no explanations of dotnet/git/C# basics), with only minor prose that could be trimmed, fitting the 'efficient with minor over-explanation' anchor.	4 / 5
Actionability	Copy-paste-ready shell, C#, XML, and YAML blocks plus two fully worked examples (PostgreSQL versions, NetworkSecurityPerimeter) cover the common cases, matching the fully-executable anchor.	5 / 5
Workflow Clarity	Steps 1-7 are clearly sequenced with a verification checkpoint (git status), a generator-error feedback loop (capture, report, stop), and pre-commit checks; validation is present so the destructive/batch cap does not apply, but the validate->fix->retry loop is less crisp than the top anchor.	4 / 5
Progressive Disclosure	Sections are clearly organized and the onboarding branch is delegated to ONBOARDING.md with a clear one-level signal, but that referenced file is absent from the bundle (no references/scripts/assets exist), so navigation breaks for one of the two workflows.	3 / 5
	Total	16 / 20 Passed

Description

82%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 well-formed: it states a clear niche, gives explicit 'what' and 'when' guidance with concrete triggers, and uses third-person voice throughout. Its only weakness is that the named actions are somewhat high-level rather than enumerating granular operations.

Dimension	Reasoning	Score
Specificity	Names the domain (Azure.Provisioning.*) and two concrete actions ('Generate new...libraries OR regenerate existing ones'), but the actions are high-level rather than a comprehensive list of specific operations, matching the anchor for 1-2 concrete actions.	3 / 5
Completeness	Explicitly answers both what (generate/regenerate Azure.Provisioning.* libraries) and when (introducing a new library, adding resource types, enum values, or API versions) with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger phrases ('introducing a brand-new provisioning library, adding new resource types, enum values, or API versions') align well with what an SDK contributor would say, with only minor synonym/extension coverage missing.	4 / 5
Distinctiveness Conflict Risk	'Azure.Provisioning.*' is a clear niche with distinctive, domain-specific triggers, giving minimal overlap risk with other skills.	5 / 5
	Total	17 / 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-sdk-for-net
Path: .github/skills/provisioning-library-generation/SKILL.md
Commit: bc946a1

Reviewed: 3 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.