backend-java

Java Developer Agent. Java/Spring Boot 기반 백엔드 개발을 담당합니다. Spring, JPA, Hibernate, Maven, Gradle 전문.

Quality

27%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/backend-java/SKILL.md

Quality

Discovery

32%

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 identifies the technology stack clearly but fails to specify concrete actions the skill performs and completely lacks trigger guidance for when Claude should select it. It reads more like a job title than an actionable skill description, missing the critical 'Use when...' clause needed for effective skill selection.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about Java development, Spring Boot applications, JPA entities, or Gradle/Maven build configuration'

Replace '백엔드 개발을 담당합니다' with specific actions like 'Creates REST APIs, configures Spring beans, writes JPA entities, manages build dependencies'

Include natural language variations users might say: 'REST API', 'microservices', 'database mapping', 'dependency management', '.java files'

Dimension	Reasoning	Score
Specificity	Names the domain (Java/Spring Boot backend development) and lists technologies (Spring, JPA, Hibernate, Maven, Gradle), but doesn't describe concrete actions like 'create REST APIs', 'configure database connections', or 'write unit tests'.	2 / 3
Completeness	Describes what domain it covers but completely lacks a 'Use when...' clause or any explicit trigger guidance. The 'when' is entirely missing, which per rubric guidelines should cap this at maximum 2, but since it's also weak on the 'what', it scores 1.	1 / 3
Trigger Term Quality	Includes relevant technical keywords (Java, Spring Boot, JPA, Hibernate, Maven, Gradle) that users might mention, but missing common variations like 'backend API', 'REST', 'microservices', 'dependency injection', or Korean equivalents users might naturally say.	2 / 3
Distinctiveness Conflict Risk	Specific to Java/Spring Boot ecosystem which provides some distinction, but '백엔드 개발' (backend development) is broad and could overlap with other backend-focused skills in different languages or frameworks.	2 / 3
	Total	7 / 12 Passed

Implementation

22%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill content reads more like a role description or persona definition than actionable technical guidance. It lists technologies and conventions but provides no concrete examples, code snippets, or workflows that would help Claude perform Java/Spring development tasks effectively. The content assumes Claude needs to know what areas this 'agent' covers rather than how to actually execute development work.

Suggestions

Add executable code examples for common patterns (e.g., Controller-Service-Repository structure, constructor injection, JPA entity definition)

Include a workflow for typical development tasks like creating a new endpoint or setting up a Spring Boot project

Replace the abstract convention list with concrete before/after code examples showing correct patterns

Add references to detailed guides for complex topics like Spring Security configuration or DDD implementation

Dimension	Reasoning	Score
Conciseness	The content is relatively brief but includes some unnecessary sections like 'trigger keywords' that don't provide actionable guidance. The role description is redundant given the title.	2 / 3
Actionability	No concrete code examples, commands, or executable guidance provided. Lists concepts and conventions abstractly without showing how to implement them.	1 / 3
Workflow Clarity	No workflow or process steps defined. Simply lists areas of expertise and naming conventions without explaining how to approach Java/Spring development tasks.	1 / 3
Progressive Disclosure	Content is brief and organized into sections, but lacks any references to detailed documentation, examples, or advanced guides that would be expected for such a broad domain.	2 / 3
	Total	6 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	10 / 11 Passed

Repository: shaul1991/shaul-agents-plugin
Commit: 9242c58

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