CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

azure-mgmt-apicenter-py

Azure API Center Management SDK for Python. Use for managing API inventory, metadata, and governance across your organization.

Quality

77%

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-claude/skills/azure-mgmt-apicenter-py/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

76%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 content is a strong, fully executable cookbook for the azure-mgmt-apicenter SDK: concise sections, runnable code, and clear operation coverage. Its only structural weakness is the absence of an explicit workflow ordering with validation checkpoints for chained operations.

DimensionReasoningScore

Conciseness

The body is dominated by executable snippets under terse headers with almost no conceptual padding. Minor filler could be trimmed: the single-row "Client Types" table and the vacuous "When to Use" line ("This skill is applicable to execute the workflow or actions described in the overview."), which adds no information.

4 / 5

Actionability

Every section is copy-paste-ready, executable code with realistic parameters covering the common cases: installation, environment setup, authentication, service creation, API registration, versions, definitions, inline spec import, environments, deployments, and metadata schemas. There is no pseudocode or vague direction.

5 / 5

Workflow Clarity

Tasks are presented as independent per-section snippets with only an implicit sequence (service → API → version → definition → deployment); there are no explicit checkpoints such as verifying the service exists before registering an API or confirming a spec import succeeded. This matches the anchor of steps present but validation implicit.

3 / 5

Progressive Disclosure

A single-file skill with no bundle files, organized with per-task headers and Operations/Client tables, and no nested references. Structure is good; minor gaps include the redundant Client Types table and an operation catalog that could partially move to a reference file if the skill grows.

4 / 5

Total

16

/

20

Passed

Description

70%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 clear, in third person, and reasonably specific with a valid domain niche and an explicit 'Use for' clause. Its main weakness is that the capability list stays at the level of objects rather than concrete operations, and the trigger guidance lacks user-facing phrases.

Suggestions

List concrete operations in the description, e.g. "Register APIs, create API versions and definitions, import OpenAPI specifications, track deployments, and define custom metadata schemas in Azure API Center."

Replace the purpose-scoped "Use for managing API inventory, metadata, and governance across your organization" with user-trigger phrasing such as "Use when the user asks to register an API, import an OpenAPI spec, or manage API Center metadata in Azure".

Add natural synonyms users might say (e.g. "API catalog", "API governance", "OpenAPI") to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain clearly ("Azure API Center Management SDK for Python") and objects ("API inventory, metadata, and governance"), but "managing" is generic — no concrete operations such as registering APIs, importing OpenAPI specifications, or tracking deployments are listed, so it matches the 'domain plus 1-2 concrete actions, not comprehensive' anchor.

3 / 5

Completeness

Answers both: the "what" (Azure API Center Management SDK for Python; managing API inventory, metadata, and governance) and an explicit "Use for managing..." clause for "when". The 'when' is purpose-scoped rather than concrete user-trigger phrases ("Use when the user asks to..."), so it matches the anchor where 'when' could be more explicit.

4 / 5

Trigger Term Quality

Good natural keywords users would say: "Azure API Center", "Python", "API inventory", "metadata", "governance". A few natural terms are missing ("API catalog", "register API", "OpenAPI"), which keeps it below the comprehensive-synonym anchor.

4 / 5

Distinctiveness Conflict Risk

"Azure API Center" is a distinct niche product name with clear triggers, giving a mostly-distinct profile; minor overlap risk remains with other broad Azure SDK or governance skills.

4 / 5

Total

15

/

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.

Validation — 15 / 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

Path

plugins/AI-Agents-Safe-Coding-Skills-claude/skills/azure-mgmt-apicenter-py/SKILL.md

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.