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.

1.81x

Quality

61%

Does it follow best practices?

Impact

100%

1.81x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/azure-ai-projects-dotnet/SKILL.md

The canonical home for this skill is azure-ai-projects-dotnet in sickn33/agentic-awesome-skills

Quality

Content

65%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.

The body is highly actionable with comprehensive executable C# examples and clear sectioning, but it is over-long, inlines reference material that belongs in separate files, and lacks validation checkpoints around its destructive delete operations.

Suggestions

Add explicit validation/verification before destructive calls (e.g., confirm an agent/thread/index exists and is safe to delete, and verify deletion succeeded) so workflow clarity is not capped at 3.

Move the bulk reference tables (Key Types, Available Agent Tools, Related SDKs, Reference Links) into one-level-deep reference files under references/ and link to them from SKILL.md to improve progressive disclosure and token efficiency.

Relocate time-sensitive version numbers to a clearly marked 'Current versions' note or a separate changelog-style section so stale data does not bloat the core body.

Dimension	Reasoning	Score
Conciseness	The body is dense and reference-like with minimal concept over-explanation, but it is long (~340 lines) and embeds time-sensitive version numbers ('GA v1.1.0, Preview v1.2.0-beta.5') outside any deprecated/old-patterns section, which the guidelines penalize.	3 / 5
Actionability	Provides fully executable, copy-paste-ready C# across eight numbered workflows plus the Azure OpenAI chat-client path, covering the common cases with concrete imports, clients, and method calls.	5 / 5
Workflow Clarity	Workflows are clearly numbered and the persistent-agent flow includes a run-polling checkpoint, but destructive delete operations (DeleteAgent, DeleteThread, dataset/index Delete) lack explicit validation/verification steps, capping workflow clarity at 3 per the destructive-operations guideline.	3 / 5
Progressive Disclosure	Sections are well-organized, but no bundle files exist and the bulk reference material (Key Types, Available Agent Tools, Related SDKs, Reference Links) is inlined into a single >50-line SKILL.md rather than split into one-level-deep reference files.	3 / 5
	Total	14 / 20 Passed

Description

58%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.

The description clearly conveys what the skill covers and is well-scoped to a distinct niche, but it omits any explicit 'when to use' trigger guidance and relies on technical jargon over natural user phrasing.

Suggestions

Add a 'Use when...' clause naming natural trigger phrases, e.g. 'Use when working with the Azure AI Projects SDK for .NET, or when the user asks about Azure AI Foundry agents, connections, datasets, deployments, evaluations, or indexes in .NET.'

Soften the jargon by including synonyms a user might actually say (e.g., 'Azure AI Foundry .NET client', 'manage Foundry project resources').

Make the capability list read as concrete operations rather than a noun list (e.g., 'create and manage agents, connections, datasets, deployments, evaluations, and indexes').

Dimension	Reasoning	Score
Specificity	Names the domain ('Azure AI Projects SDK for .NET') and enumerates six concrete capability areas ('agents, connections, datasets, deployments, evaluations, and indexes'), giving comprehensive but slightly generic action coverage rather than discrete operations.	4 / 5
Completeness	The 'what' is clearly stated ('High-level client for Azure AI Foundry projects including...'), but there is no 'when' / 'Use when...' trigger clause, which the guidelines cap at 3.	3 / 5
Trigger Term Quality	Contains relevant technical keywords ('Azure AI Foundry', '.NET', 'agents') a practitioner would say, but misses natural variations/synonyms and lacks any 'Use when' phrasing that surfaces how a user would request this skill.	3 / 5
Distinctiveness Conflict Risk	Clearly scoped to the Azure AI Projects .NET SDK with a distinct niche, with only minor overlap risk against a possible Python/non-.NET variant of the same SDK.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/azure-ai-projects-dotnet/SKILL.md
Commit: debb2ec

Reviewed: 1 day 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.