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.
65
48%
Does it follow best practices?
Impact
96%
2.40xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/antigravity-azure-ai-agents-persistent-dotnet/SKILL.mdQuality
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 domain (Azure AI Agents Persistent SDK for .NET) and lists key SDK concepts, but lacks concrete actions a user would perform and entirely omits trigger guidance for when Claude should select this skill. The terms used are a mix of specific SDK terminology and generic concepts that could overlap with other agent or Azure skills.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about building AI agents with Azure AI Agent Service in .NET, or mentions PersistentAgentsClient, agent threads, or agent runs.'
List concrete actions instead of abstract concepts, e.g., 'Creates and configures AI agents, manages conversation threads, sends and retrieves messages, executes agent runs, and integrates tools like code interpreter and file search.'
Include common user-facing trigger terms and variations such as 'C#', 'Azure OpenAI agents', 'assistant API', 'PersistentAgentsClient', and 'Azure.AI.Projects' to improve keyword coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Azure AI Agents SDK for .NET) and lists some concepts (threads, messages, runs, tools), but these are more like SDK abstractions than concrete user-facing actions. It doesn't describe specific actions like 'create agents', 'manage conversation threads', or 'configure tool integrations'. | 2 / 3 |
Completeness | Describes what the skill covers (SDK for creating/managing AI agents with threads, messages, runs, tools) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also only partially described, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Azure', 'AI Agents', '.NET', 'SDK', 'threads', 'messages', 'runs', and 'tools' which users might mention. However, it misses common variations like 'C#', 'Azure OpenAI', 'assistant API', 'agent orchestration', or 'PersistentAgentsClient'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Azure AI Agents Persistent SDK' and '.NET' provides some distinctiveness, but 'AI agents', 'threads', 'messages', and 'tools' are generic enough to overlap with other agent frameworks or Azure SDK skills. The 'Persistent' qualifier helps but isn't well explained. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
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, highly actionable SDK reference skill with excellent executable code examples covering the full breadth of the Azure AI Agents Persistent SDK. Its main weaknesses are its length (could benefit from splitting tool-specific examples into separate files) and the lack of explicit validation/error recovery steps within multi-step workflows. Some generic best practices and the placeholder 'When to Use' section add unnecessary tokens.
Suggestions
Add explicit error handling and validation checkpoints within the core workflow steps (e.g., check run.Status == RunStatus.Failed after polling, handle file upload failures before vector store creation)
Move detailed tool-specific examples (function calling, file search, Bing grounding, AI Search) into separate referenced files to reduce the main skill's token footprint
Remove the placeholder 'When to Use' section and trim generic best practices that Claude already knows (e.g., 'use async methods', 'use using statements')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly efficient with executable code examples and reference tables, but it's quite long (~300 lines) with some sections that could be consolidated. The 'Best Practices' section contains some generic advice Claude already knows (e.g., 'use async methods', 'use using statements'). The 'When to Use' section is a meaningless placeholder. | 2 / 3 |
Actionability | Excellent actionability with fully executable C# code examples for every major workflow: agent creation, threading, polling, streaming, function calling, file search, Bing grounding, AI Search, and error handling. All examples are copy-paste ready with concrete types and method signatures. | 3 / 3 |
Workflow Clarity | The numbered steps (1-9) provide a clear sequence for the core workflow, and the polling loop includes status checking. However, there are no explicit validation checkpoints or error recovery feedback loops within the multi-step workflows — e.g., no guidance on what to do if agent creation fails, if the run fails, or if file upload fails before proceeding to vector store creation. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and reference tables, but it's monolithic — all tool examples are inline rather than split into separate files. The reference links at the bottom are helpful, but the skill would benefit from moving detailed tool-specific examples (function calling, file search, Bing, AI Search) into separate referenced files to keep the main skill leaner. | 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.
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 | |
- Repository
- boisenoise/skills-collections
- Commit
f1697b6
- 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.