CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

agent-framework-azure-ai-py

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

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/agent-framework-azure-ai-py/SKILL.md

The canonical home for this skill is agent-framework-azure-ai-py in sickn33/agentic-awesome-skills

SKILL.md
Quality
Evals
Security

Quality

Content

60%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-organized, highly actionable reference with real, runnable code covering the framework's main patterns. Its two weaknesses are significant redundancy (the Complete Example section and the vacuous When to Use line) and a broken progressive-disclosure structure — the body advertises four reference files that do not exist in the bundle.

Suggestions

Ship the four advertised reference files (references/tools.md, mcp.md, threads.md, advanced.md) or remove the "Reference Files" section — as written, every reference pointer in the skill is dangling.

Delete or drastically shrink the "Complete Example" section (it re-covers all six patterns already demonstrated) and remove the filler "When to Use" line that states nothing actionable.

Make each code snippet self-contained: add the missing asyncio import/run in the function-tools example and show how BING_CONNECTION_ID is actually consumed by HostedWebSearchTool.

DimensionReasoningScore

Conciseness

The body is mostly lean and code-first with almost no padded prose, but the ~80-line "Complete Example" re-demonstrates every pattern already shown in its own section (basic agent, function tools, hosted tools, MCP, streaming, threads, structured outputs), and the closing "When to Use" line ("This skill is applicable to execute the workflow or actions described in the overview.") is pure filler. Anchor 3 fits; not 4 because the redundancy is more than minor.

3 / 5

Actionability

Concrete, executable guidance throughout: pip install commands, env var exports, auth snippets, and complete Python for agents, tools, streaming, threads, and structured outputs. Minor gaps keep it below anchor 5: the function-tools example omits the asyncio import and asyncio.run() call, the threads example uses get_weather defined only in an earlier snippet, and BING_CONNECTION_ID is exported but never wired into any HostedWebSearchTool usage.

4 / 5

Workflow Clarity

A coherent, logical progression from install → env vars → auth → basic agent → tools → streaming → threads → structured outputs, with each step fully specified in runnable code. Not 5 because there are no checkpoints or error-recovery guidance for the likely failure points (missing env vars, auth errors, the --pre package flag); not 3 because the sequence is complete and unambiguous, and no destructive/batch operations exist that would require validation loops.

4 / 5

Progressive Disclosure

The "Reference Files" section points to references/tools.md, references/mcp.md, references/threads.md, and references/advanced.md, but no references/ directory exists in the bundle — all four pointers are dangling and lead nowhere. On top of that, ~330 lines of detail (complete example, tool tables) are inlined in SKILL.md where the missing reference files presumably belong. Anchor 2 fits (broken/buried references, content inlined that belongs in separate files); not 3 because the references are not merely unclear, they are absent; not 1 because the body itself has clear section headers and the pointers would be one level deep if the files existed.

2 / 5

Total

13

/

20

Passed

Description

61%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 clean, third-person, appropriately concise description that clearly states what the skill does and names the exact technology stack. Its main deficiency is the absence of any "Use when..." trigger clause, which caps completeness and weakens trigger guidance for the model selecting skills.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user mentions Azure AI Foundry, Microsoft Agent Framework, building persistent/hosted AI agents in Python, or Foundry agent service."

Enumerate 2-3 more concrete capabilities in the description (function tools, hosted/code-interpreter/web-search tools, MCP integration, conversation threads, structured outputs) to raise specificity from a single action to comprehensive coverage.

DimensionReasoningScore

Specificity

The description names the domain ("Azure AI Foundry", "Microsoft Agent Framework Python SDK") and one concrete action ("Build persistent agents"), matching anchor 3. It is not 4 because it lists only a single action while the skill actually covers tools, MCP, threads, streaming, and structured outputs; it is not 2 because the domain and action are concrete rather than generic.

3 / 5

Completeness

The "what" is clear and specific, but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Not 2 because the "what" is concrete, not vague; not 4 because the "when" is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Natural keywords a user would actually say are present: "persistent agents", "Azure AI Foundry", "Microsoft Agent Framework", "Python SDK". It falls short of anchor 5 because common variations and synonyms ("AI agents", "hosted agents", "Foundry", "agent framework python") are missing, and is clearly above anchor 3 since the core trigger terms are specific and complete.

4 / 5

Distinctiveness Conflict Risk

The named product stack ("Microsoft Agent Framework" + "Azure AI Foundry" + "Python SDK") is a clear, unmistakable niche with only minor overlap risk from closely related Azure agent-building skills. Not 5 because generic words like "agents" and "Python" could still collide with other skills and the missing trigger clause weakens distinct triggering.

4 / 5

Total

14

/

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.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills/skills/agent-framework-azure-ai-py/SKILL.md

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.