113-java-maven-documentation

Use when you need to create a DEVELOPER.md file for a Maven project — combining a fixed base template with dynamic sections derived from allowlisted Maven POM structure, including a Plugin Goals Reference, Maven Profiles table, and Submodules table for multi-module projects. This should trigger for requests such as Create DEVELOPER.md; Generate DEVELOPER.md; Maven project documentation; Add Maven documentation; Plugin goals reference. Part of Plinth Toolkit

Quality

76%

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/113-java-maven-documentation/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 with excellent progressive disclosure, but the workflow has a step-numbering inconsistency and lacks a validation checkpoint, and the actionable template detail lives entirely in the reference rather than the body.

Suggestions

Reconcile the step count: the SCOPE says 'Execute steps 1-5 in order' but the Workflow lists only four steps — either add the fifth step or correct the reference.

Add an explicit validation/verification checkpoint (e.g. confirm every explicitly declared plugin has a subsection and that the generated DEVELOPER.md contains the verbatim base template) before declaring the file complete.

Specify the 'local XML tooling' concretely (e.g. name the XML query approach or tool) so the extraction step is reproducible without inferring.

Dimension	Reasoning	Score
Conciseness	The body is lean and does not explain concepts Claude already knows, but the untrusted-POM and explicitly-declared-plugin rules are restated across Constraints, SCOPE, and Workflow, and the 'When to use' list duplicates the description's triggers.	4 / 5
Actionability	The allowlisted extraction field list is concrete (artifact IDs, packaging, goal names from <executions>, profile IDs), but the executable base template and goal catalog are deferred to the reference and 'local XML tooling' is left unspecified.	3 / 5
Workflow Clarity	Steps are sequenced, but there is no validation/verification checkpoint for the POM-parsing and generation flow, and the SCOPE references 'steps 1-5' while the Workflow section lists only four steps.	3 / 5
Progressive Disclosure	Clear overview sections with a single, well-signaled one-level-deep reference (references/113-java-maven-documentation.md, a real file) that appropriately holds the bulk template and catalog detail.	5 / 5
	Total	15 / 20 Passed

Description

87%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 description that clearly states purpose, scope, and concrete trigger phrases with minimal conflict risk. The only weakness is the second-person 'you need to create' voice, which also slightly dilutes the otherwise comprehensive specificity.

Suggestions

Rephrase the opening in third person to match the 'Use when working with...' convention (e.g. 'Use when creating a DEVELOPER.md file for a Maven project...') and recover the specificity point lost to the voice penalty.

Add a few more natural trigger synonyms (e.g. 'Maven POM documentation', 'build documentation', 'document Maven plugins') to broaden keyword coverage.

Dimension	Reasoning	Score
Specificity	Names multiple concrete outputs ('Plugin Goals Reference, Maven Profiles table, and Submodules table'), which is comprehensive, but the second-person phrasing 'Use when you need to create' triggers the voice penalty of -1.	4 / 5
Completeness	Explicitly answers both what ('create a DEVELOPER.md file... combining a fixed base template with dynamic sections') and when ('This should trigger for requests such as...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural-term coverage with synonyms ('Create DEVELOPER.md; Generate DEVELOPER.md; Add Maven documentation; Plugin goals reference'), though a few common variations like 'POM documentation' or 'build docs' are missing.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (DEVELOPER.md for Maven projects) with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	18 / 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/113-java-maven-documentation/SKILL.md
Commit: 05bf9d1

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