CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-mgmt-apicenter-dotnet

Azure API Center SDK for .NET. Centralized API inventory management with governance, versioning, and discovery.

60

Quality

70%

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

Fix and improve this skill with Tessl

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

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

SKILL.md
Quality
Evals
Security

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 body is a strong, highly actionable SDK reference with comprehensive executable workflows and clear sequencing. Its main weaknesses are the absence of progressive disclosure into bundle files and a lack of explicit validation checkpoints in the workflows.

Suggestions

Move the long Key Types Reference and detailed per-workflow examples into a separate reference file (e.g., references/workflows.md) and keep SKILL.md as a concise overview with signaled links.

Add explicit validation checkpoints to multi-step workflows (e.g., verify a resource exists before creating dependents, confirm an import succeeded before exporting).

Replace the generic 'When to Use' filler line with concrete trigger conditions that match the description's intended usage.

DimensionReasoningScore

Conciseness

The body is mostly executable code with minimal prose explaining concepts Claude already knows; the only padding is the generic filler line 'This skill is applicable to execute the workflow or actions described in the overview.' and a few verbose reference tables that could be trimmed.

4 / 5

Actionability

Ten fully executable, copy-paste-ready C# workflows plus an error-handling block cover the common cases concretely with real types, parameters, and method calls.

5 / 5

Workflow Clarity

The resource hierarchy and numbered workflows 1-10 give a clear dependency-ordered sequence, and error handling is shown, but there are no explicit validate-then-proceed checkpoints; since these are resource-creation operations rather than destructive/batch ones, the destructive cap does not apply.

4 / 5

Progressive Disclosure

Sections are well-organized with headers, but no bundle files exist (references/scripts/assets absent) and ~400 lines of workflows plus a types table are all inlined in SKILL.md rather than split into one-level-deep reference files; the under-50-line exception does not apply.

3 / 5

Total

16

/

20

Passed

Description

61%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 clearly identifies the SDK niche and its main capability areas but reads as a feature list rather than concrete actions and lacks any explicit 'Use when...' trigger guidance. It is solid but not exemplary.

Suggestions

Add an explicit trigger clause, e.g. 'Use when managing Azure API Center resources, API inventory, or governance with the .NET SDK'.

Replace abstract capability nouns with concrete verbs the SDK performs (e.g., 'Create APIs, workspaces, versions, and deployments; import OpenAPI specs; define metadata schemas').

Include natural task phrasings or file/package tokens (e.g., 'Azure.ResourceManager.ApiCenter', 'API catalog') to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the domain ('Azure API Center SDK for .NET') and a few capability areas ('inventory management with governance, versioning, and discovery'), but these are abstract feature nouns rather than concrete actions and omit the CRUD/metadata/environments operations the body actually covers, so it is not comprehensive.

3 / 5

Completeness

There is a clear 'what' (the SDK and its capability areas) but no 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural terms a user would say ('Azure API Center', '.NET', 'API inventory', 'governance', 'versioning', 'discovery') with good coverage, though a few natural synonyms or task phrasings are missing.

4 / 5

Distinctiveness Conflict Risk

'Azure API Center SDK for .NET' carves a clear niche with minimal conflict risk, though it has minor overlap with the related Azure Resource Manager ApiManagement SDK.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.