CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

87

1.43x
Quality

86%

Does it follow best practices?

Impact

92%

1.43x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

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

SKILL.md
Quality
Evals
Security

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-dense SDK reference with executable examples across every capability area and sensible ordering from setup to advanced usage. Its weaknesses are inline bloat for a file this size (no progressive disclosure into reference files), a small amount of redundant or vacuous material, and the absence of validation checkpoints in its workflows.

Suggestions

Split long-tail sections (Azure AI Search RAG integration, Reasoning Models, Key Types Reference, Reference Links) into files under references/ and link them from a lean overview in SKILL.md, keeping only quick-start auth and chat examples inline.

Remove the vacuous 'When to Use' section ('This skill is applicable to execute the workflow or actions described in the overview') and the redundant Key Types table, which restates types already demonstrated in code.

Add a brief pre-flight validation step (e.g., confirm the deployment name exists and the endpoint resolves before making the first API call) to give the setup workflow an explicit checkpoint.

DimensionReasoningScore

Conciseness

The body is code-first with almost no explanation of concepts Claude already knows, but the "Key Types Reference" table restates types shown in the examples, "Current Version: 2.1.0" is time-sensitive detail, and the closing "This skill is applicable to execute the workflow or actions described in the overview" is vacuous filler that could be trimmed.

4 / 5

Actionability

Examples are fully executable and copy-paste ready — "dotnet add package Azure.AI.OpenAI", both auth flows, streaming via "CompleteChatStreamingAsync", structured outputs with a complete JSON schema, tool calls, and catch-based error handling — covering the common cases comprehensively.

5 / 5

Workflow Clarity

The install → environment variables → authentication → API usage sequence is clearly ordered, and the error-handling section shows a 429 retry loop as a feedback mechanism, but there are no explicit validation checkpoints (e.g., verifying a deployment exists before calling).

4 / 5

Progressive Disclosure

The skill is a single ~460-line file with no bundle files at all; content that plausibly belongs in separate references — "Azure AI Search Integration (RAG)", "Reasoning Models", the Key Types table, and the Reference Links — is inlined, fitting the anchor where content that should be separate is inline despite good section headers.

3 / 5

Total

16

/

20

Passed

Description

88%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 description that names the domain, platform, and five concrete capability areas with an explicit 'Use for' trigger clause. The main gaps are missing common synonyms (DALL-E, Whisper, TTS, C#) that would improve trigger matching and sharpen distinctiveness against adjacent OpenAI skills.

DimensionReasoningScore

Specificity

The description lists five concrete capability areas — "chat completions, embeddings, image generation, audio transcription, and assistants" — giving comprehensive coverage of the SDK's action surface, matching the multiple-specific-actions anchor rather than the 4-anchor's three-actions-with-gaps example.

5 / 5

Completeness

"Client library for Azure OpenAI and OpenAI services" clearly answers what the skill does, and "Use for chat completions, embeddings, image generation, audio transcription, and assistants" explicitly states when to use it with concrete task trigger phrases, so the missing-trigger cap does not apply.

5 / 5

Trigger Term Quality

Terms like "chat completions", "embeddings", "image generation", and "audio transcription" are natural phrases users would say, but common synonyms such as "DALL-E", "Whisper", "TTS", "C#", or "dotnet" are absent, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

"Azure OpenAI SDK for .NET" carves out a clear niche, but the phrase "for Azure OpenAI and OpenAI services" and generic terms like "chat completions" create minor overlap risk with a plain OpenAI or non-.NET skill.

4 / 5

Total

18

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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

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.