CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

azure-cosmosdb

Azure Cosmos DB partition keys, consistency levels, change feed, SDK patterns

56

Quality

70%

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

The body is exceptionally actionable — comprehensive, executable code in two languages with concrete do/don't examples — but it pays for that with duplication and monolithic length. Splitting language-specific and reference material into bundle files and adding retry/validation guidance for batch and throttled operations would address the weakest dimensions.

Suggestions

Move the Python SDK section, CLI quick reference, and indexing policy details into one-level-deep reference files (e.g., references/python-sdk.md, references/cli.md) and keep SKILL.md as a concise overview with clearly signaled links.

Deduplicate the CRUD coverage: keep one language inline and point to the other, and trim redundant examples like getUserById and the Key Concepts rows that restate basics.

Add explicit feedback loops for database operations: a 429 retry-with-exponential-backoff code sample and batch result validation/error-recovery steps for the transactional batch and bulk import flows.

DimensionReasoningScore

Conciseness

Mostly efficient — dense tables and code that assume Claude's competence — but the full Python CRUD section largely duplicates the TypeScript CRUD section, the Key Concepts table defines basics Claude already knows ('Item | Single document/record (JSON)'), and examples like the getUserById variant and verbose ETag flow could be tightened, which is more than 'minor instances of over-explanation'.

3 / 5

Actionability

Fully executable, copy-paste-ready TypeScript and Python code covering setup, CRUD, pagination, patch, ETag concurrency, batch/bulk, change feed, and indexing, plus concrete CLI commands and good/bad partition key examples that span the common cases.

5 / 5

Workflow Clarity

Sections are well-organized but the body is a reference document with no sequenced workflow, and database/batch operations (transactional batch, bulk import, 429 throttling) lack validation or retry feedback loops — the rubric's cap for database operations without feedback loops holds this at 3.

3 / 5

Progressive Disclosure

Clear section headers give it structure, but it is a ~700-line monolithic SKILL.md with no bundle files at all; the Python SDK section, CLI quick reference, and indexing policy material clearly belong in one-level-deep reference files, matching 'content that should be separate is inline'.

3 / 5

Total

14

/

20

Passed

Description

65%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 highly distinctive and uses natural domain terminology, but it reads as a topic list rather than a capability statement and omits any explicit 'use when' trigger guidance within the description field itself. Adding an action-oriented 'what' and a trigger clause would lift it substantially.

Suggestions

Add an explicit 'Use when...' clause to the description itself (e.g., 'Use when working with Azure Cosmos DB containers, partitioning, RU/s throughput, or the change feed'), since the separate when-to-use frontmatter field does not count toward the description.

Rewrite the topic list as concrete actions, e.g., 'Design partition keys, choose consistency levels, implement change feed processing, and write TypeScript/Python CRUD code for Azure Cosmos DB'.

Include natural synonyms and SDK identifiers users might say ('Cosmos', 'NoSQL account', '@azure/cosmos') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('Azure Cosmos DB') plus concrete topic areas ('partition keys, consistency levels, change feed, SDK patterns'), but these are topic nouns rather than actions and coverage of the skill's actual scope (CRUD, throughput, indexing, cost) is partial — matching the 'names domain and 1-2 concrete actions' anchor better than the 'several specific actions' anchor.

3 / 5

Completeness

The 'what' is reasonably clear (reference material on the listed topics) but the description contains no 'Use when...' clause or equivalent trigger guidance — the separate 'when-to-use' frontmatter field is not part of the description — so completeness is capped at 3.

3 / 5

Trigger Term Quality

Terms like 'Azure Cosmos DB', 'partition keys', 'consistency levels', and 'change feed' are natural phrases users would say when needing this skill, though common variations like 'Cosmos', 'NoSQL database', or SDK/package names are missing.

4 / 5

Distinctiveness Conflict Risk

'Azure Cosmos DB' with its specific feature areas carves out a clear niche with distinct triggers; no plausible overlap with other skills' trigger terms.

5 / 5

Total

15

/

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.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (714 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

alinaqi/maggy

Path

skills/azure-cosmosdb/SKILL.md

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.