azure-ai-agents-persistent-dotnet
Azure AI Agents Persistent SDK for .NET. Low-level SDK for creating and managing AI agents with threads, messages, runs, and tools.
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill azure-ai-agents-persistent-dotnet67
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
32%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 identifies the technology stack (Azure AI Agents, .NET) and mentions key concepts (threads, messages, runs, tools), but lacks explicit trigger guidance for when to use this skill. The technical terminology may not match how users naturally request help, and the absence of a 'Use when...' clause significantly limits Claude's ability to select this skill appropriately.
Suggestions
Add an explicit 'Use when...' clause with trigger scenarios like 'Use when building conversational AI agents on Azure, working with the Azure.AI.Projects SDK, or managing agent threads and message history in .NET applications.'
Include more natural language variations users might say, such as 'chatbot development', 'conversation management', 'Azure OpenAI agents', or 'assistant API'.
List more specific concrete actions like 'create persistent conversation threads', 'manage message history', 'configure agent tools', 'handle run execution and polling'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Azure AI Agents SDK for .NET) and mentions some actions (creating and managing AI agents with threads, messages, runs, and tools), but doesn't list comprehensive concrete actions like 'create threads', 'send messages', 'execute runs'. | 2 / 3 |
Completeness | Describes what it does (SDK for creating/managing AI agents) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant technical terms like 'Azure', 'AI Agents', '.NET', 'SDK', 'threads', 'messages', 'runs', 'tools', but these are more technical jargon than natural user language. Missing common variations users might say like 'chatbot', 'assistant', 'conversation'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Azure', '.NET', and 'Persistent SDK' provides some distinctiveness, but 'AI agents' is generic and could overlap with other agent-related skills. The 'Low-level SDK' qualifier helps but isn't strongly differentiating. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
87%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. The code examples are complete and executable, covering all major use cases from basic agent creation to advanced features like function calling and file search. The main weakness is that error handling and validation are separated from the core workflow rather than integrated as checkpoints.
Suggestions
Integrate error handling into the polling workflow (step 3) to show how to handle RunStatus.Failed and RunStatus.Cancelled inline rather than as a separate section
Add a validation checkpoint after agent creation to verify the agent was created successfully before proceeding to thread creation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content 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 explanations. | 3 / 3 |
Actionability | All code examples are fully executable and copy-paste ready with proper imports, async/await patterns, and complete method calls. The examples cover the full workflow from authentication through cleanup. | 3 / 3 |
Workflow Clarity | The numbered workflow steps are clear and sequential, but validation/error handling is only shown as a separate section rather than integrated into the workflow. The polling loop lacks explicit guidance on handling failed states inline. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, reference tables for quick lookup, and external links to detailed documentation. The structure allows quick scanning while providing depth where needed. | 3 / 3 |
Total | 11 / 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
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- 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.