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.
Install with Tessl CLI
npx tessl i github:microsoft/azure-skills --skill azure-aigateway95
Quality
93%
Does it follow best practices?
Impact
95%
1.72xAverage score across 3 eval scenarios
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly defines its purpose (Azure API Management as AI Gateway) and provides comprehensive trigger terms covering the full scope of the skill. The explicit 'WHEN:' clause with extensive keyword coverage ensures Claude can accurately select this skill when relevant. The description is specific to a clear niche with minimal conflict risk.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: '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.' | 3 / 3 |
Completeness | Clearly answers both what ('Configure Azure API Management as an AI Gateway for AI models, MCP tools, and agents') and when (explicit 'WHEN:' clause with comprehensive trigger scenarios). The structure explicitly separates capability from trigger conditions. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'semantic caching', 'token limit', 'content safety', 'load balancing', 'jailbreak detection', 'Azure OpenAI', 'AI Foundry', 'MCP rate limiting', 'AI cost control', 'OpenAPI to gateway'. These are terms practitioners would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: Azure API Management + AI Gateway is a specific domain. Trigger terms like 'Azure OpenAI backend', 'AI Foundry model', 'MCP rate limiting', and 'import OpenAPI to gateway' are unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with excellent conciseness and actionability. The quick reference table, executable CLI commands, and clear progressive disclosure to reference materials make it highly usable. The main gap is the lack of explicit validation steps when applying governance policies, which could lead to misconfigurations.
Suggestions
Add validation/verification steps after applying policies (e.g., 'Test with curl to confirm policy is active before proceeding')
Include a rollback or recovery note for policy changes that break API behavior
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, using tables for quick reference, minimal prose, and assuming Claude understands Azure/APIM concepts without explanation. Every section serves a clear purpose with no padding. | 3 / 3 |
Actionability | Provides fully executable bash commands with proper flags and placeholders, copy-paste ready curl examples, and specific CLI commands for common tasks. The code examples are complete and runnable. | 3 / 3 |
Workflow Clarity | The 'Apply AI Governance Policy' section lists recommended order but lacks explicit validation checkpoints. For policy configuration (which can break API behavior), there's no validate-then-apply workflow or rollback guidance. | 2 / 3 |
Progressive Disclosure | Excellent structure with a concise overview, quick reference table, and clear one-level-deep references to detailed policies, patterns, troubleshooting, and SDK docs. Navigation is well-signaled with descriptive links. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.