agent-framework-azure-ai-py
Build Azure AI Foundry agents using the Microsoft Agent Framework Python SDK (agent-framework-azure-ai). Use when creating persistent agents with AzureAIAgentsProvider, using hosted tools (code int...
92
Quality
88%
Does it follow best practices?
Impact
100%
100.00xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Quality
Discovery
89%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 a strong skill description that clearly identifies a specific technology stack (Azure AI Foundry with Microsoft Agent Framework Python SDK) and includes an explicit 'Use when...' clause. The main weakness is that the description appears truncated ('code int...'), which may hide additional capabilities. The technical specificity makes it highly distinctive and unlikely to conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Azure AI Foundry agents) and mentions specific actions like 'creating persistent agents with AzureAIAgentsProvider' and 'using hosted tools', but the description is truncated and doesn't provide a comprehensive list of concrete actions. | 2 / 3 |
Completeness | Clearly answers both what ('Build Azure AI Foundry agents using the Microsoft Agent Framework Python SDK') and when ('Use when creating persistent agents with AzureAIAgentsProvider, using hosted tools'). Has explicit 'Use when...' clause with trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Azure AI Foundry', 'agents', 'Microsoft Agent Framework', 'Python SDK', 'agent-framework-azure-ai', 'AzureAIAgentsProvider', 'hosted tools', 'code int...' (likely code interpreter). These are specific technical terms users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific technology stack (Azure AI Foundry, Microsoft Agent Framework, AzureAIAgentsProvider). Very unlikely to conflict with other skills due to the precise naming of the SDK and provider. | 3 / 3 |
Total | 11 / 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-crafted skill with excellent actionability and conciseness. The code examples are complete and executable, covering the full range of agent capabilities from basic to advanced. The main weakness is the lack of explicit error handling and validation guidance for production scenarios, which is important for Azure service integrations that can fail in various ways.
Suggestions
Add error handling patterns showing how to handle common failures (authentication errors, API rate limits, tool execution failures) with try/except blocks and retry logic
Include a validation checkpoint section showing how to verify agent creation succeeded and how to handle partial failures in multi-tool scenarios
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, assuming Claude's competence with Python, async patterns, and Azure concepts. No unnecessary explanations of basic concepts; every section provides actionable information. | 3 / 3 |
Actionability | All code examples are complete, executable, and copy-paste ready. Includes proper imports, async context managers, and realistic function implementations with type annotations. | 3 / 3 |
Workflow Clarity | While the examples show clear patterns for agent creation and usage, there are no explicit validation checkpoints or error handling guidance for operations that could fail (e.g., credential issues, API errors, tool failures). | 2 / 3 |
Progressive Disclosure | Excellent structure with quick start patterns in the main file and clear one-level-deep references to detailed documentation (tools.md, mcp.md, threads.md, advanced.md). Content is appropriately split between overview and reference files. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- boisenoise/skills-collections
- Commit
5c5ae21
- 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.