modeling-nosql-data

This skill enables Claude to design NoSQL data models. It activates when the user requests assistance with NoSQL database design, including schema creation, data modeling for MongoDB or DynamoDB, or defining document structures. Use this skill when the user mentions "NoSQL data model", "design MongoDB schema", "create DynamoDB table", or similar phrases related to NoSQL database architecture. It assists in understanding NoSQL modeling principles like embedding vs. referencing, access pattern optimization, and sharding key selection.

1.01x

Quality

53%

Does it follow best practices?

Impact

99%

1.01x

Average score across 9 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./backups/skills-migration-20251108-070147/plugins/database/nosql-data-modeler/skills/nosql-data-modeler/SKILL.md

Evaluation results

100%

Recipe Platform Data Model Design

MongoDB embedding and denormalization

Criteria

Without context

With context

Database identified

100%

Entities analyzed

100%

Embedding used

100%

Denormalization rationale

100%

Access pattern optimization

100%

Index recommendations

100%

Example documents provided

100%

Collections defined

100%

Embedding vs referencing decision

100%

Trade-offs discussed

100%

Fleet Tracking System: DynamoDB Table Design

DynamoDB index and partition key design

Criteria

Without context

With context

Database identified

100%

Partition key defined

100%

Sort key defined

100%

Even data distribution rationale

100%

Access pattern coverage

100%

Secondary index defined

100%

Index-to-query mapping

100%

Example items shown

100%

Throughput consideration

100%

Concrete schema output

100%

Hospital Records Migration: Relational to NoSQL

Relational to NoSQL schema migration

Criteria

Without context

With context

Database chosen

100%

Entities analyzed

100%

Embedding decision made

100%

Referencing decision made

100%

Embedding rationale tied to reads

100%

Denormalization identified

100%

Access pattern justification

100%

Example documents provided

100%

Collections/tables defined

100%

Concrete schema output

75%

100%

Relational translation explained

100%

MongoDB Sharding Strategy for a High-Volume Transaction Platform

Sharding key selection

Criteria

Without context

With context

MongoDB identified

100%

Multiple candidates analyzed

100%

Hot spot risk identified

100%

Even distribution rationale

100%

Sharding key recommended

100%

Schema definition provided

100%

Index recommendations

100%

Access pattern coverage

100%

Example documents provided

100%

Trade-offs discussed

100%

DynamoDB Schema Redesign for a Growing E-Commerce Platform

Optimize existing NoSQL schema

Criteria

Without context

With context

Scan anti-pattern identified

100%

Partition key redesigned

80%

100%

Sort key added

100%

Even distribution rationale

100%

Customer access pattern covered

100%

Status/time access pattern covered

100%

Seller/date access pattern covered

100%

Index-to-query mapping

100%

Example items shown

100%

Concrete table definition

75%

100%

NoSQL Schema Design for a Real-Time Collaborative Note-Taking App

Database type selection and schema design

Criteria

Without context

With context

Database type identified

100%

Database choice justified

100%

Entities analyzed

100%

Embedding used for read-heavy data

100%

Referencing used for frequently-changing data

100%

Embedding vs referencing explained

100%

Access pattern optimization

100%

Index or key recommendations

100%

Example documents provided

100%

Concrete schema output

100%

Collections or tables named

100%

97%

Food Delivery Platform Data Layer

MongoDB schema with query generation

Criteria

Without context

With context

MongoDB identified

100%

Entities analyzed

75%

100%

Embedding used

100%

Denormalization rationale

100%

Access pattern optimization

100%

Concrete schema definition

100%

Index recommendations

100%

MongoDB queries generated

100%

Queries match access patterns

100%

Example documents provided

62%

Embedding vs referencing trade-off addressed

100%

97%

Project Management SaaS Backend

Multi-tenant DynamoDB partition key design

Criteria

Without context

With context

DynamoDB identified

100%

Entities analyzed

100%

Partition key defined

100%

Even distribution rationale

100%

Sort key defined

100%

Access patterns covered

100%

GSI defined

100%

Index-to-query mapping

100%

Example items shown

100%

Concrete table definition

50%

70%

Single-table or multi-table justified

100%

Content Discovery Platform Data Model

NoSQL schema for many-to-many relationships

Criteria

Without context

With context

Database identified

100%

Database choice justified

100%

Entities analyzed

100%

Many-to-many relationship handled

100%

Embedding used for read-heavy data

100%

Referencing used for large/mutable data

100%

Access pattern optimization

100%

Index or key recommendations

100%

Example documents provided

100%

Concrete schema output

100%

Trade-offs discussed

100%

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 13d35b8

Evaluated: about 2 months ago
Agent: Claude Code
Model: Claude Sonnet 4.6

Table of Contents

Recipe Platform Data Model Design Fleet Tracking System: DynamoDB Table Design Hospital Records Migration: Relational to NoSQL MongoDB Sharding Strategy for a High-Volume Transaction Platform DynamoDB Schema Redesign for a Growing E-Commerce Platform NoSQL Schema Design for a Real-Time Collaborative Note-Taking App Food Delivery Platform Data Layer Project Management SaaS Backend Content Discovery Platform Data Model

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.