cosmos-provider

Implementation details for the EF Core Azure Cosmos DB provider. Use when changing Cosmos-specific code.

Quality

75%

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 ./.agents/skills/cosmos-provider/SKILL.md

Quality

Content

92%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 an efficient, well-organized reference that assumes competence and provides concrete, copy-paste-ready test-setup guidance. The only soft spot is that the 'Key Differences' section is descriptive rather than executable.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's EF Core competence: terse bullets like 'No migrations — use EnsureCreated()' and 'ETag for optimistic concurrency' with no concept over-explanation.	5 / 5
Actionability	The test section gives copy-paste-ready guidance (the Test__Cosmos__DefaultConnection env var and a full ConditionalFact attribute), but the 'Key Differences' bullets are descriptive constraints rather than executable steps.	4 / 5
Workflow Clarity	As a single-purpose reference skill under 50 lines with no destructive multi-step process, the content is clearly sectioned and unambiguous, satisfying the simple-skill exception.	5 / 5
Progressive Disclosure	Under 50 lines with no need for external references (none of references/scripts/assets exist), the body is well-organized into clear sections with no nested references, meeting the simple-skill bar.	5 / 5
	Total	19 / 20 Passed

Description

57%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 clearly targets a distinct, well-scoped niche and includes an explicit 'Use when' trigger, but the 'what' is abstract and lacks concrete enumerated capabilities. Tightening specificity of actions would lift the lower dimensions.

Suggestions

Replace the generic 'Implementation details' with concrete capabilities, e.g. 'Configure partition keys, model owned/complex types as embedded JSON, and handle ETag optimistic concurrency for the EF Core Azure Cosmos DB provider.'

Broaden the trigger phrase with natural variations, e.g. 'Use when changing Cosmos-specific code, modeling Cosmos entities, or configuring the EF Core Cosmos provider.'

Add a synonym/file cue (e.g. 'Cosmos DB', 'EF Core Cosmos provider') to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	The phrase 'Implementation details for the EF Core Azure Cosmos DB provider' names the domain specifically but the only action ('Implementation details') is generic, with no concrete capabilities enumerated.	2 / 5
Completeness	Both 'what' ('Implementation details for the EF Core Azure Cosmos DB provider') and 'when' ('Use when changing Cosmos-specific code') are explicitly present, though the 'what' is somewhat abstract.	4 / 5
Trigger Term Quality	'EF Core Azure Cosmos DB provider' and 'Cosmos-specific code' are relevant natural terms for this niche, but coverage lacks synonyms or variations.	3 / 5
Distinctiveness Conflict Risk	The niche 'EF Core Azure Cosmos DB provider' is highly specific with distinct triggers and minimal conflict risk, though trigger phrases are narrower than the anchor-5 example.	4 / 5
	Total	13 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: dotnet/efcore
Path: .agents/skills/cosmos-provider/SKILL.md
Commit: 92b26f9

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