azure-ai-projects-py

Build AI applications on Microsoft Foundry using the azure-ai-projects SDK.

Quality

48%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/azure-ai-projects-py/SKILL.md

Quality

Discovery

32%

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 identifies a specific platform and SDK but is too terse and lacks concrete actions and explicit trigger guidance. It would benefit greatly from listing specific capabilities (e.g., creating agents, managing connections, deploying models) and adding a 'Use when...' clause with natural trigger terms users would employ.

Suggestions

Add a 'Use when...' clause with trigger terms like 'Azure AI Foundry', 'azure-ai-projects', 'AI agents on Azure', 'Azure AI Studio', 'Foundry project'.

List specific concrete actions such as 'create AI agents, manage connections, configure deployments, run evaluations' to improve specificity.

Include common keyword variations users might say, such as 'Azure AI Foundry', 'Azure AI Studio', 'foundry SDK', and 'azure ai project setup'.

Dimension	Reasoning	Score
Specificity	Names the domain (AI applications on Microsoft Foundry) and mentions a specific SDK (azure-ai-projects), but does not list concrete actions like 'create agents', 'deploy models', 'manage datasets', etc.	2 / 3
Completeness	Describes what at a high level (build AI applications) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also weak, so this scores 1.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'Microsoft Foundry', 'azure-ai-projects SDK', and 'AI applications', but misses common variations users might say such as 'Azure AI Foundry', 'Azure AI Studio', 'foundry agent', or 'azure ai project'.	2 / 3
Distinctiveness Conflict Risk	The mention of 'Microsoft Foundry' and 'azure-ai-projects SDK' provides some distinctiveness, but 'Build AI applications' is broad enough to potentially overlap with other Azure or AI development skills.	2 / 3
	Total	7 / 12 Passed

Implementation

64%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a solid SDK reference skill with strong actionability—nearly every section includes executable code. Its main weaknesses are the lack of validation/error-handling checkpoints in multi-step workflows and moderate verbosity from sections that could be trimmed or offloaded to reference files. The progressive disclosure structure is well-conceived but undermined by missing bundle files and some inline content bloat.

Suggestions

Add error handling and validation checkpoints to multi-step workflows (e.g., check run.status for 'failed'/'expired', handle authentication errors, add cleanup in failure paths).

Trim or remove boilerplate sections ('When to Use', 'Limitations') and the SDK Comparison table to improve conciseness—these don't add actionable value for Claude.

Move detailed sections like Memory Stores, Evaluation, and Datasets/Indexes content into their respective reference files, keeping only a one-liner + link in the main SKILL.md.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient with good code examples, but includes some unnecessary sections like 'When to Use' and 'Limitations' boilerplate, the SDK Comparison table explaining azure-ai-agents (not directly needed), and the 'Best Practices' section contains guidance Claude could infer. The overall length (~250 lines) is reasonable for the breadth of coverage but could be tightened.	2 / 3
Actionability	Nearly all guidance is backed by concrete, executable Python code snippets covering authentication, agent creation, thread/message flow, tools, connections, deployments, evaluation, async usage, and memory stores. Code is copy-paste ready with proper imports and environment variable references.	3 / 3
Workflow Clarity	The Thread and Message Flow section provides a clear numbered sequence, but there's no validation or error handling guidance for any workflow. Agent creation, evaluation runs, and other multi-step operations lack checkpoints (e.g., checking run status for failures, handling authentication errors, cleanup on failure). The best practices mention cleanup but don't integrate it into workflows.	2 / 3
Progressive Disclosure	The skill references 11 separate reference files and a script, which is excellent structure in principle. However, no bundle files were provided, so these references are unverifiable. The main file itself is quite long with substantial inline content that could have been pushed to references (e.g., the full evaluation, memory stores, and datasets sections). References are listed but not consistently formatted as navigable links.	2 / 3
	Total	9 / 12 Passed

Validation

90%

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 — 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: sickn33/antigravity-awesome-skills
Commit: 9e5d4dd

Reviewed: 6 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.