CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

60

Quality

71%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/azure-cosmos-ts/SKILL.md

The canonical home for this skill is azure-cosmos-ts in administrakt0r/AI-Agents-Safe-Coding-Skills

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.

A highly actionable, code-rich SDK reference whose examples are copy-paste ready. Its weaknesses are token efficiency (inline time-sensitive version info and a bulk import reference) and a lack of progressive disclosure — everything lives in one large SKILL.md with no bundle files.

Suggestions

Move the 'TypeScript Types Reference' import block and the detailed bulk-operation API into a separate reference file linked from SKILL.md, keeping only key examples inline.

Relocate time-sensitive details ('Current Version: 4.9.0', Node version) into a versioned/deprecated note section so they don't penalize conciseness, or drop them entirely.

Add an explicit validation/feedback loop for batch and destructive operations — e.g., after executeBulkOperations or delete, verify the result and retry failed operations with backoff — to lift workflow clarity above the batch-op cap of 3.

DimensionReasoningScore

Conciseness

Mostly lean code examples with little padding, but time-sensitive details ('Current Version: 4.9.0', 'Node.js >= 20.0.0') sit outside any deprecated/old-patterns section, and the inline TypeScript Types Reference import block is reference material that adds tokens Claude largely does not need.

3 / 5

Actionability

Copy-paste-ready, executable TypeScript covering create/read/update/upsert/delete/patch, parameterized and paginated queries, bulk operations, hierarchical partition keys, error handling, and ETags — comprehensive coverage of common cases.

5 / 5

Workflow Clarity

Sections are clearly labeled and the bulk example checks per-operation status codes, but destructive/batch operations (delete, executeBulkOperations) lack explicit validate→fix→retry checkpoints, which the rubric caps at 3 for batch/destructive skills.

3 / 5

Progressive Disclosure

Well-organized with clear section headers, but the skill is a monolithic ~470-line inline reference with no bundle files and no one-level-deep references; material like the Types Reference and detailed bulk API would be better split into separate files.

3 / 5

Total

14

/

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 solid, concrete description that clearly names the SDK and its data-plane scope with a usable 'Use for' trigger clause. It is slightly below top marks because the trigger phrasing lists capabilities rather than user-mention scenarios and a few natural synonyms are absent.

DimensionReasoningScore

Specificity

Names the domain and lists several concrete action categories ('CRUD operations on documents, queries, bulk operations, and container management'), but stops short of comprehensive coverage (e.g., no stored procedures, patch, triggers).

4 / 5

Completeness

Both 'what' (data plane SDK for Cosmos DB) and 'when' ('Use for CRUD operations...') are present and concrete, but the 'when' clause enumerates capabilities rather than explicit user-trigger phrases ('Use when the user mentions...').

4 / 5

Trigger Term Quality

Good keyword coverage with natural terms users would say ('Azure Cosmos DB', '@azure/cosmos', 'documents', 'queries'), though a few common variations ('Cosmos DB', 'NoSQL') are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche with distinct triggers — 'data plane operations' and '@azure/cosmos' explicitly separate it from the management SDK, minimizing conflict risk.

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.

Validation15 / 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
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.