CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

57

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/antigravity-bundle-azure-ai-cloud/skills/azure-ai-openai-dotnet/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

64%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a comprehensive, highly actionable SDK reference with excellent executable code examples covering all major Azure OpenAI features. Its main weaknesses are its length (could benefit from splitting advanced topics into separate files) and some unnecessary boilerplate content. The function calling example is incomplete as it doesn't show the full tool-use round-trip pattern.

Suggestions

Complete the function calling workflow by showing how to send tool results back to the model (ToolChatMessage) and get the final response—this is a critical multi-step pattern that's currently truncated.

Split advanced topics (structured outputs, RAG integration, function calling, audio) into separate referenced files to reduce the main SKILL.md to a concise overview with quick-start examples.

Remove the boilerplate 'When to Use' and 'Limitations' sections and the 'Related SDKs' table—these add little value for Claude.

DimensionReasoningScore

Conciseness

The skill is largely efficient with executable code examples, but includes some unnecessary content like the 'When to Use' and 'Limitations' boilerplate sections, the 'Related SDKs' table (Claude knows these), and the best practices list contains advice Claude already knows (e.g., 'reuse client instances', 'handle rate limits'). The Key Types Reference table is borderline—useful as a quick lookup but adds significant length.

2 / 3

Actionability

Nearly every section provides fully executable, copy-paste ready C# code examples covering authentication, chat completions (sync, async, streaming), structured outputs, embeddings, image generation, audio, function calling, and error handling. The code is complete with proper using statements and realistic patterns.

3 / 3

Workflow Clarity

The client hierarchy diagram clearly shows the relationship between clients, and individual code examples are well-sequenced. However, the function calling workflow lacks the critical feedback loop of sending tool results back to the model for a final response—it only shows detecting tool calls but not completing the round-trip. The error handling section shows retry but without a proper retry loop pattern.

2 / 3

Progressive Disclosure

The content is a monolithic file with no bundle files to offload detailed content. The Reference Links table at the end provides external references, but the inline content is very long (~350+ lines) with sections like structured outputs, RAG integration, and function calling that could be split into separate files. The organization within the file is good with clear section headers, but the sheer volume in a single file hurts discoverability.

2 / 3

Total

9

/

12

Passed

Description

67%Scale 1-3

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 reasonably strong with good specificity in listing concrete capabilities and a clear niche that distinguishes it from other skills. However, it would benefit from an explicit 'Use when...' clause with trigger scenarios and additional natural language terms users might employ when seeking this skill, such as 'C#', 'GPT', or '.NET OpenAI integration'.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user needs to integrate OpenAI or Azure OpenAI services in a .NET/C# application.'

Include additional natural trigger terms users might say, such as 'C#', '.NET', 'GPT', 'NuGet', 'OpenAI API', 'DALL-E', or 'Whisper' to improve discoverability.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: chat completions, embeddings, image generation, audio transcription, and assistants. These are well-defined capabilities.

3 / 3

Completeness

Clearly answers 'what' (client library for Azure OpenAI/OpenAI services with specific capabilities) and has a partial 'when' via 'Use for...', but lacks an explicit 'Use when...' clause describing trigger scenarios (e.g., 'Use when the user asks about integrating OpenAI in .NET applications or needs help with Azure OpenAI SDK code').

2 / 3

Trigger Term Quality

Includes relevant terms like 'Azure OpenAI', 'chat completions', 'embeddings', 'image generation', 'audio transcription', and 'assistants', but misses common user variations like 'GPT', '.NET', 'C#', 'NuGet', 'OpenAI API', or 'text-to-speech'. Also lacks file extensions or SDK-specific terms users might search for.

2 / 3

Distinctiveness Conflict Risk

The combination of 'Azure OpenAI SDK for .NET' creates a very clear niche that is unlikely to conflict with other skills. It specifies both the platform (Azure/OpenAI) and the technology (.NET), making it highly distinguishable.

3 / 3

Total

10

/

12

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
popey/claude-code-skills
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.