CtrlK
BlogDocsLog inGet started
Tessl Logo

cosmos-provider

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

67

Quality

80%

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

Quality

Content

85%

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

A tight, well-organized reference that wastes no tokens and presents its facts clearly. The only real gap is actionability: most bullets describe differences rather than giving executable guidance for changing Cosmos-specific code.

Suggestions

Add one short executable code snippet showing a typical Cosmos-specific change (e.g. configuring a partition key or applying an ETag concurrency check) to lift actionability.

For the test-emulator guidance, show the exact command/env var invocation a user would run, rather than only naming Test__Cosmos__DefaultConnection.

Consider a brief 'How to change Cosmos-specific code' mini-checklist that sequences the typical edit -> run-emulator-test steps, which would also reinforce workflow clarity.

DimensionReasoningScore

Conciseness

The body is lean bullet points that assume Claude's competence (e.g. 'No migrations — use EnsureCreated()', 'ETag for optimistic concurrency') with no padded explanation of what Cosmos or EF Core is.

3 / 3

Actionability

It offers some concrete, copy-paste-ready tokens (the ConditionalFact attribute, the Test__Cosmos__DefaultConnection env var) but most bullets are descriptive differences rather than executable commands or code, leaving guidance incomplete for a 3.

2 / 3

Workflow Clarity

This is a single-purpose reference of provider differences with clearly organized sections; under the simple-skill allowance the content is unambiguous and needs no multi-step workflow.

3 / 3

Progressive Disclosure

At roughly a dozen lines with well-organized sections and no external references needed, this simple skill satisfies progressive disclosure through clean structure alone.

3 / 3

Total

11

/

12

Passed

Description

75%

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 concise, third-person description with an explicit 'Use when' trigger and a clear niche, satisfying the what-and-when requirement. It could list more concrete actions and more natural trigger-term variations to reach the top of the scale.

DimensionReasoningScore

Specificity

Names the domain ('EF Core Azure Cosmos DB provider') and a concrete action ('changing Cosmos-specific code'), but does not list multiple specific actions like query tuning or partition-key config, so it is not comprehensive enough for a 3.

2 / 3

Completeness

It states what the skill is ('Implementation details for the EF Core Azure Cosmos DB provider') and gives an explicit 'Use when changing Cosmos-specific code' trigger, answering both what and when.

3 / 3

Trigger Term Quality

Relevant terms ('Cosmos-specific code', 'EF Core Azure Cosmos DB provider') are present but it lacks common variations a user might naturally say ('Cosmos DB', 'partition key', 'NoSQL provider').

2 / 3

Distinctiveness Conflict Risk

Scoped narrowly to the Cosmos DB provider with a distinct trigger, making it unlikely to fire for unrelated EF Core or relational-provider skills.

3 / 3

Total

10

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
dotnet/efcore
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.