CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-ai-projects-dotnet

Azure AI Projects SDK for .NET. High-level client for Azure AI Foundry projects including agents, connections, datasets, deployments, evaluations, and indexes.

57

Quality

66%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/antigravity-azure-ai-projects-dotnet/SKILL.md
SKILL.md
Quality
Evals
Security

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, highly actionable SDK reference skill with executable code examples covering all major Azure AI Projects operations. Its main weaknesses are its monolithic structure (everything inline rather than using progressive disclosure) and the lack of integrated validation/error-recovery steps within multi-step workflows. Some boilerplate sections and general .NET advice slightly reduce token efficiency.

Suggestions

Integrate error handling and validation checkpoints directly into multi-step workflows (e.g., check run.Status for failure states, validate dataset upload success) rather than having a separate generic error handling section.

Split detailed workflow code examples (datasets, indexes, evaluations, etc.) into separate referenced files, keeping SKILL.md as a concise overview with the client hierarchy, authentication, and links to detailed guides.

Remove the boilerplate 'When to Use' and 'Limitations' sections, and trim 'Best Practices' to only non-obvious, SDK-specific guidance.

DimensionReasoningScore

Conciseness

The skill is fairly comprehensive but includes some unnecessary sections like 'When to Use' and 'Limitations' which are boilerplate filler. The 'Best Practices' section is useful but some points are general .NET advice Claude already knows (e.g., use async methods for I/O). The client hierarchy diagram and reference tables are efficient, but the overall document is long (~300 lines) and could be tightened.

2 / 3

Actionability

Every workflow section includes fully executable, copy-paste ready C# code with proper using statements, concrete method calls, and realistic parameters. The code covers the full lifecycle (create, use, cleanup) for agents, datasets, indexes, evaluations, and connections.

3 / 3

Workflow Clarity

The agent workflow includes a polling loop and cleanup steps, which is good. However, there are no explicit validation checkpoints or error recovery feedback loops in the multi-step workflows (e.g., dataset upload, index creation, evaluation). The error handling section is separate and generic rather than integrated into workflows where failures are likely.

2 / 3

Progressive Disclosure

The document is a monolithic wall of content with all 8 workflows inline. For a skill this comprehensive, the detailed code examples for datasets, indexes, evaluations, etc. could be split into separate reference files with the SKILL.md serving as an overview with links. The reference links at the bottom are helpful but the body itself is not well-layered.

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 strong in specificity and distinctiveness, clearly identifying the SDK, platform, and concrete capabilities. However, it lacks an explicit 'Use when...' clause, which is critical for Claude to know when to select this skill. Adding natural trigger terms and user-facing language would improve selection accuracy.

Suggestions

Add a 'Use when...' clause, e.g., 'Use when the user needs to interact with Azure AI Foundry projects in C#/.NET, including creating agents, managing deployments, or running evaluations.'

Include common user-facing trigger terms like 'C#', 'Azure.AI.Projects', 'NuGet package', or 'AI Foundry SDK' that users might naturally mention.

DimensionReasoningScore

Specificity

Lists multiple specific concrete capabilities: agents, connections, datasets, deployments, evaluations, and indexes. Also specifies the SDK name, platform (.NET), and that it's a high-level client for Azure AI Foundry projects.

3 / 3

Completeness

Clearly answers 'what does this do' (high-level client for Azure AI Foundry projects with specific sub-capabilities), but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 2 per the rubric.

2 / 3

Trigger Term Quality

Includes relevant keywords like 'Azure AI', '.NET', 'agents', 'deployments', 'evaluations', but misses common user variations like 'C#', 'NuGet', 'Azure.AI.Projects', or mentioning specific use cases users might describe naturally.

2 / 3

Distinctiveness Conflict Risk

Very specific niche: Azure AI Projects SDK for .NET is a distinct, well-scoped domain. The combination of 'Azure AI Foundry', '.NET', and the specific feature list (agents, connections, datasets, etc.) makes it highly unlikely to conflict with other skills.

3 / 3

Total

10

/

12

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
boisenoise/skills-collections
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.