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

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No known issues

Quality

Content

77%

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

The content is highly actionable with complete, executable examples and a clear TDD feedback loop, but it is verbose for a single file and lacks progressive disclosure — everything is inline with no reference files despite the large volume. Tightening the repetition and splitting topic-specific code into reference files would raise both weak dimensions.

Suggestions

Move large per-topic code catalogs (Camel route testing, CompletableFuture/async, REST Assured, JaCoCo config) into separate reference files under references/ and link to them from a concise overview, enabling one-level-deep progressive disclosure.

Remove the duplication between the inline "Key Testing Patterns" list and the "Best Practices" section — keep one canonical, brief summary of patterns and let the code examples carry the rest.

Trim or consolidate the "Best Practices" section, which largely restates patterns already demonstrated in the code blocks above.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient, actionable code rather than concept explanations Claude already knows, but it runs ~800 lines with notable repetition — the "Key Testing Patterns" list and the later "Best Practices" section restate the same @Nested/AAA/given-when-then guidance already demonstrated in the code blocks — so it could be tightened and is not level 3.	2 / 3
Actionability	Fully executable, copy-paste-ready code across unit, Camel, event-service, CompletableFuture, REST Assured, and integration tests, plus complete JaCoCo Maven plugin config and test dependencies — matching the level-3 anchor for specific, executable examples.	3 / 3
Workflow Clarity	The TDD workflow is a clearly sequenced red-green-refactor loop ("Write tests first (they should fail)", "Implement minimal code to pass", "Refactor with tests green", "Enforce coverage with JaCoCo (80%+ target)") with an explicit validation checkpoint via `mvn jacoco:check`, satisfying the level-3 anchor for a clear sequence with feedback loops.	3 / 3
Progressive Disclosure	Sections are well-organized, but the skill is a monolithic ~800-line single file with no bundle files (references/, scripts/, assets/ are absent) and no one-level-deep references; large per-topic code sections (Camel routes, CompletableFuture, REST, JaCoCo config) that could live in separate reference files are inline, matching the level-2 anchor of content that should be separate being inline.	2 / 3
	Total	10 / 12 Passed

Description

85%

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 specific, complete, and clearly niche-scoped to Quarkus TDD with an explicit Use-when trigger. The only weakness is trigger-term breadth — common testing phrases users would actually say (writing tests, unit tests, coverage, TDD) are absent.

Suggestions

Add testing-oriented trigger terms a user would naturally say, e.g. "Use when writing unit or integration tests, raising test coverage, or adding features, fixing bugs, or refactoring event-driven services."

Consider mentioning coverage/quality goals in the when-clause (e.g. "enforcing 80%+ coverage") to surface the skill when users ask about test coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete, specific elements — "Test-driven development for Quarkus 3.x LTS using JUnit 5, Mockito, REST Assured, Camel testing, and JaCoCo" — naming both the practice and five specific frameworks, matching the anchor for listing multiple specific concrete actions.	3 / 3
Completeness	Explicitly answers both what ("Test-driven development for Quarkus 3.x LTS using JUnit 5, Mockito, REST Assured, Camel testing, and JaCoCo") and when ("Use when adding features, fixing bugs, or refactoring event-driven services"), matching the level-3 anchor for clear what-and-when with explicit triggers.	3 / 3
Trigger Term Quality	The "Use when adding features, fixing bugs, or refactoring event-driven services" clause provides some natural terms a user would say, but misses common testing-specific variations such as "writing tests", "unit tests", "test coverage", or "TDD", so it is not level 3.	2 / 3
Distinctiveness Conflict Risk	The Quarkus 3.x LTS plus JUnit 5/Mockito/REST Assured/Camel/JaCoCo stack and the event-driven-services trigger carve a clear niche unlikely to fire for non-Quarkus testing skills, matching the level-3 anchor.	3 / 3
	Total	11 / 12 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
Commit: 754b8dd

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