CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-mgmt-apicenter-py

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

56

Quality

64%

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-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 highly actionable with clean, executable code examples and good organization, but it reads as an API reference rather than a guided workflow and lacks validation checkpoints for its destructive operations. The 'When to Use' section is circular and adds little.

Suggestions

Add validation/verification checkpoints after destructive or batch operations (e.g., confirm a created API Center via list_by_subscription, or verify an imported spec parses before proceeding).

Replace the circular 'When to Use' line ('applicable to execute the workflow or actions described in the overview') with concrete triggering scenarios.

Trim the repeated resource_group_name/service_name/workspace_name boilerplate by noting shared parameters once and showing only the distinctive arguments in subsequent examples.

DimensionReasoningScore

Conciseness

The body is mostly lean code examples with no concept over-explanation, though the repeated resource_group_name/service_name/workspace_name boilerplate across every snippet adds token overhead that could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready, executable Python covering the common cases (create/list API centers, register APIs, versions, definitions, import specs, environments, deployments, metadata schemas) with correct imports and parameters.

5 / 5

Workflow Clarity

The body is a catalog of independent operations rather than a sequenced workflow, and the destructive/batch operations (create_or_update, import_specification) lack any validation or verification checkpoints, capping workflow clarity at 3.

3 / 5

Progressive Disclosure

Well-organized single-file structure with clear section headers and no nested references; no bundle files exist, and the long operation catalog is reasonably placed inline with only minor split opportunity.

4 / 5

Total

16

/

20

Passed

Description

53%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 domain and purpose but lacks an explicit 'Use when...' trigger clause, leaving the invocation guidance only weakly implied. It is specific enough to be distinct yet generic enough in its verbs to leave capability coverage incomplete.

Suggestions

Add an explicit 'Use when...' trigger clause naming concrete user phrases (e.g., 'Use when the user asks to register or inventory APIs, track API versions, or manage API governance in Azure').

Replace the generic verb 'managing' with concrete operations (e.g., 'create API centers, register APIs and versions, import OpenAPI specs, define metadata schemas, track deployments').

Include natural synonyms users might say ('API catalog', 'API inventory', 'Azure API Center') to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the domain ('Azure API Center Management SDK for Python') and a few action areas ('managing API inventory, metadata, and governance'), but the verb 'managing' is generic rather than enumerating concrete operations like register, version, or deploy.

3 / 5

Completeness

The 'what' is clear, but the 'when' is only weakly implied via 'Use for managing...' rather than an explicit 'Use when...' trigger clause, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Relevant terms appear ('API Center', 'API inventory', 'metadata', 'governance') that a user might say, but common variations and synonyms are missing and there is no explicit natural-language trigger phrase.

3 / 5

Distinctiveness Conflict Risk

Azure API Center is a specific niche with distinct triggers and low conflict risk, though the broad governance framing has minor overlap with adjacent Azure management skills.

4 / 5

Total

13

/

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.