azure-cosmos-ts
Build Azure Cosmos DB Apps with TypeScript
Azure Cosmos DB development requires correct authentication, partition keys, queries, and failure handling. This skill provides practical TypeScript patterns for common data plane operations.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "azure-cosmos-ts" from https://skillstore.io/skills/sickn33-azure-cosmos-ts.md and its manifest at https://skillstore.io/api/skills/sickn33-azure-cosmos-ts/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "azure-cosmos-ts". Plan secure authentication for a TypeScript API running in Azure.
Expected outcome:
A setup plan using DefaultAzureCredential, a named endpoint variable, required Azure roles, startup validation, and account key avoidance.
Using "azure-cosmos-ts". Design product lookup by category and maximum price.
Expected outcome:
A parameterized query approach scoped by category, with pagination guidance and notes about request units and cross-partition costs.
Using "azure-cosmos-ts". Review concurrent product price updates.
Expected outcome:
A workflow that reads the item ETag, applies conditional replacement, handles precondition failures, and preserves conflicting updates.
Security Audit
SafeThe static alerts are false positives caused by Markdown code fences, TypeScript template literals, inline code, documented environment variable access, and a placeholder Azure endpoint. The skill contains instructional examples only, with no executable scripts, credential exfiltration, prompt injection, or system reconnaissance.
Risk Factors
⚙️ External commands (50)
🌐 Network access (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-azure-cosmos-ts/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-azure-cosmos-ts?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-azure-cosmos-ts?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-azure-cosmos-ts/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-azure-cosmos-ts.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). azure-cosmos-ts security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-azure-cosmos-ts/audits/5BibTeX citation
@techreport{sickn33-sickn33-azure-cosmos-ts-2026,
author = {sickn33},
title = {azure-cosmos-ts security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-azure-cosmos-ts/audits/5},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "azure-cosmos-ts security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/sickn33-azure-cosmos-ts/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-azure-cosmos-ts:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Create a Cosmos DB service
Design a typed service layer for document creation, lookup, updates, deletion, and category queries.
Review data access patterns
Check authentication, parameterized queries, partition keys, retries, and ETag handling before deployment.
Plan high-volume writes
Select bulk operation patterns and partition keys for workloads with many document changes.
Try These Prompts
Show how to connect a Node.js TypeScript application to Cosmos DB with DefaultAzureCredential and named environment variables.
Create a typed Cosmos DB service for [entity] with create, read, patch, replace, upsert, and delete methods.
Design a parameterized query for [filter requirements]. Include pagination, partition key usage, and handling for rate limits.
Review my Cosmos DB access design for authentication, partitioning, bulk writes, ETags, retries, disposal, scalability, and cost risks.
Best Practices
- Prefer DefaultAzureCredential and assign only the required Cosmos DB data roles.
- Use parameterized queries and include partition keys whenever the access pattern permits.
- Handle rate limits, ETag conflicts, missing documents, and client disposal explicitly.
Avoid
- Do not embed account keys, connection strings, or production endpoints in source code.
- Do not use broad cross-partition queries without reviewing request unit cost.
- Do not replace shared documents without ETag checks when concurrent updates are possible.