Name: azure-resource-manager-cosmosdb-dotnet
Rating: 48.8 (1 reviews)
Author: administrakt0r

Blog Docs Log in Get started

azure-resource-manager-cosmosdb-dotnet

Azure Resource Manager SDK for Cosmos DB in .NET.

Quality

53%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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-resource-manager-cosmosdb-dotnet/SKILL.md

The canonical home for this skill is azure-resource-manager-cosmosdb-dotnet in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

57%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.

The body is a well-structured, code-rich guide to Cosmos DB management-plane operations with strong actionability, but it is held back by missing verification checkpoints in the provisioning workflow and reference-file links that point to non-existent bundle files.

Suggestions

Add explicit verification steps to the Core Workflow (e.g., GET the account/database after create and assert provisioning state succeeded) to create a validate-then-proceed feedback loop.

Create the referenced bundle files (references/account-management.md, references/sql-resources.md, references/throughput.md) or remove the Reference Files table so links are not dead.

Move the version numbers into a clearly marked 'Versions' or 'Deprecated' section, or drop them, to avoid time-sensitive content penalizing conciseness.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and code-forward without explaining basics, but includes time-sensitive version strings ('Stable v1.4.0, Preview v1.4.0-beta.13') and somewhat redundant tables (Key Types Reference and Related SDKs repeat code/warning content), so it could be tightened.	3 / 5
Actionability	It provides concrete, executable C# snippets for account/database/container creation, throughput, keys, and error handling; minor gaps exist because snippets depend on variables defined in earlier steps rather than being fully standalone.	4 / 5
Workflow Clarity	The Core Workflow is clearly sequenced (steps 1-5), but it lacks validation/verification checkpoints for these cloud database provisioning operations; per the rubric, missing validation in database/batch operations caps workflow clarity at 3.	3 / 5
Progressive Disclosure	Sections are well organized and a Reference Files table clearly signals one-level-deep references, but the referenced files (references/account-management.md, sql-resources.md, throughput.md) do not exist in the bundle, so the navigation is broken and inlined content that could live in those files remains in SKILL.md.	3 / 5
	Total	13 / 20 Passed

Description

48%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.

The description is accurate and on-niche but terse: it identifies the product and platform without naming any concrete management actions or providing explicit 'when to use' trigger guidance.

Suggestions

Add concrete verbs the SDK performs, e.g. 'Create and manage Cosmos DB accounts, databases, containers, throughput, and RBAC via Azure Resource Manager'.

Append an explicit 'Use when...' clause naming natural trigger phrases (Cosmos DB, ARM, provisioning Azure Cosmos DB resources).

Include common synonyms/extensions users say, such as 'Cosmos DB', 'Azure Cosmos DB', and 'ARM', to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	The phrase 'Azure Resource Manager SDK for Cosmos DB in .NET' names the domain and platform but lists no concrete actions (no provisioning, throughput, or RBAC verbs), matching the 'names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	It gives a clear 'what' (an ARM SDK for Cosmos DB in .NET) but no 'when' / 'Use when...' clause; per the rubric a missing explicit trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	It includes relevant product keywords ('Azure Resource Manager', 'Cosmos DB', '.NET') but misses natural variations or file extensions a user might say, fitting 'some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	It targets a clear niche (Cosmos DB management plane in .NET) with minor overlap risk only against the closely related data-plane SDK, matching 'mostly distinct; minor overlap risk with closely related skills' rather than the fully-distinct 5.	4 / 5
	Total	12 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 3 missing	Warning

	Total	14 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/azure-resource-manager-cosmosdb-dotnet/SKILL.md
Commit: 57c135b

Reviewed: 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.