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.

60

Quality

71%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/azure-search-documents-dotnet/SKILL.md

The canonical home for this skill is azure-search-documents-dotnet in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

65%Weight 40%Scale 1-5

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

A well-structured, code-rich SDK reference that is highly actionable and mostly concise. It is held back by missing validation feedback loops for destructive/batch operations and by references to bundle files that are not actually present.

Suggestions

Add an explicit validation/verification step after destructive and batch operations (e.g., check `IndexDocumentsAsync` response for `Status == 200`, retry on partial failure) so workflow_clarity can exceed the destructive/batch cap of 3.

Either create the referenced `references/vector-search.md` and `references/semantic-search.md` files or remove the "See references/..." lines and the Reference Files table, so navigation is not broken.

Delete the vague filler "When to Use" line ("This skill is applicable to execute the workflow or actions described in the overview.") and the redundant opening sentence that repeats the description to tighten conciseness.

DimensionReasoningScore

Conciseness

The body is lean and code-heavy with clean section headers and little concept padding, but the intro line repeats the description and the closing "When to Use" section ("This skill is applicable to execute the workflow or actions described in the overview.") is vague filler that could be trimmed.

4 / 5

Actionability

Concrete, copy-paste-ready C# examples cover installation, auth, indexing, document ops, and search patterns, but several snippets reference undefined variables ("embedding", "hotel1"/"hotel2"/"hotel3", "endpoint", "indexName"), leaving minor gaps.

4 / 5

Workflow Clarity

Sections are organized in an implied sequence (install → auth → clients → index → documents → search), but there are no validation checkpoints, and the destructive delete and batch index operations lack any verify/retry feedback loop, capping this at 3 per the rubric.

3 / 5

Progressive Disclosure

References are clearly signaled ("See references/vector-search.md" / "semantic-search.md" plus a Reference Files table), but those referenced files do not exist in any bundle directory, so navigation is broken and a large amount of content remains inline in SKILL.md.

3 / 5

Total

14

/

20

Passed

Description

78%Weight 40%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.

A clear, specific description that names the SDK and its core search modalities with an explicit use clause. Its main weakness is that the 'when' guidance restates the 'what' rather than offering distinct trigger phrases.

DimensionReasoningScore

Specificity

"building search applications with full-text, vector, semantic, and hybrid search" names several concrete capabilities, but stops at one action verb (building) and omits actions like indexing, uploading, or querying, so it is not comprehensive enough for a 5.

4 / 5

Completeness

It states both what (the SDK and its capabilities) and when ("Use for building search applications..."), but the when clause largely restates the what rather than giving distinct explicit trigger phrases, so it is not a 5.

4 / 5

Trigger Term Quality

Natural terms users would say are present ("Azure AI Search", "search applications", "full-text", "vector", "semantic", "hybrid search", ".NET"), but common variations like the legacy name "Azure Cognitive Search" and verbs like "indexing"/"querying" are missing.

4 / 5

Distinctiveness Conflict Risk

The specific SDK name "Azure AI Search SDK for .NET (Azure.Search.Documents)" pins a clear niche with minimal overlap risk against other skills.

5 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 4 missing

Warning

Total

14

/

16

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.