SKILLEMALL.ai

BC quarkus-verification

Verification loop for Quarkus projects: build, static analysis (Checkstyle, PMD, SpotBugs), tests with JaCoCo coverage, OWASP dependency and container security scans, GraalVM native compilation, health checks, and config validation. Use when verifying a Quarkus service before a PR, after major refactoring or dependency upgrades, or pre-deploy.

affaan-m/everything-claude-code Agent Skills author: affaan-m MIT 1 file body ≈ 2 577 tokens Open the sourcegithub.com↗ analyzed 23 h ago

Verification loop for Quarkus projects: build, static analysis (Checkstyle, PMD, SpotBugs), tests with JaCoCo coverage, OWASP dependency and container…

As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

AnalyzerDockerSoftware developmentData and analyticsSecuritytype and topics are labelled automatically from the skill text
JSON
Technical rating
B
92/100
safety, quality, tests
Safety 60%
98
Quality 40%
82
Run on models
none yet
Process rating
C
51/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: quarkus-verification (affaan-m/everything-claude-code)

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 2

    ✓ No critical or high findings

    Medium and low: 2
    • low Secrets in code secret-high-entropy-token SKILL.md:134
      High-entropy token-like string (may be an id, hash or a credential)
      void crea…201() {
    • low Secrets in code secret-high-entropy-token SKILL.md:147
      High-entropy token-like string (may be an id, hash or a credential)
      void crea…400() {

    Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 51/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 3 mutating operations with no state check
    • 100Tools and files. No external tools needed
    • 100Steps. 72 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2577 tokens
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
    • low 15 top-level sections: this looks like several domains in one skill

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • -2localhost URLs: will not work for another user
    • +1No license
    • +2Single-language instructions
    • +3Description length 345: enough signal without eating the budget
    • +4Structure: 39 headings
    • +3Step-by-step instructions: 72 items
    • +4Has examples (22 code blocks)

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.