Fetches spring-boot-actuator from giuseppe-trisciuoglio/developer-kit and configures it for Cursor.
3
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/spring-boot-actuator
Restart Cursor to activate spring-boot-actuator. Access via /spring-boot-actuator in your agent's command palette.
⚠
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Include spring-boot-starter-actuator in your build configuration.
Validate: Restart the service and confirm /actuator/health and /actuator/info respond with 200 OK.
2. Expose Required Endpoints
Set management.endpoints.web.exposure.include to the precise list or "*" for internal deployments.
Adjust management.endpoints.web.base-path (e.g., /management) when the default /actuator conflicts with routing.
Review detailed endpoint semantics in references/endpoint-reference.md.
Validate: curl http://localhost:8080/actuator returns the list of exposed endpoints.
3. Secure Management Traffic
Apply an isolated SecurityFilterChain using EndpointRequest.toAnyEndpoint() with role-based rules.
Combine management.server.port with firewall controls or service mesh policies for operator-only access.
Keep /actuator/health/** publicly accessible only when required; otherwise enforce authentication.
Validate: Unauthenticated requests to protected endpoints return 401 Unauthorized.
4. Configure Health Probes
Enable management.endpoint.health.probes.enabled=true for /health/liveness and /health/readiness.
Group indicators via management.endpoint.health.group.* to match platform expectations.
Implement custom indicators by extending HealthIndicator or ReactiveHealthContributor; sample implementations in references/examples.md#custom-health-indicator.
Validate: /actuator/health/readiness returns UP with all mandatory components before promoting to production.
5. Publish Metrics and Traces
Activate Micrometer exporters (Prometheus, OTLP, Wavefront, StatsD) via management.metrics.export.*.
Apply MeterRegistryCustomizer beans to add application, environment, and business tags for observability correlation.
Surface HTTP request metrics with server.observation.* configuration when using Spring Boot 3.2+.
Validate: Scrape /actuator/prometheus and confirm required meters (http.server.requests, jvm.memory.used) are present.
6. Enable Diagnostics Tooling
Turn on /actuator/startup (Spring Boot 3.5+) and /actuator/conditions during incident response to inspect auto-configuration decisions.
Register an HttpExchangeRepository (e.g., InMemoryHttpExchangeRepository) before enabling /actuator/httpexchanges for request auditing.
Consult references/endpoint-reference.md for endpoint behaviors and limits.
Validate: /actuator/startup and /actuator/conditions return valid JSON payloads.
Examples
Basic – Expose health and info safely
management:endpoints:web:exposure:include:"health,info"endpoint:health:show-details: never
Intermediate – Readiness group with custom indicator
