Agent skill · software engineering · jeremylongshore
modeling-nosql-data
Build use when you need to work with NoSQL data modeling.
Why this skill is useful
Provides specific NoSQL modeling patterns and automation scripts for MongoDB and DynamoDB that the AI wouldn't reliably generate on its own.
What it needs
Requires aws dynamodb, cqlsh, mongosh, redis-cli installed locally. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
NoSQL Data Modeler Overview Design data models for NoSQL databases including MongoDB (document), DynamoDB (key-value/wide-column), Redis (key-value), and Cassandra (wide-column). Unlike relational modeling where normalization drives design, NoSQL modeling starts from access patterns and query requirements, then shapes the data to serve those patterns efficiently. Prerequisites mongosh, aws dynamodb CLI, redis-cli, or cqlsh installed depending on target database Documented list of application access patterns (read/write queries the application performs) Expected data volumes (document count, average document size, growth rate) Read/write ratio and latency requirements for each access pattern Understanding of consistency requirements (strong vs. eventual consistency) Instructions 1. Catalog all application access patterns as a table with columns: pattern name, query description, frequency (queries/sec), latency requirement, and data fields accessed. This drives every modeling decision. 2. For MongoDB document modeling, apply the embedding vs. referencing decision framework: Embed when: data is always accessed together, child data has no independent lifecycle, cardinality is bounded (1:few), and updates are infrequent. Reference when: data has independent access patterns, cardinality is unbounded (1:many/many:many), child documents are large, or data is shared across parents. 3. Design document schemas that match query patterns. If the application needs "all orders for a customer with line items," embed line items inside the order document. If the application needs "all products across all orders," use references to a products collection. 4. For DynamoDB, design the partition key and sort key to support the primary access pattern with a single-table design. Use composite sort keys (e.g., ORDER#2024-01-15#12345) for hierarchical data. Plan GSIs (Global Secondary Indexes) for secondary access patterns, keeping total GSI count under 5. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/modeling-nosql-data--370f29