Tessl • The management layer for AI agent skills

SkillPublic

quarkus-tdd

Test-driven development for Quarkus 3.x LTS using JUnit 5, Mockito, REST Assured, Camel testing, and JaCoCo. Use when adding features, fixing bugs, or refactoring event-driven services.

Quality

80%

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/quarkus-tdd/SKILL.md

Quality

Content

71%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 content is exceptionally actionable — complete, executable examples covering unit, Camel, async, REST, and integration testing plus coverage enforcement — with a clear TDD workflow. Its weaknesses are token efficiency (a large duplicated Best Practices section) and structure: everything is inlined in a single ~800-line SKILL.md instead of being split across one-level-deep reference files.

Suggestions

Merge the 'Best Practices' section into 'Key Testing Patterns' (or vice versa) and cut the lines that repeat them verbatim, removing ~70 lines of duplication.

Split the full test-class examples into one-level-deep reference files (e.g. references/camel-testing.md, references/async-testing.md, references/coverage.md) and keep SKILL.md as a lean overview with well-signaled links, per the progressive-disclosure rubric.

Expand the 4-step Workflow with explicit commands (e.g. 'run `mvn test` and confirm the new test fails') so each step carries an executable validation checkpoint.

Dimension	Reasoning	Score
Conciseness	The body is mostly concrete, executable code rather than padding, but it includes unnecessary material: the ~70-line 'Best Practices' section substantially duplicates the earlier 'Key Testing Patterns' list (@Nested, @DisplayName, givenX_whenY_thenZ, AAA, assertThrows), and the 'When to Use' section repeats the frontmatter description. This fits 'mostly efficient but could be tightened' rather than the noticeably-verbose anchor below it.	3 / 5
Actionability	Five complete, copy-paste-ready test classes (unit, Camel route, event service, CompletableFuture, REST resource, plus an integration test) along with full JaCoCo Maven configuration, dependency listings, and runnable commands ('mvn clean test', 'mvn jacoco:check') cover the common cases exhaustively. Fully matches the top anchor.	5 / 5
Workflow Clarity	The TDD workflow is a clear sequence with built-in checkpoints ('Write tests first (they should fail)', 'Refactor with tests green', 'Enforce coverage with JaCoCo (80%+)'), and the skill is not a destructive/batch operation. Not a 5 because the steps are terse one-liners without explicit commands or a re-run-on-failure feedback loop tying them to the later 'mvn test' / 'jacoco:check' sections.	4 / 5
Progressive Disclosure	The body has good internal section headers ('Unit Tests', 'Testing Camel Routes', 'Testing CompletableFuture', 'Resource Layer Tests', 'Coverage with JaCoCo'), but it is ~800 lines of fully inlined test-class code that belongs in separate reference files — and no references/, scripts/, or assets/ bundle exists. This matches 'some structure but content that should be separate is inline'.	3 / 5
	Total	15 / 20 Passed

Description

82%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 explicitly states what the skill does and when to use it, with a distinct Quarkus niche and good natural trigger terms. Its main weakness is specificity: it names the toolchain rather than enumerating the concrete testing actions the skill guides, and it lacks a few common trigger variations.

Suggestions

Replace part of the toolchain list with concrete actions, e.g. 'Write failing JUnit 5 tests first, implement minimally, refactor, and enforce 80%+ JaCoCo coverage' to raise specificity.

Add common trigger variations users would actually say, such as 'unit tests', 'integration tests', or 'test coverage', alongside the existing 'Use when' clause.

Dimension	Reasoning	Score
Specificity	The description names the domain and one concrete action ("Test-driven development") plus a toolchain enumeration ("JUnit 5, Mockito, REST Assured, Camel testing, and JaCoCo"), but tools are not actions, so it matches the anchor for 'names domain and 1-2 concrete actions, but not comprehensive'. It falls short of a 4 because it never states what the skill actually instructs (write failing tests first, implement minimally, refactor, enforce coverage).	3 / 5
Completeness	Clearly answers both questions: the 'what' ('Test-driven development for Quarkus 3.x LTS using JUnit 5, Mockito, REST Assured, Camel testing, and JaCoCo') and an explicit 'when' with concrete trigger phrases ('Use when adding features, fixing bugs, or refactoring event-driven services'). This matches the top anchor exactly.	5 / 5
Trigger Term Quality	Good keyword coverage with terms users naturally say: 'Quarkus', 'JUnit 5', 'Mockito', 'REST Assured', 'Camel', 'JaCoCo', 'adding features', 'fixing bugs', 'refactoring', 'event-driven services'. Not a 5 because common variations like 'unit tests', 'integration tests', 'code coverage', or 'Quarkus testing' are missing.	4 / 5
Distinctiveness Conflict Risk	Clear niche (Quarkus 3.x LTS test-driven development) with distinct technology triggers; minimal overlap risk with generic Java or Spring testing skills. It is clearly distinguishable and unlikely to trigger for the wrong skill.	5 / 5
	Total	17 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (813 lines); consider splitting into references/ and linking	Warning
metadata_version	'metadata.version' is missing	Warning

	Total	14 / 16 Passed

Repository: affaan-m/ECC
Path: skills/quarkus-tdd/SKILL.md
Revision: d2ef268

Reviewed: 2 months ago

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.

quarkus-tdd

Table of Contents

Is this your skill?