415-frameworks-quarkus-mongodb

Use when you need MongoDB persistence in Quarkus — including Panache Mongo entities/repositories, document design, indexes, transactions where applicable, and error handling. This should trigger for requests such as Add MongoDB in Quarkus; Review Quarkus Mongo Panache design; Improve Mongo error handling in Quarkus services; Model MongoDB documents for a Quarkus service; Configure Quarkus MongoDB clients codecs or transactions. Part of Plinth Toolkit

Quality

89%

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 well-structured, token-efficient overview skill with strong progressive disclosure and a validation-backed workflow. Its main weakness is actionability: the body gives executable build commands but defers all concrete MongoDB/Panache code to the reference, leaving the core implementation guidance abstract.

Suggestions

Add one or two short inline code snippets for the most common Panache Mongo patterns (e.g., an entity/repository declaration) so the body is actionable without forcing a reference read for routine cases.

Make the verify-failure recovery explicit in step 4 (e.g., 'if verify fails, fix and re-run ./mvnw clean verify before reporting') to close the workflow_clarity validation gap.

Note the most important error-handling rule inline (e.g., duplicate-key / retry guidance) rather than only hinting at 'failure handling', so the body conveys at least one concrete domain-specific rule.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: no explanation of what Quarkus, MongoDB, or Panache are, and every line is purposeful, matching the anchor 5 'every token earns its place'.	5 / 5
Actionability	Concrete executable commands are present (./mvnw compile, mvn clean verify), but the core domain guidance ('Implement/refactor Panache Mongo mappings, repository access, and failure handling') is abstract direction with all code deferred to the reference, leaving key details out of the body.	3 / 5
Workflow Clarity	A clear 4-step sequence with explicit validation checkpoints (compile-before, verify-after) and a stop-on-failure feedback loop; the minor gap is that the verify-failure recovery loop is not spelled out.	4 / 5
Progressive Disclosure	A clean overview pointing to a single real, one-level-deep reference (references/415-frameworks-quarkus-mongodb.md, verified present), signaled in three places including a markdown link, with detail appropriately split out.	5 / 5
	Total	17 / 20 Passed

Description

100%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 high-quality description that clearly states what the skill does and when to use it, with concrete natural-language trigger phrases and a distinct, low-conflict niche. It uses third person and avoids fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — Panache Mongo entities/repositories, document design, indexes, transactions, and error handling — giving comprehensive coverage of MongoDB persistence in Quarkus, matching the anchor 5 example.	5 / 5
Completeness	Explicitly answers both 'what' (MongoDB persistence in Quarkus including Panache entities, document design, indexes, transactions, error handling) and 'when' ('Use when…', 'should trigger for requests such as…') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger phrases ('Add MongoDB in Quarkus', 'Review Quarkus Mongo Panache design') plus synonyms (MongoDB/Mongo) yield comprehensive coverage of terms users would actually say.	5 / 5
Distinctiveness Conflict Risk	The Quarkus + MongoDB + Panache Mongo combination is a clear niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	20 / 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/415-frameworks-quarkus-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.