CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-cosmos-rust

Azure Cosmos DB SDK for Rust (NoSQL API). Use for document CRUD, queries, containers, and globally distributed data.

64

Quality

77%

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

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

An actionable, well-structured SDK quickstart with executable Rust examples throughout. The main weakness is workflow clarity: destructive operations proceed without validation or error-recovery checkpoints.

Suggestions

Add a verification step after destructive writes (e.g. read the item back after replace/patch/delete, or check the response status) and document a validate->fix->retry loop for failed operations.

Replace the filler "When to Use" sentence with concrete trigger conditions, or remove the section if the description already covers it.

Consider moving the per-operation API detail and the reference-links table into a separate REFERENCE.md so SKILL.md stays a lean overview pointing one level deep.

DimensionReasoningScore

Conciseness

Lean, code-first sections with minimal padding; not 5 because the "When to Use" line ("applicable to execute the workflow or actions described in the overview") is throwaway fluff that adds no information.

4 / 5

Actionability

Copy-paste-ready Rust examples for create, read, replace, patch, and delete plus auth and client setup cover the common CRUD cases end to end.

5 / 5

Workflow Clarity

CRUD operations are listed but lack validation checkpoints for destructive operations (delete, replace, patch); per the destructive-ops guideline this caps the score at 3, and there are no validate->fix->retry feedback loops.

3 / 5

Progressive Disclosure

Well-organized sections with external reference links clearly tabulated and no nested references; not 5 because the ~130-line body inlines API-style content that could be split into a reference file.

4 / 5

Total

16

/

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 specific, well-targeted description that clearly states the domain and concrete capabilities with an explicit trigger clause. Minor gains are available by adding situation-based trigger phrasing and a few more natural synonyms.

DimensionReasoningScore

Specificity

Names the domain and lists several concrete actions ("document CRUD, queries, containers, and globally distributed data"); falls short of 5 because coverage is not comprehensive (no stored procedures, TTL, change feed).

4 / 5

Completeness

Provides a clear "what" (SDK for the NoSQL API) and an explicit "Use for..." trigger clause; not 5 because the "when" is framed around actions rather than trigger situations (no "Use when the user mentions..." phrasing).

4 / 5

Trigger Term Quality

Includes natural terms users would say ("Azure Cosmos DB", "Rust", "NoSQL", "document CRUD", "queries", "containers"); not 5 because common synonyms/extensions like "Cosmos", ".json", or "partition keys" as trigger phrases are absent.

4 / 5

Distinctiveness Conflict Risk

"Azure Cosmos DB SDK for Rust (NoSQL API)" carves out a clear niche with distinct triggers and minimal overlap risk 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.