182-java-observability-metrics-micrometer

Use when you need to implement or improve Java metrics observability with Micrometer — including meter design, naming/tag conventions, cardinality control, timers/counters/gauges/distribution summaries, percentiles/histograms, Actuator/Prometheus integration, and metrics validation through tests. This should trigger for requests such as Improve metrics; Apply Micrometer; Add metrics observability; Refactor Micrometer instrumentation; Add Micrometer timers counters or gauges to Java services. Part of Plinth Toolkit

Quality

85%

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

78%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 well-structured, concise overview with clean progressive disclosure and a clear workflow. Its main weakness is actionability: the body offers declarative guidance and a verify command but no executable instrumentation examples in-line, deferring concrete code to the reference.

Suggestions

Add one small copy-paste Micrometer code snippet in the body (e.g., registering a Timer with low-cardinality tags) so the core instrumentation step is executable without opening the reference.

Make the workflow's validate→fix→retry loop explicit (e.g., 'If verify fails, fix the reported meter/tag issue and re-run verify') to reach a 5 on workflow clarity.

Include a one-line example of correct vs. incorrect tagging to ground the 'LOW CARDINALITY FIRST' constraint in concrete code.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — it states meter-type selection rules and constraints without explaining what Micrometer or Java metrics are, and every section earns its place.	5 / 5
Actionability	Guidance is mostly declarative ('Use Counter for monotonically increasing events', 'Never tag metrics with unbounded values') with only one concrete executable command ('./mvnw clean verify' / 'mvn clean verify'); it lacks copy-paste instrumentation code in the body and delegates specifics to the reference, leaving key execution details implicit.	3 / 5
Workflow Clarity	A clear four-step numbered workflow with named phases and an explicit VERIFY checkpoint ('Run ./mvnw clean verify or mvn clean verify after changes'), though the validate→fix→retry feedback loop is only implicit rather than spelled out.	4 / 5
Progressive Disclosure	SKILL.md is a concise overview with well-organized sections and a single clearly-signaled one-level-deep reference ('see references/182-java-observability-metrics-micrometer.md') that exists as a real bundle file, making navigation easy.	5 / 5
	Total	17 / 20 Passed

Description

92%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, specific description that clearly states both capability and trigger conditions with concrete natural-language phrases. Minor room to broaden trigger-term synonyms, but overall it is comprehensive and distinctive.

Dimension	Reasoning	Score
Specificity	The description enumerates many concrete capabilities — 'meter design, naming/tag conventions, cardinality control, timers/counters/gauges/distribution summaries, percentiles/histograms, Actuator/Prometheus integration, and metrics validation through tests' — giving comprehensive, specific coverage rather than vague language.	5 / 5
Completeness	It explicitly answers 'what' (implement/improve Java metrics observability with Micrometer, including the enumerated capabilities) and 'when' via both 'Use when you need to...' and 'This should trigger for requests such as...' with concrete trigger phrases.	5 / 5
Trigger Term Quality	It lists natural user phrases ('Improve metrics; Apply Micrometer; Add metrics observability; Refactor Micrometer instrumentation; Add Micrometer timers counters or gauges') with good synonym coverage, though a few common variations or file/library extensions are missing, keeping it just below a 5.	4 / 5
Distinctiveness Conflict Risk	The combination of Java + Micrometer + metrics with operationally specific triggers carves a clear niche with minimal overlap risk against other skills.	5 / 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: jabrena/plinth
Path: skills/182-java-observability-metrics-micrometer/SKILL.md
Commit: 05bf9d1

Reviewed: 4 minutes 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.