azure-cosmosdb
Azure Cosmos DB partition keys, consistency levels, change feed, SDK patterns
40
40%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/azure-cosmosdb/SKILL.mdQuality
Discovery
22%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a comma-separated list of Cosmos DB topics with no verbs, no actions, and no 'Use when...' guidance. While the domain keywords provide some relevance for matching, the lack of concrete capability statements and explicit trigger conditions makes it very weak as a skill selector. It would be difficult for Claude to confidently choose this skill over other Azure or database-related skills.
Suggestions
Add concrete action verbs describing what the skill does, e.g., 'Designs partition key strategies, configures consistency levels, implements change feed processors, and writes Cosmos DB SDK code.'
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Azure Cosmos DB configuration, NoSQL data modeling, partition strategies, or Cosmos DB SDK usage.'
Include natural keyword variations users might say, such as 'CosmosDB', 'NoSQL', 'Azure database', 'RU/s', 'throughput', or 'document database'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists topic areas (partition keys, consistency levels, change feed, SDK patterns) but does not describe any concrete actions. There are no verbs indicating what the skill does—it reads like a keyword list rather than a capability description. | 1 / 3 |
Completeness | The description answers neither 'what does this do' (no actions described) nor 'when should Claude use it' (no 'Use when...' clause or equivalent trigger guidance). It is essentially a topic list with no functional or contextual information. | 1 / 3 |
Trigger Term Quality | It includes relevant technical terms a user might mention ('Cosmos DB', 'partition keys', 'consistency levels', 'change feed', 'SDK patterns'), but lacks natural phrasing variations or broader terms like 'NoSQL', 'Azure database', 'RU', 'throughput', or 'CosmosDB' that users might also say. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Azure Cosmos DB' provides some niche specificity, but without clear actions or trigger guidance, it could overlap with a general Azure skill or a broader database skill. The domain is somewhat distinct but the description doesn't reinforce boundaries. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is highly actionable with excellent, executable code examples across TypeScript, Python, and CLI, covering a comprehensive range of Cosmos DB operations. However, it suffers from being a monolithic document that tries to cover too many topics in a single file without progressive disclosure or external references. It also lacks explicit multi-step workflows with validation checkpoints, particularly for operations like bulk imports and batch operations where error recovery is important.
Suggestions
Split content into separate files (e.g., SDK_PATTERNS.md, INDEXING.md, PYTHON_SDK.md, CLI_REFERENCE.md) and keep SKILL.md as a concise overview with links to each
Add explicit multi-step workflows with validation checkpoints for common scenarios like 'setting up a new container with proper indexing' or 'performing a bulk data migration with verification'
Remove or significantly condense the API comparison table and basic concept definitions table - Claude already knows what Cosmos DB APIs are
Add a retry/error recovery pattern for 429 throttling since it's listed as an anti-pattern to ignore but no concrete retry code is provided
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is quite long (~500 lines) and covers a lot of ground. While most content is useful, the tables explaining basic Cosmos DB concepts (APIs, consistency levels) and the full Python SDK section alongside TypeScript add bulk. Some sections like the API table and concept definitions could be trimmed since Claude knows these. However, the code examples are lean and well-structured. | 2 / 3 |
Actionability | Excellent actionability throughout - every section provides fully executable TypeScript and Python code with proper imports, error handling, and realistic patterns. CLI commands are copy-paste ready. The CRUD operations, batch operations, change feed, indexing, and throughput management all have concrete, complete examples. | 3 / 3 |
Workflow Clarity | The skill presents individual operations clearly but lacks explicit multi-step workflows with validation checkpoints. For example, there's no workflow for setting up a new Cosmos DB project end-to-end, no validation steps after bulk imports, and no error recovery flow for batch operations beyond a simple throw. The batch operation section checks for failures but doesn't provide a retry/recovery pattern. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of content with no references to external files. At ~500 lines covering partition keys, SDK setup, CRUD, consistency, batching, change feed, Python SDK, indexing, throughput, CLI, cost optimization, and anti-patterns, this would greatly benefit from splitting into separate reference files (e.g., SDK patterns, indexing guide, Python reference) with a concise overview in SKILL.md. | 1 / 3 |
Total | 8 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
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 | 9 / 11 Passed | |
- Repository
- alinaqi/claude-bootstrap
- Commit
65efb33
- 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.