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".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a well-organized, information-dense NoSQL modeling guide with concrete patterns and a clear step sequence, but it lacks executable code, omits feedback loops for database operations, and fails to connect to or properly maintain its bundled reference files.

Suggestions

Reference the bundled scripts in the workflow, e.g. add a step that runs 'python scripts/validate_schema.py' and explicitly loops on fix-and-revalidate until it passes.

Provide at least one copy-paste-ready executable example (a mongosh command, a cqlsh statement, or a sample document) rather than only prose descriptions.

Fix the two broken resource links (Cassandra data modeling guide and NoSQL design patterns catalog) or remove them, and link to the bundled scripts/assets from the body so progressive disclosure is fully wired.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and assumes competence (it does not explain what NoSQL is), but the prerequisites list and several explanatory passages add tokens that could be tightened without losing clarity.	2 / 3
Actionability	It gives concrete, specific guidance (composite sort keys like 'ORDER#2024-01-15#12345', GSI count under 5, the 16MB limit, bucket/adjacency patterns) but provides no executable code or commands, and never invokes the bundled scripts (validate_schema.py, generate_sample_data.py, migrate_schema.py).	2 / 3
Workflow Clarity	A clear 10-step sequence exists and step 9 mentions validation via explain()/capacity units, but there is no explicit validate->fix->retry feedback loop for these database/batch operations, which the scoring notes say should cap workflow clarity at 2.	2 / 3
Progressive Disclosure	The body is reasonably sectioned (Instructions, Output, Error Handling, Examples, Resources), but it never links to the bundled scripts/assets and the Resources section has two broken empty links (Cassandra guide and NoSQL patterns catalog), so navigation and content split are only partially realized.	2 / 3
	Total	8 / 12 Passed

Description

57%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description targets a clear niche with reasonable trigger phrases, but suffers from a malformed opening ('Build use when...') and vague capability language ('comprehensive guidance and automation') that undercut specificity and completeness.

Suggestions

Fix the malformed opening: replace 'Build use when you need to work with NoSQL data modeling.' with a clean 'Use when...' clause, e.g. 'Design and optimize NoSQL data models for MongoDB, DynamoDB, Redis, and Cassandra. Use when the user needs to model NoSQL data, design document structure, or optimize a NoSQL schema.'

Replace vague fluff ('comprehensive guidance and automation') with concrete capabilities the skill performs (e.g. embedding-vs-referencing decisions, single-table DynamoDB design, schema migration).

Expand trigger terms to include specific database names and common variations (e.g. 'MongoDB schema', 'DynamoDB single-table design', 'Cassandra data model').

Dimension	Reasoning	Score
Specificity	The description names the NoSQL domain and offers trigger phrases, but the stated actions are generic ('NoSQL database design with comprehensive guidance and automation') rather than multiple concrete capabilities, matching the 'names domain and some actions' anchor.	2 / 3
Completeness	It attempts both 'what' and 'when', but the trigger clause is malformed ('Build use when you need to work with NoSQL data modeling') rather than a clean 'Use when...' statement, so the when is present but weak and awkward rather than explicit and clear.	2 / 3
Trigger Term Quality	It lists a few natural phrases a user might say ('model NoSQL data', 'design document structure', 'optimize NoSQL schema'), but coverage of common variations is thin and missing broader terms like specific database names.	2 / 3
Distinctiveness Conflict Risk	NoSQL data modeling is a clear niche with distinct, domain-specific triggers ('model NoSQL data', 'optimize NoSQL schema') that are unlikely to fire for unrelated skills.	3 / 3
	Total	9 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

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

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 6e3a65f

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.