quarkus-verification

Verification loop for Quarkus projects: build, static analysis, tests with coverage, security scans, native compilation, and diff review before release or PR.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/quarkus-verification/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.

A thorough, highly actionable verification playbook with a clear phased workflow and executable examples throughout. Its main weaknesses are length/padding and a lack of progressive disclosure — much of the reference-grade material is inlined in one large file.

Suggestions

Move the detailed Java test examples (unit/integration/API), the K6 load-test script, and the full GitHub Actions YAML into separate reference files under references/, keeping SKILL.md as a concise overview that links to them.

Trim generic-knowledge sections such as 'Common Issues to Address' and 'Best Practices' down to Quarkus-specific guidance Claude would not already know.

Add explicit per-phase feedback loops (e.g., 'If dependency-check reports CVEs: <action>; if native build fails: <recovery steps>') so error recovery is as concrete as the build phase.

Dimension	Reasoning	Score
Conciseness	The ~480-line body is mostly efficient commands and code, but sections like 'Common Issues to Address', 'Best Practices', and the generic environment/documentation checklists restate knowledge Claude already has and could be trimmed.	3 / 5
Actionability	Provides copy-paste ready mvn/gradle/docker/k6 commands, complete executable Java test examples, and a full GitHub Actions YAML, covering the common verification cases concretely.	5 / 5
Workflow Clarity	Ten numbered phases give a clear sequence with explicit checkpoints ('If build fails, stop and fix', jacoco:check, set -e) and checklists, but per-phase feedback loops (what to do when security scans or native build fail) are only partially spelled out.	4 / 5
Progressive Disclosure	Sections are well-organized, but the skill is a monolithic ~480-line single file with no bundle references; detailed Java test examples, the K6 load test, and the full CI/CD YAML are inlined where separate reference files would aid navigation.	3 / 5
	Total	15 / 20 Passed

Description

83%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 names concrete verification actions and an explicit trigger ('before release or PR'), with a clear Quarkus niche. It could be improved by broadening the trigger phrases to match more natural user phrasings.

Dimension	Reasoning	Score
Specificity	Lists six concrete, specific actions — 'build, static analysis, tests with coverage, security scans, native compilation, and diff review' — giving comprehensive coverage of the verification domain rather than vague abstractions.	5 / 5
Completeness	Clearly states what the skill does (the enumerated actions) and gives explicit when-guidance ('before release or PR'), but the when clause could be more comprehensive — the body mentions 'after major refactoring or dependency upgrades' which is absent from the description.	4 / 5
Trigger Term Quality	Contains natural terms a user would say ('Quarkus projects', 'build', 'security scans', 'native compilation', 'PR', 'release'), but misses common synonyms such as 'CI/CD', 'QA', or 'lint' that a user might naturally invoke.	4 / 5
Distinctiveness Conflict Risk	The 'Quarkus projects' niche and native-compilation/coverage-threshold triggers are highly specific, making conflict with unrelated skills minimal.	5 / 5
	Total	18 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: skills/quarkus-verification/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.