CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-search-documents-dotnet

Azure AI Search SDK for .NET (Azure.Search.Documents). Use for building search applications with full-text, vector, semantic, and hybrid search.

59

Quality

69%

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 ./skills/azure-search-documents-dotnet/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

64%Scale 1-5

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 SDK reference skill with excellent actionable code examples covering the full breadth of Azure AI Search capabilities. Its main weaknesses are the lack of end-to-end workflow sequencing with validation checkpoints (especially for index creation and batch document operations), moderate verbosity in sections like Best Practices and the tautological 'When to Use' section, and unclear progressive disclosure given that referenced files aren't provided and substantial content is duplicated inline.

Suggestions

Add an explicit end-to-end workflow section with validation steps: create index → verify creation → upload documents → check IndexDocumentsResult for errors → run test query → verify results.

Remove the 'When to Use' section (adds no value) and trim 'Best Practices' to only non-obvious guidance that Claude wouldn't already know.

Clarify the boundary between inline content and reference files — either keep vector/semantic search examples minimal inline with a clear pointer to the reference file, or inline everything and remove the references.

DimensionReasoningScore

Conciseness

The skill is reasonably efficient but includes some unnecessary content. The 'Best Practices' section contains advice Claude already knows (e.g., 'batch operations for better throughput', 'return only needed fields'). The 'When to Use' section is a meaningless tautology. The Field Attributes Reference table, while useful, could be trimmed. Overall, there's moderate bloat across ~250 lines.

3 / 5

Actionability

Excellent actionable content throughout. Every section provides copy-paste ready C# code examples covering authentication, index creation, document operations, all search patterns (basic, faceted, vector, semantic, hybrid), autocomplete, and error handling. The code is complete and executable with proper using statements and realistic patterns.

5 / 5

Workflow Clarity

The skill presents individual operations clearly but lacks workflow sequencing. There's no explicit multi-step workflow showing the end-to-end process (create index → upload documents → verify → search). Index creation and document upload are batch/destructive operations that lack validation checkpoints (e.g., verifying index was created successfully before uploading documents, checking IndexDocumentsResult for failures in batch operations).

3 / 5

Progressive Disclosure

References to 'references/vector-search.md' and 'references/semantic-search.md' are mentioned but no bundle files are provided, so we can't verify they exist. The main file inlines substantial content for vector and semantic search while also pointing to reference files, creating ambiguity about what's where. The reference table at the bottom is good structure, but the inline content could be better organized with clearer delineation of what's overview vs. what's in the reference files.

3 / 5

Total

14

/

20

Passed

Description

73%Scale 1-5

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 clearly identifies the specific SDK and platform, making it highly distinctive and unlikely to conflict with other skills. It includes a reasonable 'Use for' clause but could benefit from listing more concrete actions (e.g., creating indexes, uploading documents, running queries) and additional natural trigger terms like 'cognitive search' or 'search index'.

Suggestions

Add concrete actions like 'create and manage search indexes, upload documents, execute queries, configure scoring profiles' to improve specificity.

Include additional trigger terms and synonyms such as 'cognitive search', 'search index', 'indexer', 'Azure search query', 'SearchClient' to improve keyword coverage.

DimensionReasoningScore

Specificity

Names the domain (Azure AI Search SDK for .NET) and lists search types (full-text, vector, semantic, hybrid) but doesn't describe concrete actions like creating indexes, uploading documents, querying, or managing indexers.

3 / 5

Completeness

Has a clear 'what' (Azure AI Search SDK for .NET) and a 'when' clause ('Use for building search applications with full-text, vector, semantic, and hybrid search'). The 'when' could be more explicit with additional trigger scenarios like 'when the user mentions Azure search indexes or search queries'.

4 / 5

Trigger Term Quality

Includes good keywords like 'Azure AI Search', '.NET', 'Azure.Search.Documents', 'full-text', 'vector', 'semantic', 'hybrid search'. Missing some natural terms users might say like 'cognitive search', 'search index', 'indexer', or 'Azure search query'.

4 / 5

Distinctiveness Conflict Risk

Highly distinctive with the specific SDK name 'Azure.Search.Documents', the .NET platform, and the Azure AI Search domain. Very unlikely to conflict with other skills due to the precise technology stack identification.

5 / 5

Total

16

/

20

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
administrakt0r/AI-Agents-Safe-Coding-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.