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

67%

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-claude/skills/azure-ai-projects-dotnet/SKILL.md

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 content is highly actionable with comprehensive executable examples, but it is monolithic (no reference files), includes time-sensitive version info and filler prose, and its destructive workflows lack validation checkpoints.

Suggestions

Add explicit validation steps before destructive calls (e.g. confirm a dataset/index exists and verify the target name before Delete), creating a validate→confirm→delete feedback loop to lift workflow clarity.

Move version-sensitive content into a clearly labeled 'Versions / deprecation' section or a separate reference file, and replace the vague "When to Use" line with concrete trigger guidance.

Split the long document into one-level-deep reference files (e.g. agents.md, datasets.md, evaluations.md) referenced from a concise overview in SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is largely lean and code-first with minimal prose, but it carries time-sensitive version numbers ("GA v1.1.0, Preview v1.2.0-beta.5") outside any 'old patterns'/'deprecated' section and a filler "When to Use" line ("This skill is applicable to execute the workflow or actions described in the overview."), which the rubric penalizes.	3 / 5
Actionability	It provides eight complete, copy-paste-ready C# code blocks plus install commands, env vars, and auth setup, covering the common cases with executable guidance.	5 / 5
Workflow Clarity	Workflow 1 shows a clear create→run→poll→cleanup sequence, but destructive operations (deleting datasets, indexes, agents) lack validation/verification checkpoints, so per the rubric cap for destructive/batch workflows without validation, workflow clarity cannot exceed 3.	3 / 5
Progressive Disclosure	The body is a well-headered but ~340-line monolithic document with no bundle/reference files; content such as full workflow examples and type/tool tables is inlined that could live in separate reference files, matching the 'some structure but content that should be separate is inline' anchor.	3 / 5
	Total	14 / 20 Passed

Description

70%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 is specific, well-targeted, and distinct, but it only answers "what" — it lacks an explicit "when to use" trigger clause, which caps its completeness.

Suggestions

Add an explicit 'Use when...' clause naming the natural triggers, e.g. 'Use when working with Azure AI Foundry projects in .NET, or when the user mentions Azure AI Projects, agents, deployments, or evaluations in C#'.

Include common synonyms/package-name variants users might say (e.g. 'Azure.AI.Projects NuGet package', 'AI Foundry SDK') to broaden trigger-term coverage.

Reframe the capability list with verbs (e.g. 'create and manage agents, connections, datasets, deployments, evaluations, and indexes') to lift specificity from concrete nouns to concrete actions.

Dimension	Reasoning	Score
Specificity	The description enumerates several concrete capability areas ("agents, connections, datasets, deployments, evaluations, and indexes"), matching the anchor for listing several specific actions, though it names resource nouns rather than verbs, keeping it below a 5.	4 / 5
Completeness	It clearly states what the skill does ("High-level client for Azure AI Foundry projects...") but provides no explicit "Use when..." trigger guidance, so per the rubric a missing trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	It includes strong domain keywords a user would naturally say ("Azure AI Projects SDK", "Azure AI Foundry", ".NET", "agents", "deployments"), giving good keyword coverage, but it lacks synonyms or file/package-name variants that would push it to 5.	4 / 5
Distinctiveness Conflict Risk	The combination "Azure AI Projects SDK for .NET" / "Azure AI Foundry" carves a clear, specific niche with distinct triggers and minimal overlap with other skills.	5 / 5
	Total	16 / 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-claude/skills/azure-ai-projects-dotnet/SKILL.md
Commit: 57c135b

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.