Name: azure-mgmt-apimanagement-dotnet
Rating: 54.400000000000006 (1 reviews)
Author: administrakt0r

Blog Docs Log in Get started

azure-mgmt-apimanagement-dotnet

Azure Resource Manager SDK for API Management in .NET.

Quality

62%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/azure-mgmt-apimanagement-dotnet/SKILL.md

The canonical home for this skill is azure-mgmt-apimanagement-dotnet in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

72%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 highly actionable and concise with comprehensive executable examples, but its long-running/destructive workflows lack validation checkpoints and its progressive disclosure is undermined by missing reference files. Adding verification steps and creating the referenced files would lift the weaker dimensions.

Suggestions

Add validation checkpoints to the core workflow (e.g. verify the service is active before creating APIs; confirm backup blob exists after BackupAsync) to satisfy the destructive/long-running-operation feedback-loop requirement.

Create the referenced files (references/service-management.md, apis-operations.md, products-subscriptions.md, policies.md) or remove the broken reference table.

Move the large Resource Hierarchy, Key Types, and SKU tables into the corresponding reference files to keep SKILL.md an overview.

Dimension	Reasoning	Score
Conciseness	The body is largely lean with executable code and minimal prose, and does not over-explain concepts Claude already knows; only minor sections (the management-vs-data-plane warning and a few commentary lines) could be trimmed, matching the 'efficient; minor instances of over-explanation' anchor.	4 / 5
Actionability	Copy-paste-ready C# examples cover the common cases (create service, API, product, subscription, policy, backup/restore) plus concrete install and env-var commands, matching the 'fully executable; specific examples cover the common cases' anchor.	5 / 5
Workflow Clarity	The six-step Core Workflow is clearly sequenced, but it involves long-running/destructive operations (30+ min service creation, backup/restore) with no validation or verification checkpoints, which the rubric caps at 3.	3 / 5
Progressive Disclosure	References are signaled in a table, but the referenced files (references/service-management.md, apis-operations.md, etc.) do not exist in the bundle, and substantial reference-style content (resource hierarchy, SKU/types tables) is inlined, matching the 'some structure but references not cleanly backed and inline content that should be separate' level.	3 / 5
	Total	15 / 20 Passed

Description

52%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 specific and clearly niched but terse: it states what the skill is without listing concrete actions or any 'when to use' trigger guidance. Adding concrete verbs and a Use-when clause would raise specificity and completeness.

Suggestions

Add concrete actions, e.g. 'Provision and manage Azure API Management services, APIs, products, subscriptions, and policies'.

Append a 'Use when...' trigger clause naming natural phrases users say (e.g. 'Use when provisioning Azure API Management resources in .NET').

Include common synonyms/extensions such as 'APIM', 'ARM', and the package name to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Azure Resource Manager SDK for API Management in .NET') but states no concrete actions, only that it is an SDK, which matches the 'names domain but actions minimal or generic' anchor rather than the level-3 anchor requiring 1-2 concrete actions.	2 / 5
Completeness	A clear 'what' is present (an SDK for API Management) but there is no 'when'/'Use when' clause, and the rubric guideline caps completeness at 3 when trigger guidance is missing.	3 / 5
Trigger Term Quality	It includes relevant terms a user might say ('Azure', 'API Management', '.NET', 'Resource Manager') but omits common synonyms and file/package extensions, matching the 'some relevant keywords but missing common variations or synonyms' anchor.	3 / 5
Distinctiveness Conflict Risk	It targets a narrow, specific niche (Azure API Management management-plane SDK for .NET) with distinct triggers and minimal overlap risk with other skills, matching the 'clear niche with distinct triggers' anchor.	5 / 5
	Total	13 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 4 missing	Warning

	Total	14 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/azure-mgmt-apimanagement-dotnet/SKILL.md
Commit: 57c135b

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