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.

55

Quality

62%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/azure-ai-openai-dotnet/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

64%

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

This is a solid API reference skill with excellent actionability — nearly every section has complete, executable C# code examples covering the full breadth of Azure OpenAI SDK capabilities. Its main weaknesses are its monolithic length (~400 lines that could benefit from progressive disclosure into sub-files) and some unnecessary content like boilerplate sections and generic best practices that Claude already knows. The function calling workflow is also incomplete, missing the critical step of sending tool results back to the model.

Suggestions

Split detailed feature sections (structured outputs, function calling, RAG, audio) into separate referenced files, keeping SKILL.md as a concise overview with quick-start examples and navigation links.

Complete the function calling workflow by showing the full loop: initial call → detect tool calls → execute function → send ToolChatMessage back → get final response.

Remove the generic 'When to Use' and 'Limitations' boilerplate sections and trim the best practices to only Azure OpenAI-specific guidance Claude wouldn't already know.

DimensionReasoningScore

Conciseness

The skill is fairly comprehensive but includes some unnecessary elements like the 'When to Use' and 'Limitations' boilerplate sections that add no value, the 'Related SDKs' table restates obvious information, and the Key Types Reference table explains types Claude could infer. The best practices section contains generic advice Claude already knows. However, the code examples themselves are lean and well-structured.

2 / 3

Actionability

Every section provides fully executable, copy-paste ready C# code examples with proper using statements, concrete method calls, and realistic parameters. The examples cover all major scenarios (chat, streaming, structured outputs, embeddings, images, audio, function calling, error handling) with complete, runnable code.

3 / 3

Workflow Clarity

The client hierarchy diagram and individual feature sections are clear, but there's no explicit workflow for multi-step processes like function calling (the tool call loop is incomplete — it shows detecting tool calls but not sending results back to the model for a final response). The error handling section shows retry but lacks a proper feedback loop pattern. For a reference-style skill this is acceptable but not exemplary.

2 / 3

Progressive Disclosure

The content is a monolithic ~400-line file with no bundle files to offload detailed content. The structured outputs, function calling, and RAG sections could be split into separate reference files. The Reference Links table at the end provides external navigation, but the skill itself would benefit from splitting into a concise overview with references to detailed sub-files for each capability.

2 / 3

Total

9

/

12

Passed

Description

60%

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 does a good job listing specific capabilities and identifying the domain (Azure OpenAI SDK for .NET), but it falls short on explicit trigger guidance and natural user keywords. It would benefit from a 'Use when...' clause with situational triggers and additional natural terms users might use like 'C#', 'GPT', or '.NET'.

Suggestions

Add an explicit 'Use when...' clause describing trigger scenarios, e.g., 'Use when the user is building .NET/C# applications that call Azure OpenAI or OpenAI APIs.'

Include additional natural trigger terms users would say, such as 'C#', '.NET', 'GPT', 'NuGet', 'OpenAI API', 'DALL-E', 'Whisper' to improve keyword coverage and distinctiveness.

DimensionReasoningScore

Specificity

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

3 / 3

Completeness

Clearly answers 'what' (client library for Azure OpenAI/.NET with specific capabilities) and has a partial 'when' via 'Use for...' but lacks an explicit 'Use when...' clause describing trigger scenarios (e.g., 'when the user is building .NET applications that integrate with Azure OpenAI services'). The 'Use for' lists capabilities rather than situational triggers.

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 missing file extensions or SDK package names users might reference.

2 / 3

Distinctiveness Conflict Risk

The combination of Azure OpenAI + .NET + SDK is fairly distinctive, but could overlap with general OpenAI skills, general Azure SDK skills, or Python-based OpenAI SDK skills. Specifying '.NET' or 'C#' more prominently in trigger terms would help differentiate.

2 / 3

Total

9

/

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.

Validation10 / 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
sickn33/antigravity-awesome-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.