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

52%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/database/nosql-data-modeler/skills/modeling-nosql-data/SKILL.md

Quality

Content

65%Weight 40%Scale 1-3

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

The content is concise, well-structured, and gives specific NoSQL modeling guidance across four databases, but it underuses its own bundle (scripts unreferenced, references/assets essentially empty) and lacks explicit validation feedback loops and executable commands.

Suggestions

Wire the bundled scripts into the workflow, e.g. replace step 9's generic validation with 'Run `python scripts/validate_schema.py <schema.json>`' and step 8's migration with 'Use `python scripts/migrate_schema.py`', and add an explicit 'if validation fails, fix and re-validate' feedback loop.

Fill the empty Resources links (Cassandra data modeling guide, NoSQL design patterns catalog) or remove them, and populate references/ with the detailed material currently inlined (e.g., an embedding-vs-referencing decision guide) so SKILL.md stays an overview.

Either deliver the promised asset templates (schema_templates/, sample_data/, diagrams/) or remove the unchecked placeholders in assets/README.md to avoid advertising content that does not exist.

Dimension	Reasoning	Score
Conciseness	The body is dense and information-rich, assumes Claude's knowledge of NoSQL concepts, and avoids padding or explaining basics; every section (embedding vs. referencing, sort-key formats, GSI limits, error table) earns its place.	3 / 3
Actionability	Guidance is concrete and specific (composite sort keys like 'ORDER#2024-01-15#12345', GSI count under 5, 16MB limit, schemaVersion fields), but no executable commands are given and the bundled validate_schema.py / migrate_schema.py scripts are never referenced, leaving the validation/migration steps missing key details.	2 / 3
Workflow Clarity	A clear 10-step numbered sequence exists with a validation step (step 9, explain() / capacity units), but there is no explicit validate-fix-retry feedback loop for destructive/batch schema operations, which the rubric caps at 2.	2 / 3
Progressive Disclosure	The body is well-organized into sections, but the bundled scripts/ are not referenced from the body, references/ contains only a placeholder README, assets/ lists unchecked template placeholders, and two Resources links (Cassandra guide, NoSQL patterns catalog) are empty.	2 / 3
	Total	9 / 12 Passed

Description

40%Weight 40%Scale 1-3

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 identifies a clear niche and includes explicit triggers, but is undermined by a garbled opening, vague fluff, narrow trigger coverage, and second-person voice. It answers both what and when only weakly.

Suggestions

Fix the garbled opening to a clean third-person trigger clause, e.g. 'Designs data models for NoSQL databases (MongoDB, DynamoDB, Redis, Cassandra). Use when modeling NoSQL data, designing document/key-value schemas, or optimizing NoSQL access patterns.'

Replace 'comprehensive guidance and automation' with two or three concrete capabilities (e.g., 'designs document schemas, plans partition/sort keys and GSIs, and validates access patterns').

Add database-specific natural trigger terms (MongoDB schema, DynamoDB single-table design, Cassandra data model) and drop the ambiguous 'design document structure'.

Dimension	Reasoning	Score
Specificity	Names the NoSQL domain and a few actions ('model NoSQL data', 'design document structure', 'optimize NoSQL schema', 'NoSQL database design'), but pads with fluff ('comprehensive guidance and automation'); the second-person 'you need to work with' triggers the rubric's -1 specificity penalty.	1 / 3
Completeness	Both a use-when clause and explicit trigger guidance are present, plus a what-statement, but the what is vague ('comprehensive guidance and automation') and the opening 'Build use when you need...' is garbled, so it does not clearly answer both.	2 / 3
Trigger Term Quality	Lists three explicit trigger phrases, but they are narrow and 'design document structure' is jargon-leaning; missing common variations and database-specific terms (MongoDB, DynamoDB) users would naturally say.	2 / 3
Distinctiveness Conflict Risk	NoSQL data modeling is a fairly distinct niche, but the 'design document structure' trigger could overlap with document/file-handling skills and a general database skill, so conflict risk is not fully eliminated.	2 / 3
	Total	7 / 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
Path: plugins/database/nosql-data-modeler/skills/modeling-nosql-data/SKILL.md
Commit: 4c47e33

Reviewed: about 4 hours 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.