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?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/azure-ai-projects-ts/SKILL.md

Quality

Content

64%Scale 1-3

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. However, it's somewhat monolithic for the breadth of topics covered, lacks validation/error-handling in multi-step workflows, and includes some generic boilerplate sections ('When to Use', 'Limitations') that waste tokens without adding value.

Suggestions

Add error handling and validation checkpoints to multi-step workflows like agent creation and execution (e.g., check agent creation succeeded before running, handle function tool call responses).

Remove the generic 'When to Use' and 'Limitations' sections—they are boilerplate that adds no skill-specific value.

Consider splitting detailed tool configurations (code interpreter, file search, MCP, etc.) into a separate AGENT_TOOLS.md reference file to reduce the main file's length and improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient with good 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 ('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. Import statements, environment variables, and concrete API calls are all specified.	3 / 3
Workflow Clarity	The 'Run Agent' section shows a multi-step workflow (create conversation → generate response → cleanup) which is clear, but lacks validation checkpoints—there's no error handling, no verification that the agent was created successfully before running, and no feedback loops for failure cases in any of the multi-step operations.	2 / 3
Progressive Disclosure	The content is well-structured with clear headers and a logical progression from setup to specific operations, but it's a monolithic file with no references to supporting documents. Given the breadth of coverage (agents, connections, deployments, datasets, indexes, evaluators), detailed tool configurations and advanced patterns could be split into separate files.	2 / 3
	Total	9 / 12 Passed

Description

32%Scale 1-3

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 and a 'Use when...' clause. It reads more like a tagline than a functional description that would help Claude reliably select this skill from a large pool. The terms used are somewhat distinctive due to the Azure AI Foundry branding but remain too high-level to prevent overlap with similar cloud/AI skills.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about Azure AI Foundry projects, creating AI agents, managing Azure AI connections, deploying models, or running evaluations.'

Replace the noun list with specific action verbs, e.g., 'Creates and manages AI agents, configures project connections, deploys models, and runs evaluation pipelines in Azure AI Foundry.'

Include common user-facing terms and file/package references like 'azure-ai-projects SDK', 'Azure AI Studio', or 'AI model evaluation' to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (Azure AI Foundry) and lists some capabilities (agents, connections, deployments, evaluations), but these are fairly high-level categories rather than concrete actions. No verbs describe what specific operations are performed.	2 / 3
Completeness	Provides a partial 'what' (high-level SDK for Azure AI Foundry projects) but completely lacks a 'when' clause. There is no 'Use when...' or equivalent trigger guidance, which per the rubric should cap completeness at 2, and since the 'what' is also weak, this scores a 1.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'Azure AI Foundry', 'agents', 'connections', 'deployments', and 'evaluations' that users might mention, but misses common variations like 'Azure AI', '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 'agents', 'connections', 'deployments', and 'evaluations' are generic enough terms that could overlap with other Azure or cloud-related 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: popey/claude-code-skills
Path: skills/azure-ai-projects-ts/SKILL.md
Commit: a5a6601

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