Name: azure-api-management
Rating: 62.4 (1 reviews)
Author: membranedev

azure-api-management

Azure API Management integration. Manage data, records, and automate workflows. Use when the user wants to interact with Azure API Management data.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/azure-api-management/SKILL.md

Quality

Content

82%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 concrete, executable Membrane CLI commands and a strong state-machine feedback loop for connection setup. Weaker spots are minor padding, inconsistent step numbering, and a redundant 'Popular actions' section.

Suggestions

Tighten the intro: remove the explanatory sentence about what Azure API Management is and the filler line 'Use action names and parameters as needed.'

Fix the step numbering (the body references 'Step 2' and '1b' without a clearly numbered Step 1) so the workflow reads as a coherent ordered sequence.

Add a brief validation/check step after running an action (e.g. inspect the `output` field and handle error states) to close the workflow loop on action execution.

Dimension	Reasoning	Score
Conciseness	The body is mostly concrete commands with little padding, but includes minor over-explanation (the intro sentence on what APIM does, the resource hierarchy tree, 'Use action names and parameters as needed.', and a duplicated action-list instruction in 'Popular actions').	4 / 5
Actionability	It provides copy-paste-ready, fully executable commands throughout — install, login, connection ensure, connection get --wait, action list/run with --input, and a thorough proxy request flags table covering the common cases.	5 / 5
Workflow Clarity	A clear install → auth → connect → poll → search → run sequence exists with explicit state-based validation checkpoints and an error-recovery feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but step numbering is inconsistent ('skip to Step 2', '1b') and there is no validation step on action-run output.	4 / 5
Progressive Disclosure	The single SKILL.md is well-organized into clearly headed sections with no nested references, appropriate for a single-file skill; however it exceeds the under-50-line simple-skill threshold and the 'Popular actions' section is thin/redundant, a minor organization gap.	4 / 5
	Total	17 / 20 Passed

Description

66%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 explicitly covers both what the skill does and when to use it, anchored to a clearly distinct named service. Its main weakness is generic action language ('manage data, records, automate workflows') and limited trigger-term variation.

Suggestions

Replace generic verbs with concrete Azure API Management capabilities, e.g. 'publish, secure, transform, and analyze APIs; manage gateways, products, subscriptions, and policies'.

Broaden the 'Use when' trigger to include natural phrases users say, such as 'API gateway', 'publish APIs', 'developer portal', or 'API subscriptions'.

Drop the vague 'Manage data, records' phrasing, which overlaps with many skills and weakens distinctiveness.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Azure API Management integration') and a couple of action verbs ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete capabilities like publish, secure, or transform APIs.	3 / 5
Completeness	It answers both 'what' (integration, manage data/records, automate workflows) and 'when' with an explicit 'Use when the user wants to interact with Azure API Management data' clause, though the 'when' trigger is somewhat narrow.	4 / 5
Trigger Term Quality	'Azure API Management' is the natural term a user would say and it appears, but common variations and synonyms like 'API gateway', 'publish APIs', or 'developer portal' are missing.	3 / 5
Distinctiveness Conflict Risk	'Azure API Management' is a clear, named-service niche with distinct triggers and minimal conflict risk with other skills.	5 / 5
	Total	15 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/azure-api-management/SKILL.md
Commit: f484c82

Reviewed: less than a minute 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.