CtrlK
BlogDocsLog inGet started
Tessl Logo

java-coding-standards

Java coding standards for Spring Boot and Quarkus services: naming, immutability, Optional usage, streams, exceptions, generics, CDI, reactive patterns, and project layout. Automatically applies framework-specific conventions. Use when writing or reviewing Java in a Spring Boot or Quarkus service.

71

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%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, actionable coding-standards skill with concrete executable Java examples and clear framework-scoped guidance. It is largely concise and well-organized, with only minor verbosity and no need for external reference files given its size.

Suggestions

Trim the 'Examples' intro paragraph and other restating prose to push conciseness toward the lean anchor.

Consider extracting the larger reference sections (e.g., Project Structure, Testing Expectations) into separate reference files with clearly signaled one-level links if the skill grows further.

DimensionReasoningScore

Conciseness

Mostly lean with PASS/FAIL code blocks and terse inline rationale, but a few restating passages (the 'Examples' intro and repeated framework-detection prose) could be trimmed; not the fully lean top anchor.

4 / 5

Actionability

Concrete, copy-paste-ready Java throughout with explicit PASS/FAIL labels covering the common cases (DI, Optional, reactive pipelines, exception handling, config), matching the fully-executable anchor.

5 / 5

Workflow Clarity

The Framework Detection section gives a clear branching sequence ('Build file contains quarkus -> ...'), and as a standards reference no destructive-checkpoints are required; it stops short of the top anchor because it is reference-style rather than a sequenced workflow with explicit feedback loops.

4 / 5

Progressive Disclosure

Well-organized single self-contained file with clear section headers and no nested references; good structure with minor gaps (some inlined reference-style content that could live in separate files), just below the well-signaled-one-level-reference top anchor.

4 / 5

Total

17

/

20

Passed

Description

92%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, specific description that explicitly answers both what the skill does and when to use it, with concrete domain coverage and a clear use trigger. Slightly technical in its trigger vocabulary, which keeps trigger_term_quality just below the top anchor.

DimensionReasoningScore

Specificity

Lists multiple specific concrete capability areas ('naming, immutability, Optional usage, streams, exceptions, generics, CDI, reactive patterns, and project layout') with the action 'writing or reviewing', matching the comprehensive-coverage anchor.

5 / 5

Completeness

Clearly states what ('Java coding standards for Spring Boot and Quarkus services: ...') and explicitly when ('Use when writing or reviewing Java in a Spring Boot or Quarkus service.'), matching the both-what-and-when anchor.

5 / 5

Trigger Term Quality

Natural terms like 'writing or reviewing Java', 'Spring Boot', and 'Quarkus' are present and triggerable, but the keyword set leans technical and omits some common variations a user might naturally say.

4 / 5

Distinctiveness Conflict Risk

Narrow niche (Spring Boot/Quarkus Java coding standards) with distinct, framework-scoped triggers and minimal overlap risk with other skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
affaan-m/ECC
Reviewed

Table of Contents

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.