azure-ai-projects-ts

High-level SDK for Azure AI Foundry projects with agents, connections, deployments, and evaluations.

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-ts/SKILL.md

Quality

Content

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 API reference skill with excellent actionability — nearly every operation has executable TypeScript code. Its main weaknesses are the monolithic structure (all content inline with no progressive disclosure to supporting files) and the lack of validation/error-handling guidance in multi-step workflows. Some generic boilerplate sections ('When to Use', 'Limitations') waste tokens without adding value.

Suggestions

Remove the generic 'When to Use' and 'Limitations' sections, which are boilerplate that Claude doesn't need.

Add error handling and validation checkpoints to the 'Run Agent' workflow (e.g., check agent creation success, handle authentication failures).

Split the lengthy Agents section (especially the tool examples) into a separate AGENTS.md reference file and link to it from the main skill.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient with executable code examples, but includes some unnecessary sections like 'When to Use' and 'Limitations' that are generic boilerplate adding no value. The 'Best Practices' section contains some obvious advice (e.g., 'don't hardcode credentials'). The operation groups table is useful but some sections like Indexes and Datasets could be more compact.	2 / 3
Actionability	The skill provides fully executable, copy-paste ready TypeScript code for every operation group — authentication, agents with multiple tool types, connections, deployments, datasets, and indexes. Code examples are concrete with real method signatures and parameters.	3 / 3
Workflow Clarity	The 'Run Agent' section shows a clear multi-step workflow (create conversation → generate response → cleanup), but lacks validation checkpoints. There's no error handling guidance, no verification that agent creation succeeded before running, and no feedback loops for common failure modes like authentication errors or missing deployments.	2 / 3
Progressive Disclosure	The content is a single monolithic file with no references to supporting documents. At ~200+ lines covering 7+ operation groups, the agents section alone is quite long and could benefit from being split out. However, the sections are well-organized with clear headers, making navigation reasonable despite the length.	2 / 3
	Total	9 / 12 Passed

Description

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 the domain (Azure AI Foundry) and lists broad capability areas but lacks concrete action verbs, explicit trigger guidance, and natural user-facing keywords. It reads more like a tagline than a functional skill description, making it difficult for Claude to confidently select this skill over others in a large skill set.

Suggestions

Add a 'Use when...' clause specifying trigger scenarios, e.g., 'Use when the user asks about Azure AI Foundry projects, creating AI agents, managing model deployments, or running evaluations in Azure.'

Replace the high-level noun list with specific concrete actions, e.g., 'Creates and manages AI agents, configures project connections, deploys models, and runs evaluation pipelines in Azure AI Foundry.'

Include natural keyword variations users might say, such as 'Azure AI Studio', 'AI project setup', 'model endpoint', 'azure-ai-projects SDK', or 'AI evaluation runs'.

Dimension	Reasoning	Score
Specificity	Names the domain (Azure AI Foundry) and lists some capabilities (agents, connections, deployments, evaluations), but these are high-level category names rather than concrete actions. No verbs describe what specific operations can be performed.	2 / 3
Completeness	Describes 'what' at a high level but completely lacks any 'Use when...' clause or equivalent trigger guidance. Per the rubric, a missing 'Use when' clause caps completeness at 2, and since the 'what' is also quite vague, this scores a 1.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'Azure AI Foundry', 'agents', 'deployments', and 'evaluations' that users might mention, but misses common variations like 'Azure AI Studio', 'AI project', 'model deployment', or SDK-specific terms users might naturally use.	2 / 3
Distinctiveness Conflict Risk	The mention of 'Azure AI Foundry' provides some distinctiveness, but terms like 'agents', 'deployments', and 'evaluations' are generic enough to overlap with other Azure or AI-related skills. Without clearer scoping, it could conflict with general Azure SDK or AI deployment skills.	2 / 3
	Total	7 / 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: 9431b67

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