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.
91
53%
Does it follow best practices?
Impact
99%
1.01xAverage score across 9 eval scenarios
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.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly articulates what the skill does, when it should be activated, and includes specific trigger terms and domain concepts. It covers multiple concrete actions, names specific technologies, and provides an explicit 'Use this skill when...' clause with natural user phrases. The only minor weakness is slight verbosity, but it doesn't detract from clarity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and concepts: schema creation, data modeling for MongoDB/DynamoDB, defining document structures, embedding vs. referencing, access pattern optimization, and sharding key selection. | 3 / 3 |
Completeness | Clearly answers both 'what' (design NoSQL data models, schema creation, embedding vs referencing, access pattern optimization, sharding key selection) and 'when' (explicit 'Use this skill when...' clause with specific trigger phrases). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'NoSQL data model', 'design MongoDB schema', 'create DynamoDB table', 'NoSQL database architecture', 'document structures'. These cover common user phrasings well. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to NoSQL database design with specific technologies (MongoDB, DynamoDB) and domain-specific concepts (sharding keys, embedding vs referencing). Unlikely to conflict with general database or SQL skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
7%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads like a product description or README rather than actionable instructions for Claude. It lacks any concrete code examples, actual schema definitions, or specific decision frameworks. The content mostly tells Claude what it should do at a high level without providing the domain-specific knowledge (e.g., actual document structures, partition key strategies, GSI patterns) that would make it useful.
Suggestions
Replace the abstract examples with actual schema definitions — e.g., show a concrete MongoDB document structure with embedded vs. referenced patterns, or a DynamoDB table definition with PK/SK design.
Add a decision framework for embedding vs. referencing with specific criteria (document size limits, update frequency, read patterns) rather than just naming the concept.
Remove the 'How It Works' and 'When to Use This Skill' sections — these describe Claude's behavior rather than teaching it anything new. Replace with concrete modeling patterns and anti-patterns.
Include DynamoDB-specific guidance like single-table design patterns, GSI overloading, and partition key selection rules with concrete examples showing PK/SK schemas for common access patterns.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and explains concepts Claude already knows well (what denormalization is, what access patterns are, what NoSQL databases do). The 'How It Works' and 'When to Use This Skill' sections describe Claude's own behavior rather than providing actionable instructions. Much of this is meta-description rather than useful content. | 1 / 3 |
Actionability | There is no concrete code, no executable examples, no actual schema definitions, no specific commands. The examples describe what 'the skill will' do rather than showing actual MongoDB document structures or DynamoDB table definitions. Everything is abstract description rather than instruction. | 1 / 3 |
Workflow Clarity | The 'How It Works' section lists vague high-level steps like 'Analyze Data Requirements' and 'Design Data Model' without any concrete guidance on how to perform these steps. There are no validation checkpoints, no decision criteria for embedding vs. referencing, and no feedback loops. | 1 / 3 |
Progressive Disclosure | The content is organized into clear sections with headers, which provides some structure. However, there are no references to external files, and content that could benefit from deeper treatment (e.g., MongoDB-specific patterns vs. DynamoDB-specific patterns) is neither included nor referenced. | 2 / 3 |
Total | 5 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Commit
13d35b8
- 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.