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

The body is highly actionable with comprehensive executable examples, but it is a monolithic ~470-line reference that could be trimmed and split into bundle files, and its batch/destructive operations lack validation feedback loops. Conciseness and progressive disclosure are the weakest dimensions.

Suggestions

Move the bulk TypeScript Types Reference import list and the detailed bulk-operations example into a references/ file (e.g. REFERENCE.md) and link to it, cutting SKILL.md well under 50 lines of pure reference.

Remove the generic "When to Use" filler and the redundant Best Practices recap that restates guidance already shown in code, and drop or relocate the pinned version numbers ("4.9.0", Node version) to a versioned/deprecated note.

Add an explicit validate->fix->retry feedback loop for batch/destructive operations (e.g., check each bulk result statusCode, retry 429s with backoff, re-run failed operations) to lift workflow clarity above the batch-operation cap of 3.

DimensionReasoningScore

Conciseness

Mostly efficient code-focused content, but it includes redundant sections (full TypeScript import reference, a Best Practices recap, a repeated createIfNotExists partition example), time-sensitive version numbers ("4.9.0", "Node.js >= 20.0.0") outside any deprecated section, and a filler "When to Use" line that add tokens Claude does not need.

3 / 5

Actionability

Copy-paste-ready executable examples cover the common cases comprehensively: CRUD, upsert, patch, parameterized queries, pagination, bulk operations, hierarchical partition keys, error handling, ETags, and a complete service-layer pattern.

5 / 5

Workflow Clarity

This is a reference catalog rather than a sequenced workflow, and the destructive/batch operations (delete, executeBulkOperations) lack a validate->fix->retry feedback loop; per the rubric, batch operations without validation cap workflow clarity at 3.

3 / 5

Progressive Disclosure

Good section headers make the ~470-line file navigable, but no bundle files exist and large reference material (full type import list, bulk-operation details, common patterns) is inlined that would be better split into one-level-deep references.

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.

The description is specific, actionable, and clearly distinguishes the data-plane SDK, with an explicit "Use for" trigger. It falls just short of top marks because the trigger terms lack synonyms (NoSQL/database) and the when-clause lists operations rather than scenario-based triggers.

Suggestions

Add natural synonyms and extensions a user might say, e.g. "NoSQL database", "Cosmos DB", ".ts/.js", to broaden trigger-term coverage.

Reframe the when-clause around user situations (e.g. "Use when the user needs to read/write Cosmos DB documents, run SQL queries, or do bulk inserts") rather than only listing operation types.

Mention stored procedures/triggers/patch in the description to lift specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

Lists several concrete actions ("CRUD operations on documents, queries, bulk operations, and container management") but omits others present in the body (stored procedures, triggers, patch), so it is not fully comprehensive.

4 / 5

Completeness

Clearly states what ("Azure Cosmos DB JavaScript/TypeScript SDK ... for data plane operations") and has an explicit "Use for ..." trigger clause; the when lists operations rather than user-situation triggers, which keeps it just below a 5.

4 / 5

Trigger Term Quality

Strong natural terms ("Azure Cosmos DB", "documents", "queries", "CRUD", "@azure/cosmos") but missing common synonyms a user might say such as "NoSQL", "database", or file extensions, so coverage is good but not complete.

4 / 5

Distinctiveness Conflict Risk

Names a specific SDK and package (@azure/cosmos) with a clear data-plane niche, giving it distinct triggers and minimal overlap with other skills.

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.