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

68%

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

80%

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 tight, highly actionable reference: concrete package/module mappings, exact test commands, and a clear decision tree for repository placement. Its weaknesses are the absence of explicit validation checkpoints in its workflows and a monolithic single-file structure with no progressive split despite running ~100 lines.

Suggestions

Add an explicit validation/feedback step to the test-building workflow (e.g. 'If make test-backend-app reports cannot-find-symbol, run make test-backend to rebuild dependencies before re-trying').

Extract the large placement table and query-repository catalog into a reference file (e.g. references/placement.md) and link to it from SKILL.md to apply progressive disclosure.

Add a short 'Verify' checklist at the end confirming dependency direction and package placement before considering a backend change complete.

Dimension	Reasoning	Score
Conciseness	The body is dense and reference-style — a placement table, module list, package paths, and make commands — with no padding explaining Maven/Java basics, matching 'lean and efficient; every token earns its place'.	3 / 3
Actionability	It gives copy-paste-ready specifics: the module/package placement table, 'make test-backend-app' / 'make test-backend' commands, and a 4-step decision list for query repositories, matching 'fully executable commands; copy-paste ready'.	3 / 3
Workflow Clarity	The read-use-case decision list and test-building guidance are clearly sequenced, but there are no explicit validation checkpoints or feedback loops, fitting 'sequence present but checkpoints missing or implicit'.	2 / 3
Progressive Disclosure	It is well-organized into clear sections but is a single monolithic SKILL.md with no external references and no content split; the full placement table and catalogs sit inline, matching 'some structure but content that should be separate is inline'.	2 / 3
	Total	10 / 12 Passed

Description

57%

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 well-scoped to a specific project niche and states its purpose clearly, but it reads as a declarative rule statement rather than trigger guidance and omits any 'Use when' clause, leaving the 'when to use' half implicit.

Suggestions

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

Surface natural trigger terms users would actually say ('where do I put this service', 'new controller', 'Maven module') rather than only architectural jargon.

List a few concrete capabilities (placement table lookup, dependency-direction checks, test commands) to lift specificity toward the score-3 anchor.

Dimension	Reasoning	Score
Specificity	Quotes 'Rules for the SkillHub backend Maven multi-module clean architecture' and 'Ensures agents place new code in the correct module and respect dependency direction' name the domain and a couple of actions, but do not list multiple concrete capabilities, matching the score-2 anchor.	2 / 3
Completeness	It states what the skill does but provides no 'Use when...' or equivalent trigger guidance, so per the rubric a missing explicit trigger caps completeness at 2.	2 / 3
Trigger Term Quality	Terms like 'backend', 'Maven multi-module', 'module' are relevant, but the phrasing is declarative/technical ('clean architecture', 'dependency direction') with no natural user-facing trigger phrasing, fitting 'some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	Scoped tightly to 'SkillHub backend Maven multi-module clean architecture', it occupies a clear niche and is unlikely to fire for unrelated skills, matching the score-3 anchor.	3 / 3
	Total	9 / 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: iflytek/skillhub
Path: .agents/skills/backend-module-structure/SKILL.md
Commit: ac46ad5

Reviewed: 3 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.