Azure Cosmosdb
CheckedAccess, query, and manage data stored within your Azure Cosmos DB accounts using alinaqi's specialized AI agent skill.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add alinaqi/maggy --skill azure-cosmosdb -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
alinaqi
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned alinaqi/claude-bootstrap at 72a456e6cc.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 72a456e6cc
- Manifest
- skills/azure-cosmosdb/SKILL.md
- Scanned
- 1 file, 662 lines
About this skill
What it does
This skill enables AI agents to interact with Azure Cosmos DB, a fully managed NoSQL database service. Specifically, it focuses on the NoSQL (Core) API, which provides a flexible document database. The skill allows for accessing, querying, and managing data stored within your Cosmos DB accounts, understanding concepts like containers, items, partition keys, and request units (RUs). It's designed to help you leverage Cosmos DB’s scalability and performance capabilities effectively.
When to use it
- Managing user data: Retrieve or update user profiles and order information using a
userIdas the partition key. - Multi-tenant applications: Query documents based on tenant identifiers for efficient access within a shared database environment.
- IoT telemetry analysis: Access device readings and sensor data organized by
deviceId. - Log aggregation and analysis: Query logs partitioned using synthetic keys (e.g., date + category).
- Working with graph databases: While the skill primarily focuses on NoSQL Core, it can be adapted to interact with other Cosmos DB APIs like Gremlin for graph database operations.
Key capabilities
- Access and query data within Azure Cosmos DB accounts.
- Supports the NoSQL (Core) API, MongoDB, PostgreSQL (Citus), Apache Cassandra, Apache Gremlin, and Table APIs.
- Understands key concepts such as containers, items, partition keys, logical partitions, physical partitions, and request units.
- Provides guidance on designing effective partition keys for optimal performance and scalability.
Example prompts
- "Retrieve all documents where userId is 'user-456'."
- "Find all logs from the tenant with ID 'tenant-abc' that occurred on 2024-01-15."
- "Show me the latest telemetry readings for deviceId 'device-789'."
Tips & gotchas
- Partition Key Design is Crucial: Carefully consider your partition key strategy. Avoid low cardinality or monotonically increasing keys to prevent hot partitions and ensure even data distribution.
- RU Consumption: Be mindful of request units (RUs) when querying, as they represent the throughput currency for Cosmos DB operations.
- Environment Variables: The skill requires environment variables
COSMOS_ENDPOINT,COSMOS_KEY, andCOSMOS_DATABASEto be configured.