springboot-verification

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

Quality

72%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/springboot-verification/SKILL.md

Quality

Content

77%

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

A highly actionable, well-sequenced verification skill with strong workflow gating, though it leans long by inlining lengthy Java test examples Claude already knows. Splitting reference material into bundled files would improve token efficiency and progressive disclosure.

Suggestions

Move the three full Java test snippets (unit, Testcontainers, MockMvc) into a references file (e.g. references/test-patterns.java) and keep only a one-line pointer plus the key assertion pattern in SKILL.md.

Extract the security grep patterns and common-findings checks into a references/security-checks.md file, summarizing the intent inline.

Trim incidental commentary like 'Test against a real database instead of H2' which restates concepts Claude already knows.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but the full Java unit/integration/MockMvc test examples are lengthy reference-style material that Claude already knows and could be moved to a bundled reference.	2 / 3
Actionability	Every phase provides concrete, copy-paste-ready commands and complete executable Java snippets, plus a filled-in output report template.	3 / 3
Workflow Clarity	Six phases are explicitly sequenced with an early 'If build fails, stop and fix' checkpoint, a diff-review checklist, and a final READY/NOT READY gate with feedback looping.	3 / 3
Progressive Disclosure	Well-organized into clear sections, but everything is inline in one file with no bundle references; the detailed test examples and security grep patterns would benefit from being split into reference files.	2 / 3
	Total	10 / 12 Passed

Description

67%

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 clearly scopes the skill to Spring Boot verification, but it lacks an explicit 'Use when...' trigger clause that would lift completeness and trigger-term quality. Adding natural-language trigger phrasing would round it out.

Suggestions

Append an explicit 'Use when...' clause naming common user requests (e.g. 'Use before opening a PR, after refactoring, or when the user asks to verify or run CI checks on a Spring Boot service').

Add user-natural trigger terms like 'verify', 'run CI checks', 'pre-deploy gate', or 'check my Spring Boot app' to improve trigger-term quality.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'build, static analysis, tests with coverage, security scans, and diff review' — each a specific verification activity rather than vague language.	3 / 3
Completeness	It clearly states what the skill does but has no 'Use when...' clause; the 'before release or PR' phrase only implicitly conveys when to invoke it.	2 / 3
Trigger Term Quality	Includes natural terms like 'build', 'tests', 'security scans', 'PR', and 'release', but lacks common user phrasings such as 'verify my Spring Boot app' or 'run the CI gate'.	2 / 3
Distinctiveness Conflict Risk	Scoped narrowly to Spring Boot verification with a distinct pipeline (build/static/tests/security/diff), making it unlikely to trigger for unrelated skills.	3 / 3
	Total	10 / 12 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
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.