CtrlK
BlogDocsLog inGet started
Tessl Logo

springboot-verification

Spring Boot 项目的验证循环:构建、静态分析、带有覆盖率的测试、安全扫描以及发布或 PR 前的差异审查。

69

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-3

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

The body is a tight, highly actionable verification runbook with clearly sequenced phases, explicit checkpoints, and a concrete output template. It respects Claude's competence and needs no external references for its scope.

DimensionReasoningScore

Conciseness

Lean and efficient — mostly runnable commands and terse checklists with no padding explaining what Spring Boot, Maven, or coverage is; every token earns its place.

3 / 3

Actionability

Provides concrete, copy-paste-ready mvn/gradlew commands for each phase plus a fill-in output report template, leaving nothing abstract.

3 / 3

Workflow Clarity

A clear six-phase sequence with an explicit checkpoint ('如果构建失败,请停止并修复问题'), a coverage gate, and a diff-review checklist that serves as validation feedback.

3 / 3

Progressive Disclosure

A single self-contained, well-organized file under 100 lines with no need for external references, which meets the simple-skill allowance for full marks.

3 / 3

Total

12

/

12

Passed

Description

67%Weight 40%Scale 1-3

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 and well-scoped to a Spring Boot verification loop, but it omits an explicit 'Use when...' trigger clause and relies on technical jargon over natural user phrasing. Adding explicit trigger guidance would lift the completeness and trigger-term dimensions.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use before opening a PR, after major changes, or before deploying a Spring Boot project.'

Broaden trigger terms with natural user phrasings such as 'run tests', 'check coverage', 'security scan', or 'CI checks' in addition to the current technical terms.

Keep the third-person voice (currently consistent) while folding in a brief 'when' clause to satisfy both what and when.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 构建, 静态分析, 带有覆盖率的测试, 安全扫描, 差异审查 — rather than vague language.

3 / 3

Completeness

Clearly states what the skill does, but the 'when' is only implied via '发布或 PR 前' with no explicit 'Use when...' trigger clause, which caps completeness at 2.

2 / 3

Trigger Term Quality

Includes relevant domain terms (验证循环, 覆盖率, 安全扫描, PR) but leans on technical jargon and lacks common natural phrasings a user would actually say.

2 / 3

Distinctiveness Conflict Risk

The Spring Boot verification-loop niche is clearly scoped with distinct triggers and is unlikely to fire for unrelated skills.

3 / 3

Total

10

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
xu-xiang/everything-claude-code-zh
Reviewed

Table of Contents

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.