azure-ai-openai-dotnet

Azure OpenAI SDK for .NET. Client library for Azure OpenAI and OpenAI services. Use for chat completions, embeddings, image generation, audio transcription, and assistants.

1.43x

Quality

81%

Does it follow best practices?

Impact

92%

1.43x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

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

A highly actionable, code-rich SDK reference that is lean and well-organized by feature. Its main weakness is structure: everything lives inline in one long file with no progressive disclosure to supporting reference files, and the closing "When to Use" is vague boilerplate.

Suggestions

Move the Key Types Reference, Related SDKs, and Reference Links tables into a separate references file (e.g., references/types.md) and link to it from SKILL.md, keeping the body as a quick-start overview.

Replace the boilerplate "When to Use" line with concrete guidance on when this skill applies versus the plain OpenAI SDK and other Azure skills.

Move the version number into a clearly marked, easily-updatable spot (or a version note) so time-sensitive detail does not pad the overview.

Dimension	Reasoning	Score
Conciseness	The body is lean and dominated by executable code with minimal prose, never explaining concepts Claude already knows; the time-sensitive "Current Version: 2.1.0 (stable)" line and the somewhat redundant Key Types / Related SDKs tables are minor trimmable instances that keep it just below a 5.	4 / 5
Actionability	Every section provides complete, copy-paste-ready C# covering the common cases — chat, streaming, embeddings, image generation, audio, function calling, structured outputs, and RAG — matching the fully executable anchor.	5 / 5
Workflow Clarity	Each feature section follows a clear client→operation sequence and the skill is not a destructive/batch workflow so the validation cap does not apply; the boilerplate "When to Use" line ("applicable to execute the workflow or actions described in the overview") is a minor gap.	4 / 5
Progressive Disclosure	There are no bundle files (references/, scripts/, assets/ are absent) and the SKILL.md is a ~460-line monolith with the Key Types Reference, Related SDKs, and Reference Links tables all inlined; section headers give structure, but reference material that would benefit from being split into separate files is not, and no external references are signaled.	3 / 5
	Total	16 / 20 Passed

Description

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

A strong, specific description that names the domain and lists concrete capabilities with an explicit "Use for" trigger clause. It could be improved by adding natural synonyms and situational trigger phrasing rather than a capability list.

Suggestions

Add situational "Use when..." phrasing (e.g., "Use when integrating Azure OpenAI into a .NET app for chat, embeddings, or audio") so the "when" is user-situation-based rather than capability-based.

Include natural synonyms and tokens users actually type (e.g., "GPT-4", "DALL-E", "Whisper", ".NET", "C#") to broaden trigger coverage.

Consider mentioning the OpenAI compatibility angle more explicitly to distinguish from the plain OpenAI SDK skill.

Dimension	Reasoning	Score
Specificity	The description enumerates multiple concrete capabilities — "chat completions, embeddings, image generation, audio transcription, and assistants" — giving comprehensive coverage of the SDK's surface, matching the anchor for listing multiple specific concrete actions.	5 / 5
Completeness	It answers "what" ("Client library for Azure OpenAI and OpenAI services") and provides an explicit "Use for" trigger listing concrete tasks, but the "when" is phrased as a capability list rather than user situations, keeping it just below the most explicit anchor.	4 / 5
Trigger Term Quality	It uses good technical keywords a .NET developer would name ("chat completions", "embeddings", "image generation", "audio transcription", "assistants"), but lacks common synonyms or file/extension variants that would lift it to a 5.	4 / 5
Distinctiveness Conflict Risk	Scoping to "Azure OpenAI SDK for .NET" carves a clear niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	18 / 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-openai-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.