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

Blog Docs Log in Get started

azure-mgmt-apimanagement-dotnet

Azure Resource Manager SDK for API Management in .NET.

Quality

60%

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/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

65%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 with complete, executable examples and a clear resource-hierarchy and workflow structure. Its weaknesses are missing validation checkpoints for batch/destructive operations, some filler and an inline version number, and a reference table pointing to files that are not bundled.

Suggestions

Add validation checkpoints after long-running or batch operations, e.g. verify the provisioning state after CreateOrUpdate and confirm a backup completed before relying on it.

Move the time-sensitive version number (v1.3.0) into a versioned/deprecated section or remove it from the overview.

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

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and code-dense, but the "When to Use" line is generic filler and an inline time-sensitive version number (v1.3.0) appears outside any deprecated/old-patterns section, which the guidelines penalize; this matches anchor 3 rather than the leaner anchor 4.	3 / 5
Actionability	The guide provides fully executable, copy-paste-ready C# that covers the common cases (service, API, product, subscription, policy, backup/restore), matching anchor 5.	5 / 5
Workflow Clarity	Six numbered workflow steps are clearly sequenced, but backup/restore and CreateOrUpdate are batch/long-running operations with no validation or verification checkpoints; the guidelines cap workflow_clarity at 3 for this, so it does not reach anchor 4.	3 / 5
Progressive Disclosure	A well-signaled one-level reference table is present, but the referenced files (references/*.md) are not bundled and a fair amount of detail is inlined, matching anchor 3 rather than the well-resolved anchor 4.	3 / 5
	Total	14 / 20 Passed

Description

56%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 distinct and uses natural domain keywords, but it is minimal: it states only what the SDK is without enumerating concrete actions or providing an explicit use-when trigger clause. Adding actions and a trigger clause would substantially raise completeness and specificity.

Suggestions

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

Append an explicit "Use when" trigger clause, e.g. "Use when provisioning or managing Azure API Management resources from a .NET application."

Include common synonyms such as APIM and gateway to improve trigger-term coverage toward a 5.

Dimension	Reasoning	Score
Specificity	The description names the domain precisely ("Azure Resource Manager SDK for API Management in .NET") but lists no concrete actions such as provision, manage, or deploy, matching anchor 2 rather than the vague anchor 1 or the action-listing anchor 3.	2 / 5
Completeness	It gives a clear "what" (an ARM SDK for API Management in .NET) but no "when" / "Use when" clause at all; per the judging guidelines a missing explicit trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	"Azure Resource Manager", "API Management", and ".NET" are exactly the natural terms a user would say, giving good keyword coverage; it falls short of anchor 5 only because common synonyms like APIM or gateway are absent.	4 / 5
Distinctiveness Conflict Risk	The niche is specific with minimal conflict risk, but it could overlap with sibling Azure ARM SDK skills and no distinct triggers are articulated, placing it at anchor 4 rather than 5.	4 / 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/skills/azure-mgmt-apimanagement-dotnet/SKILL.md
Commit: 57c135b

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