705-technologies-nosql-mongodb

Use when you need framework-agnostic MongoDB and non-relational database query guidance — document schema design, collection modeling, JSON Schema validation, indexes, aggregation pipelines, query performance, consistency trade-offs, transactions, and operational safety — without choosing Spring Boot, Quarkus, or Micronaut. This should trigger for requests such as Design MongoDB document schemas; Review MongoDB queries and indexes; Improve aggregation pipeline performance; Model non-relational data access patterns; Review NoSQL consistency and transaction trade-offs. Part of Plinth Toolkit

Quality

80%

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 ./skills/705-technologies-nosql-mongodb/SKILL.md

Quality

Content

65%Weight 40%Scale 1-5

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

Well-structured overview with clean progressive disclosure and good token efficiency. The main weaknesses are deferred actionable code examples in the body and the absence of an explicit retry/feedback loop in the workflow, the latter being material given the database-operation context the rubric calls out.

Suggestions

Add one or two minimal inline executable examples (e.g., a compound-index creation snippet or a $match-first aggregation skeleton) so the body is actionable without forcing a reference hop for the common cases.

Make the workflow's verification step an explicit feedback loop: 'If build/schema/query-plan checks fail, fix and re-run before proceeding' to satisfy the database-operations validation expectation.

Collapse the 'When to use this skill' list into the scope line or remove it, since the same trigger phrases already appear in the description, to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	Lean and assumes Claude's knowledge (no basic MongoDB primer), but the 'What is covered' and 'When to use this skill' lists partially restate the description's trigger phrases, a minor redundancy that could be trimmed.	4 / 5
Actionability	Concrete commands ('./mvnw compile', './mvnw clean verify') and named operators ($match pushdown, $lookup, $unwind, explain()) are present, but the actual executable query/index/pipeline examples are deferred to the reference rather than shown inline, leaving key details missing in the body.	3 / 5
Workflow Clarity	Four clearly sequenced steps with a dedicated verification step ('Run verification and report results') plus a VERIFY constraint, but there is no explicit validate->fix->retry feedback loop, which the rubric flags as a gap for database operations and caps the score at 3.	3 / 5
Progressive Disclosure	The body is a focused overview that points to a single, clearly signaled, one-level-deep reference (references/705-technologies-nosql-mongodb.md, verified present) referenced in both the workflow and a dedicated Reference section, with details appropriately split out.	5 / 5
	Total	15 / 20 Passed

Description

95%Weight 40%Scale 1-5

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

A strong, comprehensive description with explicit what/when structure, natural trigger phrases, and clear differentiation from related framework skills. The only ding is the second-person voice ('you need'), which costs one point on specificity per the rubric's voice guideline.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities ('document schema design, collection modeling, JSON Schema validation, indexes, aggregation pipelines, query performance, consistency trade-offs, transactions, and operational safety'), but the second-person voice ('Use when you need...') triggers the 1-point specificity reduction.	4 / 5
Completeness	Explicitly answers both 'what' (framework-agnostic MongoDB/NoSQL query guidance across named topics) and 'when' via concrete trigger phrases ('This should trigger for requests such as...').	5 / 5
Trigger Term Quality	Comprehensive natural trigger phrases users would actually say ('Design MongoDB document schemas; Review MongoDB queries and indexes; Improve aggregation pipeline performance') with synonyms spanning MongoDB and NoSQL.	5 / 5
Distinctiveness Conflict Risk	Clear niche (framework-agnostic MongoDB/NoSQL) with explicit deferral of Spring Boot, Quarkus, and Micronaut, minimizing overlap with sibling framework skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: jabrena/plinth
Path: skills/705-technologies-nosql-mongodb/SKILL.md
Commit: f6dfc6f

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