CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

azure-cosmos-ts

Azure Cosmos DB JavaScript/TypeScript SDK (@azure/cosmos) for data plane operations. Use for CRUD operations on documents, queries, bulk operations, and container management.

Quality

79%

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

Quality

Content

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

A highly actionable, executable reference for the @azure/cosmos data plane SDK with excellent code coverage. Its weaknesses are structural: everything lives in one long SKILL.md with no reference files, and validation/retry feedback loops for database and bulk operations are recommended but not demonstrated.

Suggestions

Add an explicit retry/feedback loop example, e.g., a helper that inspects bulk result statusCode and retries 429s using error.retryAfterInMs, and reference it from the bulk and error-handling sections.

Move 'TypeScript Types Reference' and 'Common Patterns' into a references/ file (e.g., references/types.md, references/patterns.md) linked from SKILL.md to apply progressive disclosure.

Delete the vacuous 'When to Use' section, which restates nothing actionable and wastes context.

DimensionReasoningScore

Conciseness

Efficient and code-dominant with terse prose throughout. Not 5 because the 'When to Use' section ('This skill is applicable to execute the workflow or actions described in the overview') is pure filler and the 30-line 'TypeScript Types Reference' import block earns little; not 3 because over-explanation is minor relative to the whole body.

4 / 5

Actionability

Fully executable, copy-paste-ready TypeScript for auth, CRUD, patch, parameterized queries, pagination, bulk operations, error handling, ETags, and a service-layer pattern, with env vars and install commands included. Nothing falls to the 4 anchor since no pseudocode or missing key details exist.

5 / 5

Workflow Clarity

Sections are well-ordered, but this skill covers database and batch operations where the rubric caps workflow clarity at 3 without feedback loops: the bulk example checks result.statusCode per operation yet no validate-fix-retry loop is shown, and retry guidance ('Implement retry logic with exponential backoff') is stated but never demonstrated. Not 4 because explicit retry/verify loops are missing.

3 / 5

Progressive Disclosure

A single ~470-line monolith with no bundle files: 'TypeScript Types Reference' and 'Common Patterns' clearly belong in separate reference files. Not 2 because section headers are clean and in-file navigation is easy; not 4 because nothing is split out despite substantial separable content, and the skill is far beyond the under-50-lines simple-skill exception.

3 / 5

Total

15

/

20

Passed

Description

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

A strong, specific description that names the exact SDK, the plane it operates on, and its concrete capabilities with an explicit use clause. The main improvement is making the 'when' guidance situational (mentioning Cosmos DB/NoSQL work) and adding a few synonyms like 'NoSQL database'.

Suggestions

Rewrite the 'when' clause to name trigger situations rather than repeat capabilities, e.g., 'Use when building TypeScript/JavaScript apps that read, write, or query documents in an Azure Cosmos DB NoSQL account.'

Add natural synonyms such as 'NoSQL database' and 'Cosmos container' to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Lists several specific actions ('CRUD operations on documents, queries, bulk operations, and container management') with a named SDK and domain. Not 5 because coverage has minor gaps (stored procedures, patch, pagination, concurrency are absent); not 3 because more than 1-2 concrete actions are enumerated.

4 / 5

Completeness

Answers 'what' clearly (data plane SDK for the listed operations) and includes an explicit 'Use for...' trigger clause. Not 5 because the 'when' clause restates the capability list rather than naming concrete trigger situations (e.g., 'when working with Cosmos DB NoSQL accounts'); not 3 because the 'Use for...' clause is explicit.

4 / 5

Trigger Term Quality

Good natural keywords: 'Azure Cosmos DB', '@azure/cosmos', 'JavaScript/TypeScript', 'documents', 'bulk operations'. Not 5 because common variations users would say are missing ('NoSQL database', 'Cosmos container', 'partition key'); not 3 because several genuinely natural terms are present.

4 / 5

Distinctiveness Conflict Risk

'Azure Cosmos DB JavaScript/TypeScript SDK (@azure/cosmos) for data plane operations' carves a clear, distinct niche with minimal conflict risk; the data-plane framing distinguishes it from the ARM management SDK. Neighboring anchor 4 would require noted overlap risk, which is not present.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

skills/azure-cosmos-ts/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.