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

79%

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 highly actionable with complete, executable examples across the full Quarkus testing stack, but it pays for that breadth in token weight: an ~800-line monolith with duplicated pattern/best-practice lists and no progressive disclosure into reference files.

Suggestions

Move the large per-domain code examples (Camel routes, EventService, FileStorage, REST Assured, integration) into separate reference files under references/ and link to them from SKILL.md to improve progressive disclosure.

De-duplicate the "Key Testing Patterns" list and the "Best Practices" section, which restate the same guidance (@Nested, @DisplayName, givenX_whenY_thenZ, AAA, verify/never).

Add an explicit validation/checklist step to the core workflow (e.g. run `mvn jacoco:check` and only proceed when coverage thresholds pass) to strengthen the feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is roughly 800 lines with substantial duplication between the inline "Key Testing Patterns" list and the later "Best Practices" section, so while content is mostly concrete code rather than conceptual fluff, it could be tightened to reach anchor 4.	3 / 5
Actionability	Provides fully executable, copy-paste-ready code across unit tests, Camel routes, event services, CompletableFuture, REST Assured, integration tests, JaCoCo config, and Maven dependencies, covering the common cases comprehensively.	5 / 5
Workflow Clarity	The TDD workflow is a clear four-step sequence (write failing tests → implement → refactor green → enforce JaCoCo coverage) with the inherent red-green feedback loop, though explicit validation checkpoints beyond "tests green" are thin.	4 / 5
Progressive Disclosure	No bundle files exist and all large code examples are inlined in a single SKILL.md; section headers give reasonable structure, but content that clearly belongs in separate reference files is not split out.	3 / 5
	Total	15 / 20 Passed

Description

87%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.

The description is well-crafted: it pairs a concrete capability statement with an explicit "Use when" trigger clause and a distinctive Quarkus-specific niche. Minor gains would come from richer synonyms or file extensions, but it cleanly answers both what and when.

Dimension	Reasoning	Score
Specificity	Lists several concrete capabilities — "Test-driven development... using JUnit 5, Mockito, REST Assured, Camel testing, and JaCoCo" — naming specific tools, though the underlying action is essentially one (TDD) rather than many distinct actions, so it falls short of the comprehensive anchor 5.	4 / 5
Completeness	Clearly states both what it does ("Test-driven development for Quarkus 3.x LTS using...") and when to use it ("Use when adding features, fixing bugs, or refactoring event-driven services"), with concrete trigger phrases matching the anchor-5 example.	5 / 5
Trigger Term Quality	Includes natural user phrases ("adding features, fixing bugs, or refactoring event-driven services") alongside specific framework names (Quarkus, JUnit 5, Mockito, REST Assured, Camel, JaCoCo), giving good keyword coverage but missing common synonyms or file extensions that would reach anchor 5.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (TDD specifically for Quarkus 3.x LTS event-driven services) with distinct technology triggers, making overlap with other skills minimal.	5 / 5
	Total	18 / 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
Commit: d8409a4

Reviewed: 1 day 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.