CtrlK
BlogDocsLog inGet started
Tessl Logo

refresh-arm-sdk-release

**WORKFLOW SKILL** — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR creation. FOR SINGLE OPERATIONS: Use git or GitHub tools directly.

68

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

A well-structured, lean workflow document with concrete version-resolution logic and a useful checklist. Its main gaps are abstract git/PR operations and the absence of a verification feedback loop for the batch refresh process.

Suggestions

Add concrete, copy-paste-ready git and gh commands for Steps 1 and 7 (e.g., `git fetch origin main && git checkout -b refresh/<pkg>-<date>`, `gh pr create --title "Prepare release for Azure.ResourceManager.XXX Version 1.x.x"`).

Add an explicit verification checkpoint after Step 7 — e.g., confirm the PR was created, check CI status, and loop back to fix the changelog/csproj if validation fails.

Clarify the exact PR title-version interpolation (where the 1.x.x comes from) so the title can be assembled deterministically rather than left as a template.

DimensionReasoningScore

Conciseness

Lean bullet-style workflow with no explanations of concepts Claude already knows; each section (Prerequisites, Steps 1–7, Checklist) earns its place, and the closing checklist serves as a quick reference rather than padding.

3 / 3

Actionability

Concrete file paths (eng/centralpackagemanagement/Directory.Packages.props, src/Azure.ResourceManager.XXX.csproj, metadata.json) and detailed version-resolution logic are actionable, but the git/PR steps ('Commit with a refresh-focused message', 'Push branch to origin', 'Create PR') are described rather than given as copy-paste commands.

2 / 3

Workflow Clarity

Steps are clearly numbered and the Step 2 eligibility check is a validation checkpoint, but this batch operation across packages lacks an explicit verify→fix→retry feedback loop, capping workflow clarity at 2 per the batch-operations guideline.

2 / 3

Progressive Disclosure

A single self-contained file with well-organized sections (When to Use, Scope Boundaries, Prerequisites, Workflow, Checklist) and no need for external references; structure is clear and easy to navigate.

3 / 3

Total

10

/

12

Passed

Description

90%

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 focused, trigger-rich description that clearly states both capability and activation conditions for a narrow Azure SDK workflow. The only weakness is the second-person 'Use git or GitHub tools directly' clause, which violates the third-person-voice guideline.

DimensionReasoningScore

Specificity

Names concrete actions ('Prepares Azure.ResourceManager SDK refresh pull requests', 'branch, commit, push, and PR creation') and specific paths, but the second-person directive 'Use git or GitHub tools directly' triggers the rubric's −1 specificity penalty for non-third-person voice.

2 / 3

Completeness

Explicitly answers both what (preparing ARM SDK refresh PRs in azure-sdk-for-net) and when (a WHEN: clause with concrete trigger phrases), matching the anchor for full completeness.

3 / 3

Trigger Term Quality

Quoted triggers ('prepare sdk refresh', 'refresh Azure.ResourceManager package', 'update ARM SDK from autorest tag', 'refresh changelog dependencies') give good coverage of natural phrases a maintainer would say for this task.

3 / 3

Distinctiveness Conflict Risk

Scoped tightly to Azure.ResourceManager refresh PRs driven by API-version/tag resolution, a clear niche unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Azure/azure-sdk-for-net
Reviewed

Table of Contents

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.