315-frameworks-spring-mongodb

Use when you need to design or implement MongoDB data access in Spring Boot — including document modeling, Spring Data Mongo repositories/templates, indexing, optimistic concurrency, and error handling. This should trigger for requests such as Add MongoDB in Spring Boot; Review Spring Data Mongo design; Improve error handling for Mongo writes; Model MongoDB documents for a Spring Boot service; Configure Spring Data MongoDB indexes or transactions. Part of Plinth Toolkit

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

85%

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

The body is concise, well-structured, and uses progressive disclosure effectively by delegating detail to a verified one-level reference. Its main weakness is actionability: the in-body workflow steps are abstract while concrete code lives only in the reference.

Suggestions

Add one short in-body code snippet (e.g., a minimal @Document/@Version mapping or a DuplicateKeyException handling block) so the most representative guidance is actionable without opening the reference.

Tighten the duplicate compile guidance — the "Compile before MongoDB refactors" header line restates the MANDATORY bullet beneath it.

Make Workflow step 3 ("Apply framework-aligned changes") concrete by listing the specific artifact types to touch (entity class, repository interface, service method) rather than restating the high-level categories.

Dimension	Reasoning	Score
Conciseness	The body is lean, assumes Claude's competence, and avoids explaining concepts Claude already knows; the only minor redundancy is the "Compile before MongoDB refactors" header echoing the bullet beneath it.	3 / 3
Actionability	It supplies concrete executable commands ("./mvnw compile", "mvn clean verify") and a real reference path, but the Workflow steps themselves are abstract ("Implement/refactor mappings, repositories, indexes...") with no executable code in the body, deferring specifics to the reference.	2 / 3
Workflow Clarity	Four sequenced steps with explicit validation checkpoints — MANDATORY compile-before, SAFETY stop-on-failure, VERIFY after — providing the validate/fix/retry feedback loop the rubric rewards for batch/destructive operations.	3 / 3
Progressive Disclosure	A clear overview that points to a single, well-signaled one-level-deep reference (references/315-frameworks-spring-mongodb.md, verified present) via a markdown link, with content appropriately split between overview and detail.	3 / 3
	Total	11 / 12 Passed

Description

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.

The description is concise yet comprehensive, naming concrete capabilities alongside natural-language trigger phrases that cover both what the skill does and when to use it. It is clearly scoped to Spring Boot + MongoDB with low conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete capabilities — "document modeling, Spring Data Mongo repositories/templates, indexing, optimistic concurrency, and error handling" — rather than vague language.	3 / 3
Completeness	Explicitly answers both what ("design or implement MongoDB data access in Spring Boot") and when ("Use when...", "This should trigger for requests such as...") with explicit triggers.	3 / 3
Trigger Term Quality	Provides natural phrasings users would say: "Add MongoDB in Spring Boot", "Review Spring Data Mongo design", "Improve error handling for Mongo writes", "Model MongoDB documents", "Configure Spring Data MongoDB indexes or transactions".	3 / 3
Distinctiveness Conflict Risk	The Spring Boot + MongoDB niche with these specific triggers is clearly distinguishable and unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 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
Commit: aaee915

Reviewed: 1 day 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.