spring-explore

Explores a Spring Boot application and builds primary context: tech stack, module structure, domain entities, REST endpoints. Triggers on explicit requests: "explore project", "describe project", "project overview", "what is this project", "project structure", "tech stack", "give me context about the project", or whenever you need to understand the project before starting any task.

Quality

94%

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

Quality

Content

92%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 high-quality, actionable workflow skill with concrete MCP tool routing, a subagent execution template, report/assumption structures, and an explicit refinement loop. It is lean and avoids padding, with only minor repetitive procedural phrasing.

Suggestions

Collapse the repeated 'Tell the user: Step X/6: ...' and 'Do NOT call any tools in this step' boilerplate into a single stated convention at the top of the Explore section to save tokens.

The Step 1 worked path-evaluation example is long; consider shortening it to the few most instructive include/skip decisions.

Dimension	Reasoning	Score
Conciseness	The body is well-organized and avoids explaining concepts Claude already knows (no Spring Boot primers), but the repeated 'Tell the user: Step X/6...' and 'Do NOT call any tools in this step' lines across nearly every step could be tightened, so minor trimming is possible.	4 / 5
Actionability	Gives fully executable guidance: concrete MCP tool names (get_project_summary, get_entity_details, list_entity_repositories), explicit JPA/JDBC routing rules, a copy-paste subagent prompt template, and worked example plans with parameters — covering the common cases.	5 / 5
Workflow Clarity	Steps 0–6 plus 5.5 are clearly sequenced, each building on the prior, with an explicit feedback loop in Step 6 (score > 80 → return to Step 1, else stop) and a preflight validation that checks for Amplicode tools before proceeding.	5 / 5
Progressive Disclosure	SKILL.md acts as an overview orchestrator with well-signaled, one-level-deep references — all 10 referenced files in references/ exist and are linked via a Step 2 table and inline Step 1 links — keeping detailed MCP procedures split into separate files.	5 / 5
	Total	19 / 20 Passed

Description

96%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, third-person description that explicitly states concrete capabilities and an extensive set of natural trigger phrases. Its only weakness is that several triggers are generic project-overview terms not uniquely tied to Spring Boot.

Suggestions

Tie the generic trigger phrases to Spring Boot to reduce overlap, e.g. 'explore this Spring Boot project' or 'project overview for a Spring application'.

Consider adding the natural term 'Spring' or 'Spring Boot' explicitly among the trigger keywords so it fires only for the intended stack.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete outputs — 'tech stack, module structure, domain entities, REST endpoints' — giving comprehensive coverage of what the skill builds, matching the anchor for several specific concrete actions.	5 / 5
Completeness	Explicitly answers both 'what' (explores Spring Boot app, builds primary context) and 'when' ('Triggers on explicit requests: ... or whenever you need to understand the project before starting any task') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Provides many natural phrases a user would actually say ('explore project', 'describe project', 'project overview', 'what is this project', 'project structure', 'tech stack', 'give me context about the project'), covering synonyms comprehensively.	5 / 5
Distinctiveness Conflict Risk	The Spring Boot framing is a clear niche, but several trigger phrases ('describe project', 'project overview', 'what is this project') are generic and could overlap with non-Spring project-overview skills, so minor overlap risk remains rather than minimal.	4 / 5
	Total	19 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: Amplicode/spring-skills
Path: skills/spring-explore/SKILL.md
Commit: bf19b3c

Reviewed: 5 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.