spring-boot-dependency-injection
Dependency injection workflow for Spring Boot projects covering constructor-first patterns, optional collaborator handling, bean selection, and validation practices.
Install with Tessl CLI
npx tessl i github:giuseppe-trisciuoglio/developer-kit --skill spring-boot-dependency-injectionOverall
score
67%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
33%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 identifies a clear technical domain (Spring Boot dependency injection) and lists relevant subtopics, but lacks actionable specificity and completely omits trigger guidance. Without a 'Use when...' clause, Claude cannot reliably determine when to select this skill over other Spring or Java-related skills.
Suggestions
Add an explicit 'Use when...' clause with trigger scenarios like 'Use when configuring Spring beans, setting up @Autowired dependencies, or resolving injection issues'
Include common user terms and variations: '@Autowired', 'DI', 'IoC container', 'bean wiring', 'inject dependencies'
Convert category names to concrete actions: 'Configure constructor injection, handle optional dependencies with @Nullable, select beans with @Qualifier'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Spring Boot dependency injection) and lists several areas (constructor-first patterns, optional collaborator handling, bean selection, validation practices), but these are categories rather than concrete actions like 'configure', 'inject', or 'resolve'. | 2 / 3 |
Completeness | Describes what the skill covers (dependency injection patterns) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant technical terms like 'dependency injection', 'Spring Boot', 'constructor', 'bean selection' that users might mention, but misses common variations like '@Autowired', 'DI', 'IoC', 'wiring', or 'inject dependencies'. | 2 / 3 |
Distinctiveness Conflict Risk | The Spring Boot + dependency injection focus provides some distinctiveness, but could overlap with general Spring skills, Java configuration skills, or broader backend development skills without clearer boundaries. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with strong actionability through executable code examples and clear workflow progression. The progressive disclosure is excellent with appropriate references to supporting materials. Minor verbosity in introductory sections and some workflow descriptions could be trimmed to improve token efficiency.
Suggestions
Remove or condense the introductory paragraph ('This skill captures...') as it restates what the Overview section already covers
Tighten the 'When to Use' section to bullet points without full sentences (e.g., 'New @Service/@Component/@Repository classes' instead of 'Implement constructor injection for new...')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some unnecessary explanation (e.g., 'This skill captures the dependency injection approach promoted in this repository' preamble, verbose workflow descriptions). Some sections could be tightened while preserving clarity. | 2 / 3 |
Actionability | Provides fully executable Java code examples at multiple complexity levels (basic, intermediate, advanced), with concrete annotations, patterns, and copy-paste ready implementations. Clear guidance on what to do in each scenario. | 3 / 3 |
Workflow Clarity | The 5-step workflow is clearly sequenced with explicit validation step (Step 5), progression from mapping to implementation to testing, and references to supporting materials at each stage. Includes feedback loop through unit tests before integration tests. | 3 / 3 |
Progressive Disclosure | Excellent structure with clear overview, well-organized sections, and one-level-deep references to supporting files (references/reference.md, references/examples.md, references/spring-official-dependency-injection.md). Navigation is intuitive with specific anchors for detailed topics. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
63%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 10 / 16 Passed | |
- 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.