agent-framework-azure-ai-py

Build persistent agents on Azure AI Foundry using the Microsoft Agent Framework Python SDK.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

65%

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 complete, executable code examples, but it is padded by repetitive boilerplate and generic templated sections, and its reference files point to a bundle that is not present. Workflow clarity lacks validation checkpoints for risky operations.

Suggestions

Consolidate the repeated async-with setup boilerplate into a single reusable snippet referenced by later examples to reduce token weight.

Replace the generic 'When to Use' and 'Limitations' template text with skill-specific guidance or remove it.

Either provide the referenced references/*.md files or remove the Reference Files section so signaled navigation matches the actual bundle.

Add validation/verification checkpoints (e.g. confirm credential resolution, validate structured-output responses) for risky operations.

Dimension	Reasoning	Score
Conciseness	Content is mostly efficient and code-forward, but the repeated async-with boilerplate across many near-identical examples and the generic templated 'When to Use'/'Limitations' sections could be tightened; not the lean level-3 anchor.	2 / 3
Actionability	Provides fully executable, copy-paste-ready code with specific commands and concrete examples throughout (installation, env vars, function/hosted tools, streaming, threads, structured outputs), matching the level-3 anchor.	3 / 3
Workflow Clarity	Examples are organized by feature with a logical progression, but there are no validation checkpoints or error-recovery feedback loops for risky operations like agent deployment or structured-output parsing, capping the score at 2.	2 / 3
Progressive Disclosure	The body signals one-level-deep references (references/tools.md, mcp.md, threads.md, advanced.md) but those bundle files do not exist in the skill, so navigation is signaled without a real bundle to back it; structure is present but not verified.	2 / 3
	Total	9 / 12 Passed

Description

67%

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 is specific and clearly niche-scoped to Azure AI Foundry persistent agents, but it omits an explicit 'Use when' trigger clause and relies on technical terminology over natural user phrasing. Trigger guidance and completeness are the weakest aspects.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases (e.g. 'Use when building Azure AI agents, persistent agents, or Azure AI Foundry assistants').

Broaden trigger terms to include user-natural phrasings like 'Azure AI assistant', 'AI Foundry agent', and 'persistent chatbot' rather than only SDK jargon.

Dimension	Reasoning	Score
Specificity	Names concrete actions ('Build persistent agents') tied to a specific platform and SDK ('Azure AI Foundry', 'Microsoft Agent Framework Python SDK'), matching the multiple-specific-actions anchor rather than the single-domain anchor at 2.	3 / 3
Completeness	Clearly states what the skill does but lacks an explicit 'Use when...' trigger clause, which the guidelines cap at 2 rather than 3.	2 / 3
Trigger Term Quality	Relevant terms exist ('Azure AI Foundry', 'Agent Framework', 'Python SDK') but lean toward technical jargon and miss common natural variations a user would say; not the broad coverage of the level-3 anchor.	2 / 3
Distinctiveness Conflict Risk	The narrow Azure AI Foundry persistent-agent niche with distinct platform triggers is unlikely to conflict with other skills, matching the level-3 anchor.	3 / 3
	Total	10 / 12 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 4 missing	Warning

	Total	14 / 16 Passed

Repository: boisenoise/skills-collections
Commit: 56fd61a

Reviewed: 2 days 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.