backend-module-structure

Rules for the SkillHub backend Maven multi-module clean architecture. Ensures agents place new code in the correct module and respect dependency direction.

Quality

64%

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 ./.agents/skills/backend-module-structure/SKILL.md

Quality

Content

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

The body is a well-structured, actionable reference skill: it provides a concrete module/placement table, executable test commands, and a clear decision procedure, all without explaining concepts Claude already knows. Minor gains are possible by tightening a few explanatory passages and adding a pom.xml example for new module dependencies.

Dimension	Reasoning	Score
Conciseness	The body is information-dense and assumes Claude knows Java/Maven/clean architecture without padding, but passages like the 'Code reality' deviation note and the stale-artifact explanation are slightly expansive and could be trimmed, fitting 'efficient; minor instances of over-explanation'.	4 / 5
Actionability	Concrete, actionable guidance pervades the skill — a full code-type→module→package placement table, executable `make test-backend-app` commands, and a 4-step decision procedure — with only minor gaps such as no pom.xml snippet for adding a new module dependency.	4 / 5
Workflow Clarity	The read-use-case decision tree is a clearly numbered sequence and the test section includes an explicit 'do not run X, run Y because...' avoidance checkpoint, but there is no explicit validate-then-fix feedback loop, leaving it just below 5.	4 / 5
Progressive Disclosure	Content is well-organized into clear headed sections (Trigger, Rules, subsections) with no nested references and no bundle files present; it sits below 5 only because some inline reference material (the placement table, query-repository list) could optionally live in a separate file.	4 / 5
	Total	16 / 20 Passed

Description

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

The description clearly states what the skill governs and targets a distinct, specific niche, but it omits any 'when to use' trigger guidance and relies on technical jargon rather than natural user phrases. Adding an explicit 'Use when...' clause with natural trigger terms would raise completeness and trigger quality.

Suggestions

Add an explicit trigger clause, e.g. 'Use when adding or modifying SkillHub backend Java code, creating services/controllers/repositories, or reviewing module placement.'

Include natural user-facing terms and synonyms (e.g. 'backend module', 'which module', 'Maven module', 'clean architecture') alongside the technical jargon to improve trigger quality.

Consider naming a third concrete action (e.g. 'choosing between domain and query repositories') to broaden specificity coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('SkillHub backend Maven multi-module clean architecture') and two concrete actions ('place new code in the correct module' and 'respect dependency direction'), matching the 1-2 concrete actions anchor; not a 4 because coverage is limited to two high-level actions.	3 / 5
Completeness	The 'what' is clear ('Rules for... Ensures agents place new code...'), but there is no 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Relevant technical keywords ('backend', 'Maven', 'module', 'dependency direction') appear but are fairly jargon-heavy with no synonyms or natural user variations, fitting 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	The niche is highly specific ('SkillHub backend Maven multi-module clean architecture') with minimal conflict risk, but the absence of explicit trigger phrases keeps it just below the 5 anchor.	4 / 5
	Total	13 / 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: iflytek/skillhub
Path: .agents/skills/backend-module-structure/SKILL.md
Commit: b896c69

Reviewed: 5 days 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.