modeling-nosql-data

tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill modeling-nosql-data

Build use when you need to work with NoSQL data modeling. This skill provides NoSQL database design with comprehensive guidance and automation. Trigger with phrases like "model NoSQL data", "design document structure", or "optimize NoSQL schema".

49%

Overall

Validation — 81%

Implementation — 20%

Activation — 67%

SKILL.md

Review

Evals

Validation

81%

Warnings & errors only

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
metadata_version	'metadata' field is not a dictionary	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Implementation

20%

This skill is a generic template with no actual NoSQL data modeling content. It lacks any concrete guidance on document design, denormalization strategies, access patterns, partition keys, or specific database examples (MongoDB, DynamoDB, Cassandra). The content could apply to virtually any technical task and provides no value beyond what Claude already knows.

Suggestions

Add concrete NoSQL data modeling examples: show document structures, embedding vs referencing decisions, and partition key selection with actual JSON/code

Include specific patterns for common NoSQL databases (e.g., DynamoDB single-table design, MongoDB schema patterns) with executable examples

Replace generic steps with NoSQL-specific workflow: identify access patterns → design documents → validate with sample queries → test performance

Remove all generic boilerplate (prerequisites, error handling sections) and focus on NoSQL-specific knowledge Claude doesn't already have

Dimension	Reasoning	Score
Conciseness	Extremely verbose and generic; filled with boilerplate that applies to any task. Contains no NoSQL-specific content that Claude doesn't already know. Phrases like 'Review current configuration, setup, and baseline metrics' are padding without substance.	1 / 3
Actionability	Entirely abstract with no concrete code, commands, or NoSQL-specific examples. No actual data modeling patterns, no document structure examples, no query patterns. 'Design optimal approach based on best practices' is vague direction, not executable guidance.	1 / 3
Workflow Clarity	Steps are numbered and sequenced, but they're generic project management steps, not NoSQL data modeling workflows. No validation checkpoints specific to data modeling (e.g., testing query patterns, validating denormalization decisions).	2 / 3
Progressive Disclosure	References external files in Resources section, but the main content is a monolithic wall of generic text. The referenced files use placeholder paths that may not exist. No clear navigation between quick-start and advanced topics.	2 / 3
	Total	6 / 12 Passed

Activation

67%

This description adequately covers the basics with explicit trigger phrases and a clear domain focus on NoSQL. However, it lacks specific concrete actions beyond generic 'guidance and automation', and the trigger terms miss common database-specific keywords users would naturally use. The description would benefit from more specific capabilities and broader trigger term coverage.

Suggestions

Add specific concrete actions like 'design document schemas', 'define partition keys', 'model relationships in document databases', or 'optimize query patterns'

Expand trigger terms to include specific NoSQL databases (MongoDB, DynamoDB, Cassandra) and common phrases like 'document database', 'key-value store', or 'denormalization'

Dimension	Reasoning	Score
Specificity	Names the domain (NoSQL data modeling) and mentions 'design' and 'guidance and automation', but lacks specific concrete actions like 'create document schemas', 'define partition keys', or 'normalize/denormalize data structures'.	2 / 3
Completeness	Explicitly answers both what ('NoSQL database design with comprehensive guidance and automation') and when ('Trigger with phrases like...'), providing clear trigger guidance for when Claude should select this skill.	3 / 3
Trigger Term Quality	Includes some relevant trigger phrases ('model NoSQL data', 'design document structure', 'optimize NoSQL schema') but misses common variations users might say like 'MongoDB', 'DynamoDB', 'document database', 'key-value store', or 'schema design'.	2 / 3
Distinctiveness Conflict Risk	Focuses on NoSQL specifically which helps distinguish from general database skills, but 'data modeling' and 'schema' could overlap with SQL/relational database skills. Could be more distinctive by specifying NoSQL types (document, key-value, graph).	2 / 3
	Total	9 / 12 Passed

Reviewed

13 days ago

Table of Contents

Validation Implementation Activation

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.