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.

Install with Tessl CLI

npx tessl i github:boisenoise/skills-collections --skill azure-ai-openai-dotnet

What are skills?

1.43x

Quality

73%

Does it follow best practices?

Impact

92%

1.43x

Average score across 3 eval scenarios

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/antigravity-azure-ai-openai-dotnet/SKILL.md

SKILL.md

Review

Evals

Discovery

67%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description effectively communicates specific capabilities and has a clear niche targeting Azure OpenAI SDK for .NET developers. However, it lacks explicit trigger guidance ('Use when...') and could benefit from more natural user-facing keywords beyond technical API terminology.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user is building .NET applications with Azure OpenAI, implementing GPT chat features, or integrating OpenAI services in C# projects.'

Include more natural trigger terms users might say: 'GPT', 'C#', 'AI integration', 'generate images with DALL-E', 'speech-to-text', 'Whisper'.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'chat completions, embeddings, image generation, audio transcription, and assistants' - these are distinct, actionable capabilities.	3 / 3
Completeness	Clearly answers 'what' with specific capabilities, but lacks an explicit 'Use when...' clause with trigger guidance. The 'Use for' phrase describes capabilities rather than when to select this skill.	2 / 3
Trigger Term Quality	Includes relevant keywords like 'Azure OpenAI', 'OpenAI', '.NET', 'chat completions', 'embeddings', but missing common user variations like 'GPT', 'AI chat', 'generate images', 'transcribe audio', or file extensions like '.cs'.	2 / 3
Distinctiveness Conflict Risk	Clearly scoped to Azure OpenAI SDK for .NET specifically - the combination of 'Azure', 'OpenAI', and '.NET' creates a distinct niche unlikely to conflict with generic AI or document skills.	3 / 3
	Total	10 / 12 Passed

Implementation

79%

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

This is a high-quality SDK reference skill with excellent actionability and conciseness. All code examples are executable and well-structured. The main weaknesses are the lack of explicit validation workflows for complex operations and the monolithic structure that could benefit from splitting advanced topics into separate files.

Suggestions

Add explicit validation steps to the Function Calling section (e.g., validate arguments before execution, handle missing required parameters, verify tool call results)

Consider splitting advanced topics (RAG integration, Function Calling, Reasoning Models) into separate reference files with clear navigation links in the main skill

Dimension	Reasoning	Score
Conciseness	The skill is lean and efficient, providing executable code examples without explaining basic concepts Claude already knows. Every section serves a purpose with no padding or unnecessary context.	3 / 3
Actionability	All code examples are fully executable and copy-paste ready with proper using statements, complete method calls, and realistic patterns. Covers authentication, chat, streaming, embeddings, images, audio, and function calling with concrete implementations.	3 / 3
Workflow Clarity	While individual operations are clear, the skill lacks explicit validation checkpoints or feedback loops for multi-step processes like tool calling or RAG integration. The error handling section is good but not integrated into workflows.	2 / 3
Progressive Disclosure	Content is well-organized with clear sections and a reference table, but the skill is monolithic (~400 lines) with all content inline. Advanced topics like RAG integration and function calling could be split into separate reference files.	2 / 3
	Total	10 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Reviewed: about 19 hours 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.