CtrlK
BlogDocsLog inGet started
Tessl Logo

azsdk-common-apiview-feedback-resolution

Analyze and resolve APIView review feedback on Azure SDK PRs. **UTILITY SKILL**. USE FOR: APIView comments, API review feedback, SDK API surface changes. DO NOT USE FOR: general code review, non-APIView feedback. INVOKES: azure-sdk-mcp:azsdk_apiview_get_comments, azure-sdk-mcp:azsdk_customized_code_update, azure-sdk-mcp:azsdk_typespec_delegate_apiview_feedback, azure-sdk-mcp:azsdk_run_typespec_validation, azure-sdk-mcp:azsdk_package_generate_code.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The content is token-efficient, actionable with exact tool names, and structured as a clear validated workflow. It appropriately offloads detail to a single well-signaled reference file rather than inlining it.

DimensionReasoningScore

Conciseness

The body is lean, using a tool table and a numbered step list without explaining what APIView or TypeSpec are; it assumes Claude's competence and every token earns its place, matching the score-3 anchor.

3 / 3

Actionability

It names exact MCP tools (e.g. azsdk_apiview_get_comments, azsdk_customized_code_update) and gives concrete numbered steps plus a troubleshooting block with executable guidance, matching the score-3 anchor.

3 / 3

Workflow Clarity

A clear 5-step sequence (Retrieve, Categorize, Resolve, Validate, Confirm) with an explicit validation checkpoint ("Validate, regenerate, build, and test after applying fixes") and an error-recovery loop in Troubleshooting; not capped at 2 because validation is present.

3 / 3

Progressive Disclosure

SKILL.md is a concise overview that links to a single real one-level-deep reference (references/feedback-resolution-steps.md), clearly signaled twice including an anchor, matching the score-3 anchor; not 2 because the split is clean and navigation is explicit.

3 / 3

Total

12

/

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.

The description is specific, third-person, and provides explicit USE FOR / DO NOT USE FOR triggers alongside concrete actions and invoked tools. It cleanly answers both what and when with minimal padding.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ("Analyze and resolve APIView review feedback", retrieve/categorize comments, apply TypeSpec or customization updates, re-review) rather than vague language, matching the score-3 anchor.

3 / 3

Completeness

Explicitly answers both what ("Analyze and resolve APIView review feedback on Azure SDK PRs") and when (a clear "USE FOR" clause with explicit triggers), matching the score-3 anchor; not 2 because the when is explicit rather than implied.

3 / 3

Trigger Term Quality

The "USE FOR: APIView comments, API review feedback, SDK API surface changes" clause and the body examples ("resolve APIView comments", "address API review feedback") are natural terms a user would say, giving good coverage; not score 2 because common variations are present.

3 / 3

Distinctiveness Conflict Risk

The "DO NOT USE FOR: general code review, non-APIView feedback" clause carves out a clear niche unlikely to trigger the wrong skill, matching the score-3 anchor.

3 / 3

Total

12

/

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.