CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-aigateway

Configure Azure API Management as an AI Gateway for AI models, MCP tools, and agents. WHEN: semantic caching, token limit, content safety, load balancing, AI model governance, MCP rate limiting, jailbreak detection, add Azure OpenAI backend, add AI Foundry model, test AI gateway, LLM policies, configure AI backend, token metrics, AI cost control, convert API to MCP, import OpenAPI to gateway.

70

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

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.

A well-structured skill body that pairs lean reference tables with executable Azure CLI/curl/XML snippets and cleanly defers detail to a verified one-level-deep reference bundle. Minor conciseness and inline-validation gaps prevent a perfect content score.

Suggestions

Move or inline a brief validate-then-proceed checkpoint (e.g., test the endpoint returns 200 after applying a policy) so the main workflow has an explicit feedback loop rather than relying on the troubleshooting file.

Add a one-line pointer to references/auth-best-practices.md, which exists in the bundle but is currently orphaned (not linked from SKILL.md), so the managed-identity/RBAC steps are discoverable.

Tighten the prose around the recommended policy order by folding it into the existing Quick Reference table to avoid restating what the table already shows.

DimensionReasoningScore

Conciseness

Lean tables and copy-pasteable code that assumes Azure knowledge with no padding about what APIM or a PDF-equivalent concept is; a few lines like the recommended policy-order prose and inline troubleshooting rows edge toward explanation that could be trimmed, so it sits at 4 rather than 5.

4 / 5

Actionability

Concrete, executable `az apim`, `curl`, and XML policy snippets cover the common cases, comparable to the 4-anchor executable example; placeholders like <apim-name> and the "See references/patterns.md" pointers leave minor gaps keeping it below 5.

4 / 5

Workflow Clarity

The "Apply AI Governance Policy" section gives a numbered 6-step order and the troubleshooting table maps symptoms to fixes, a clear sequence with most checkpoints; explicit validate-then-proceed feedback loops live in the referenced patterns file rather than inline, so a minor validation gap keeps it at 4.

4 / 5

Progressive Disclosure

SKILL.md is a concise overview with well-signaled, one-level-deep references to policies.md, patterns.md, troubleshooting.md, and sdk/ quick refs; every anchor referenced (token-rate-limiting, semantic-caching, content-safety, combining-policies, etc.) resolves to a real heading in a real bundle file, matching the "Clear overview with well-signaled one-level-deep references" anchor.

5 / 5

Total

17

/

20

Passed

Description

95%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.

A strong, highly specific description that clearly states the skill's purpose and provides a rich explicit WHEN clause of natural trigger phrases. It is distinct from adjacent Azure skills and avoids vague fluff.

DimensionReasoningScore

Specificity

Lists several specific concrete actions across model, tool, and agent governance ("semantic caching", "token limit", "content safety", "load balancing", "convert API to MCP", "import OpenAPI to gateway"), comparable to the anchor "Extracts text from PDF files, fills forms, converts pages to images"; just short of fully comprehensive coverage so it stays at 4 rather than 5.

4 / 5

Completeness

Explicitly answers both: what ("Configure Azure API Management as an AI Gateway for AI models, MCP tools, and agents") and when (explicit "WHEN:" clause with concrete trigger phrases), matching the anchor that includes both a clear what and an explicit "Use when..." trigger list.

5 / 5

Trigger Term Quality

Comprehensive coverage of natural phrases users would say ("semantic caching", "jailbreak detection", "content safety", "load balancing", "convert API to MCP", "add Azure OpenAI backend", "test AI gateway") plus synonyms/variants, matching the anchor "PDF files, PDFs, forms, document extraction, .pdf".

5 / 5

Distinctiveness Conflict Risk

Occupies a clear Azure AI Gateway niche with distinct, domain-specific triggers ("MCP rate limiting", "jailbreak detection", "add AI Foundry model") unlikely to fire for unrelated skills, matching the "Clear niche with distinct triggers; minimal conflict risk" anchor.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 4 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 4 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository
microsoft/azure-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.