spring-boot-actuator
Configure Spring Boot Actuator for production-grade monitoring, health probes, secured management endpoints, and Micrometer metrics across JVM services.
Install with Tessl CLI
npx tessl i github:giuseppe-trisciuoglio/developer-kit --skill spring-boot-actuatorOverall
score
86%
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
68%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description excels at specificity and distinctiveness, clearly identifying the Spring Boot Actuator domain with concrete capabilities. However, it lacks an explicit 'Use when...' clause which limits its completeness score, and could benefit from additional natural trigger terms that users might actually say when needing this skill.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when configuring actuator endpoints, setting up health checks, or implementing metrics in Spring Boot applications'
Include additional natural trigger terms users might say: 'actuator endpoints', '/health endpoint', '/metrics', 'application observability', 'Spring Boot monitoring'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Configure Spring Boot Actuator', 'production-grade monitoring', 'health probes', 'secured management endpoints', and 'Micrometer metrics across JVM services'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what does this do' with specific capabilities, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The when is only implied through the technical domain. | 2 / 3 |
Trigger Term Quality | Includes relevant technical terms like 'Spring Boot Actuator', 'health probes', 'Micrometer metrics', 'JVM services', but missing common user variations like 'actuator endpoints', 'application health', 'metrics endpoint', '/health', '/metrics', or 'observability'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly specific to Spring Boot Actuator ecosystem with distinct triggers like 'Actuator', 'Micrometer', 'JVM services'. Unlikely to conflict with generic monitoring or other framework-specific skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exemplary skill file that demonstrates excellent token efficiency while providing comprehensive, actionable guidance for Spring Boot Actuator configuration. The content is well-structured with clear workflows, executable code examples at multiple complexity levels, and appropriate delegation to reference materials. The validation checklist ensures Claude can verify successful implementation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of concepts Claude already knows (no explanation of what Actuator is or how Spring Boot works). Every section provides actionable configuration without padding. | 3 / 3 |
Actionability | Provides fully executable code examples including Maven/Gradle dependencies, complete YAML configurations, and working Java code for security configuration and custom health indicators. All examples are copy-paste ready. | 3 / 3 |
Workflow Clarity | The Implementation Workflow section provides a clear 5-step sequence with explicit validation checkpoints. The Validation Checklist at the end provides concrete verification steps to confirm correct implementation before production deployment. | 3 / 3 |
Progressive Disclosure | Excellent structure with a concise overview, quick start, and graduated examples (Basic → Intermediate → Advanced). References are clearly signaled and one level deep, pointing to specific files in references/ directory for detailed documentation. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
69%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 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 |
Total | 11 / 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.