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

86%

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

Quality

Content

78%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.

A token-efficient, well-structured overview that delegates detail to a single clearly-signaled reference and includes a validating build workflow. Its main weakness is actionability: the body's core implementation steps are abstract, with concrete code living only in the reference.

Suggestions

Add one short inline code snippet or a concrete parameter example (e.g., a minimal @Document/@Version mapping) so the body is executable without opening the reference.

Replace the 'stop immediately' failure handling with an explicit fix-and-retry loop (e.g., 'If compilation fails, fix the reported errors and re-run compile until it passes before proceeding').

Tighten the 'When to use this skill' list since it largely duplicates the description's trigger phrases, reclaiming tokens for the inline example.

Dimension	Reasoning	Score
Conciseness	The body is lean (~40 lines), assumes Claude's competence, explains no basic concepts, and every section earns its place — Constraints, When-to-use, Workflow, and Reference are all terse and purposeful.	5 / 5
Actionability	Concrete executable commands exist for verification ('./mvnw compile', 'mvn clean verify'), but the core change steps are high-level ('Implement/refactor mappings, repositories, indexes, and failure handling policies') with the actual implementation detail delegated to the reference, leaving key specifics out of the body.	3 / 5
Workflow Clarity	A clear 4-step sequence with explicit validation checkpoints (MANDATORY compile before, SAFETY stop-on-failure, VERIFY after), but the feedback loop is 'stop immediately' rather than a fix-and-retry cycle, leaving a minor validation gap.	4 / 5
Progressive Disclosure	Clear overview body pointing to a single one-level-deep reference (references/315-frameworks-spring-mongodb.md, which exists), signaled both inline in workflow step 1 and in a dedicated Reference section; content is appropriately split.	5 / 5
	Total	17 / 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, well-structured description that clearly states capabilities and natural trigger phrases with a distinct niche. The only weakness is the use of second-person voice ('you need to'), which the rubric penalizes on specificity.

Suggestions

Rewrite the opening in third-person imperative voice (e.g., 'Designs and implements MongoDB data access in Spring Boot...') to avoid the second-person specificity penalty while keeping the trigger clause.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('document modeling, Spring Data Mongo repositories/templates, indexing, optimistic concurrency, and error handling') for comprehensive coverage, but the second-person phrasing 'Use when you need to...' triggers the rubric's voice penalty, reducing the score by one.	4 / 5
Completeness	Explicitly answers both what ('design or implement MongoDB data access in Spring Boot — including...') and when ('Use when you need to... This should trigger for requests such as...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural trigger phrases a user would actually say: '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'.	5 / 5
Distinctiveness Conflict Risk	Clear niche (Spring Boot + MongoDB data access) with distinct triggers; minimal overlap risk with other skills, and 'Part of Plinth Toolkit' signals its place in a toolkit.	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/315-frameworks-spring-mongodb/SKILL.md
Commit: 77b8825

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