azure-ai-projects-ts

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

Quality

59%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

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

The canonical home for this skill is azure-ai-projects-ts 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 content is a lean, mostly executable reference with strong code coverage of the SDK's common operations, but it inlines what could be split into reference files and provides no validation checkpoints around its destructive delete operations.

Suggestions

Add verification steps before destructive calls (e.g. confirm an agent/conversation/dataset exists before deleting it) to lift workflow clarity above the cap.

Move the exhaustive tool-variant and key-type API reference into a separate reference file linked from SKILL.md, keeping only a quick-start overview inline.

Define or note the placeholders used in examples (vectorStoreId, connectionId) so snippets are fully copy-paste runnable.

Dimension	Reasoning	Score
Conciseness	The body is predominantly executable code with brief section headers and inline comments, with only minor repetition (the overview line restates the description), fitting 'efficient; minor instances of over-explanation that could be trimmed'.	4 / 5
Actionability	Provides concrete, copy-paste-ready TypeScript across agents, tools, connections, deployments, datasets, and indexes, with only minor placeholder gaps (e.g. undefined vectorStoreId/connectionId), matching 'mostly executable guidance; concrete code with minor gaps'.	4 / 5
Workflow Clarity	A partial sequence exists (e.g. the 'Run Agent' create-conversation -> respond -> cleanup flow), but there are no validation checkpoints, and destructive operations (deleteVersion, conversations.delete, datasets.delete) lack verification, which caps workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	The body is well-sectioned but ~290 lines of API reference (operation groups, every tool variant, key types) are inlined in SKILL.md with no references split into separate files and no bundle files present, fitting 'some structure but content that should be separate is inline'.	3 / 5
	Total	14 / 20 Passed

Description

53%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 states what the SDK covers and carves out a distinct Azure AI Foundry niche, but it omits any explicit 'when to use' guidance and relies on feature-area nouns rather than concrete actions or natural trigger phrases.

Suggestions

Add a 'Use when...' clause naming concrete trigger situations, e.g. 'Use when working with Azure AI Foundry agents, project connections, model deployments, or evaluations.'

Reframe feature areas as concrete actions ('create and manage agents, list connections, deploy models, run evaluations') to raise specificity.

Include natural synonyms and surface terms users actually say (e.g. 'Azure AI', 'Foundry', 'AI agent', 'model deployment') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('Azure AI Foundry projects') and lists several feature areas ('agents, connections, deployments, and evaluations'), but these are capability categories rather than concrete action verbs, fitting the 'names domain and 1-2 concrete actions' anchor more than the 'several specific actions' anchor.	3 / 5
Completeness	Provides a clear 'what' (a high-level SDK for Azure AI Foundry with named feature areas) but no 'Use when...' or equivalent explicit trigger guidance for 'when', so completeness is capped at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Includes relevant domain terms ('Azure AI Foundry', 'agents', 'deployments', 'evaluations') a user might say, but misses common natural variations and synonyms, landing at 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	Targets a specific niche (Azure AI Foundry SDK) that is mostly distinct from other skills with only minor overlap risk, but the absence of explicit trigger phrases keeps it just below the 'clear niche with distinct triggers' anchor.	4 / 5
	Total	13 / 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-ts/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.