Redis Observability
redis/agent-skills
Redis observability guidance — which metrics to monitor (memory, connections, hit ratio, ops/sec, rejected connections), which built-in commands to reach for during incident triage (SLOWLOG, INFO…
A skill your agent uses when you need to implement or improve Java metrics observability with Micrometer — including meter design, naming/tag conventions, cardinality control…
Install 182 Java Observability Metrics Micrometer
$ npx skills add jabrena/plinth --skill 182-java-observability-metrics-micrometer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jabrena/plinth 182-java-observability-metrics-micrometer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/182-java-observability-metrics-micrometer .claude/skills/182-java-observability-metrics-micrometer && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "182-java-observability-metrics-micrometer" agent skill from https://github.com/jabrena/plinth/tree/main/skills/182-java-observability-metrics-micrometer into .claude/skills/182-java-observability-metrics-micrometer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "182-java-observability-metrics-micrometer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jabrena/plinth/tree/main/skills/182-java-observability-metrics-micrometerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jabrena/plinth --skill 182-java-observability-metrics-micrometer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jabrena/plinth 182-java-observability-metrics-micrometer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/182-java-observability-metrics-micrometer .agents/skills/182-java-observability-metrics-micrometer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "182-java-observability-metrics-micrometer" agent skill from https://github.com/jabrena/plinth/tree/main/skills/182-java-observability-metrics-micrometer into .agents/skills/182-java-observability-metrics-micrometer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "182-java-observability-metrics-micrometer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jabrena/plinth --skill 182-java-observability-metrics-micrometer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jabrena/plinth 182-java-observability-metrics-micrometer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/182-java-observability-metrics-micrometer .cursor/skills/182-java-observability-metrics-micrometer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "182-java-observability-metrics-micrometer" agent skill from https://github.com/jabrena/plinth/tree/main/skills/182-java-observability-metrics-micrometer into .cursor/skills/182-java-observability-metrics-micrometer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "182-java-observability-metrics-micrometer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jabrena/plinth.git --path skills/182-java-observability-metrics-micrometer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jabrena/plinth --skill 182-java-observability-metrics-micrometer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jabrena/plinth 182-java-observability-metrics-micrometer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/182-java-observability-metrics-micrometer .gemini/skills/182-java-observability-metrics-micrometer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "182-java-observability-metrics-micrometer" agent skill from https://github.com/jabrena/plinth/tree/main/skills/182-java-observability-metrics-micrometer into .gemini/skills/182-java-observability-metrics-micrometer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "182-java-observability-metrics-micrometer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jabrena/plinth 182-java-observability-metrics-micrometerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jabrena/plinth --skill 182-java-observability-metrics-micrometer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/182-java-observability-metrics-micrometer .github/skills/182-java-observability-metrics-micrometer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "182-java-observability-metrics-micrometer" agent skill from https://github.com/jabrena/plinth/tree/main/skills/182-java-observability-metrics-micrometer into .github/skills/182-java-observability-metrics-micrometer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "182-java-observability-metrics-micrometer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jabrena/plinth --skill 182-java-observability-metrics-micrometer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jabrena/plinth 182-java-observability-metrics-micrometer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/182-java-observability-metrics-micrometer .opencode/skills/182-java-observability-metrics-micrometer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "182-java-observability-metrics-micrometer" agent skill from https://github.com/jabrena/plinth/tree/main/skills/182-java-observability-metrics-micrometer into .opencode/skills/182-java-observability-metrics-micrometer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "182-java-observability-metrics-micrometer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
182-java-observability-metrics-micrometer- GitHub stars
- 446
- Token cost
- ~868 tokens
- SKILL.md length
- 317 words
- Files
- 2 (incl. references)
- Skills in repo
- 124
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
A skill your agent uses when you need to implement or improve Java metrics observability with Micrometer — including meter design, naming/tag conventions, cardinality control…
- You need to implement
- SKILL.md covers Constraints, When to use this skill, Workflow and Reference
- Calls mvn
- Improve Java metrics observability with Micrometer — including meter design
What it does
182 Java Observability Metrics Micrometer is an agent skill from jabrena/plinth. 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
Its SKILL.md is about 870 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/182-java-observability-metrics-micrometer.md`).
It sits in DevOps & Cloud, covering Observability and Monitoring and alerting. It works with Java and Prometheus. The repository describes itself as: Plinth is an AI-native engineering toolkit for modern Java enterprise SDLC, built around reusable Commands, Agents, Skills, and MCP Servers. The licence is Apache-2.0.
When your agent uses it
- You need to implement
- Improve Java metrics observability with Micrometer — including meter design
- Naming/tag conventions
- Cardinality control
Example prompts
- “/182-java-observability-metrics-micrometer”
What it can do on your machine
Read from SKILL.md and the folder at commit dca88dc. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
mvn
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
182 Java Observability Metrics Micrometer loads about 868 tokens when it runs, and up to ~4.8k if it reads all its reference files. Until then it costs about 140 tokens; SKILL.md has 317 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from jabrena/plinth at commit dca88dc, republished under its Apache-2.0 licence (© jabrena). 317 words, ~868 tokens.
Download SKILL.mdSave it as
.claude/skills/182-java-observability-metrics-micrometer/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- 182-java-observability-metrics-micrometer
- description
- 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
- license
- Apache-2.0
- metadata.author
- Juan Antonio Breña Moral
- metadata.version
- 0.19.0
Java Metrics Observability with Micrometer
Implement effective Java metrics instrumentation with Micrometer by defining meaningful service-level metrics, controlling cardinality, selecting the right meter type, and exposing production-ready telemetry for dashboards and alerting.
What is covered in this Skill?
- Metrics-first observability with Micrometer in Java applications
- Meter selection: Counter, Timer, DistributionSummary, Gauge, LongTaskTimer
- Naming and tagging conventions with low-cardinality dimensions
- Cardinality and meter lifecycle safeguards to prevent time-series explosion
- Histogram/percentile strategy and SLO-oriented metrics design
- Integration guidance for Actuator + Prometheus/OpenTelemetry pipelines
- Testing and verification of metrics registration and values
Scope: Application-level metrics design and instrumentation quality for Java services, with emphasis on operationally useful and cost-efficient telemetry.
Constraints
Metrics instrumentation must be operationally safe, low-cardinality, and validated. Poor tag design or excessive meter creation can degrade observability systems and increase costs.
- LOW CARDINALITY FIRST: Never tag metrics with unbounded values (userId, UUID, raw URL, full exception message)
- RIGHT METER TYPE: Use Counter for monotonically increasing events, Timer for latency, Gauge for point-in-time state, and DistributionSummary for sampled values
- BEFORE APPLYING: Read the reference for good/bad instrumentation examples and anti-patterns
- VERIFY: Run
./mvnw clean verifyormvn clean verifyafter changes
When to use this skill
- Improve metrics
- Apply Micrometer
- Add metrics observability
- Refactor Micrometer instrumentation
- Add Micrometer timers counters or gauges to Java services
Workflow
- Define measurement goals and meter contract
Identify key service indicators (throughput, latency, error ratio, saturation) and map each to stable metric names, units, and low-cardinality tags.
- Select meter types and instrument code paths
Apply Counter/Timer/Gauge/DistributionSummary/LongTaskTimer where appropriate, ensuring consistent naming conventions and reusable tags.
- Harden instrumentation for production
Control cardinality, avoid dynamic meter churn, configure histogram/percentile strategy only where needed, and align export settings with the telemetry backend.
- Validate and operationalize metrics
Verify metrics in tests and runtime endpoints, confirm expected labels/units, and ensure dashboards/alerts can consume the emitted series.
Reference
For detailed guidance, examples, and constraints, see references/182-java-observability-metrics-micrometer.md.
© jabrena, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in skills/182-java-observability-metrics-micrometer of jabrena/plinth.
- SKILL.md
- references/182-java-observability-metrics-micrometer.md
Open the folder on GitHubat commit dca88dc
Compare with similar skills
182 Java Observability Metrics Micrometer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| 182 Java Observability Metrics Micrometer this skilljabrena/plinth | 446 | — | ~868 | Automated safety check: Pass | Apache-2.0 | |
| Redis Observabilityredis/agent-skills | 165 | 2 repos | ~911 | Automated safety check: Pass | MIT | |
| Qdrant Advisorqdrant/skills | 253 | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Developing Funboost Mixinydf0509/funboost | 892 | — | ~2.1k | Automated safety check: Pass | None | |
| Archestra Dev Observabilityarchestra-ai/archestra | 4.4k | — | ~1.2k | Automated safety check: Pass | Custom licence | |
| Frontmcp Observabilityagentfront/frontmcp | 146 | — | ~4.6k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
- Official
Qdrant Advisor
qdrant/skills
Diagnose, troubleshoot, and advise on any Qdrant deployment by loading the latest official Qdrant skills live from skills.qdrant.tech.
Developing Funboost Mixin
ydf0509/funboost
当需要为 funboost 创建 Consumer 或 Publisher 的 Mixin 扩展类时使用。触发场景：添加监控、熔断、限流、链路追踪等横切关注点，编写自定义前置/后置处理钩子。关键词：mixin, consumeroverridecls, publisheroverridecls, ConsumerMixin, 自定义消费者, hook, 拦截器, 熔断器, 监控…
Archestra Dev Observability
archestra-ai/archestra
A skill your agent uses when changing Archestra tracing, metrics, OpenTelemetry, Tempo, Grafana, Prometheus, LLM/MCP spans, observability labels, or local observability setup.
Frontmcp Observability
agentfront/frontmcp
A skill your agent uses when adding tracing, structured logging, metrics, or monitoring to a FrontMCP server.
Monitoring Observability
ahmedasmar/devops-claude-skills
Monitoring and observability strategy, implementation, and troubleshooting.
More from jabrena/plinth
All 124 skills in this repo703 Technologies Fuzzing Testing
jabrena/plinth
A skill your agent uses when you need to add or review fuzz testing for Java APIs with CATS — including contract-driven negative testing, malformed payload validation, boundary input exploration, CI…
033 Architecture Diagrams
jabrena/plinth
A skill your agent uses when you need to generate Java project diagrams — including UML sequence diagrams, UML class diagrams, C4 model diagrams, UML state machine diagrams, UML Deployment Diagrams…
112 Java Maven Plugins
jabrena/plinth
A skill your agent uses when you need to add or configure Maven plugins in your pom.xml — including quality tools (enforcer, surefire, failsafe, jacoco, pitest, spotbugs, pmd), security scanning…
151 Java Performance Jmeter
jabrena/plinth
A skill your agent uses when you need to set up JMeter performance testing for a Java project — including creating the run-jmeter.sh script from the exact template, configuring load tests with…
161 Java Profiling Detect
jabrena/plinth
A skill your agent uses when you need to set up Java application profiling to detect and measure performance issues — including trusted preinstalled async-profiler v4.x setup, problem-driven…
001 Commands Inventory
jabrena/plinth
A skill your agent uses when you need to generate a checklist document with embedded commands inventory, following the embedded template exactly and producing INVENTORY-COMMANDS-JAVA.md in the…
Related
Works with
Categories
Questions about 182 Java Observability Metrics Micrometer
What does 182 Java Observability Metrics Micrometer do?
A skill your agent uses when you need to implement or improve Java metrics observability with Micrometer — including meter design, naming/tag conventions, cardinality control…. 182 Java Observability Metrics Micrometer is an agent skill from jabrena/plinth. 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.
When should I use 182 Java Observability Metrics Micrometer?
182 Java Observability Metrics Micrometer fits situations like: you need to implement; improve Java metrics observability with Micrometer — including meter design; naming/tag conventions; cardinality control.
How do I install 182 Java Observability Metrics Micrometer in Claude Code?
Run `npx skills add jabrena/plinth --skill 182-java-observability-metrics-micrometer -a claude-code`. Or copy the skill folder (skills/182-java-observability-metrics-micrometer in jabrena/plinth) into .claude/skills/182-java-observability-metrics-micrometer in your project. Claude Code loads it when a task matches its description.
How do I install 182 Java Observability Metrics Micrometer in Codex?
Run `npx skills add jabrena/plinth --skill 182-java-observability-metrics-micrometer -a codex`. Or copy the skill folder (skills/182-java-observability-metrics-micrometer in jabrena/plinth) into .agents/skills/182-java-observability-metrics-micrometer in your project. Codex loads it when a task matches its description.
Can I use 182 Java Observability Metrics Micrometer in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jabrena/plinth --skill 182-java-observability-metrics-micrometer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/182-java-observability-metrics-micrometer, .gemini/skills/182-java-observability-metrics-micrometer, .github/skills/182-java-observability-metrics-micrometer and .opencode/skills/182-java-observability-metrics-micrometer in your project.
What does 182 Java Observability Metrics Micrometer need to run?
Going by SKILL.md and its folder, 182 Java Observability Metrics Micrometer needs the command-line tools its instructions call (mvn).
Does 182 Java Observability Metrics Micrometer access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is 182 Java Observability Metrics Micrometer safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does 182 Java Observability Metrics Micrometer use?
182 Java Observability Metrics Micrometer is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does 182 Java Observability Metrics Micrometer use?
About 868 tokens (SKILL.md is roughly 3.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.9k tokens, read only when the agent opens those files.
What are the alternatives to 182 Java Observability Metrics Micrometer?
Skills that share tags, products or a category with 182 Java Observability Metrics Micrometer: Redis Observability (redis/agent-skills, 165 stars), Qdrant Advisor (qdrant/skills, 253 stars), Developing Funboost Mixin (ydf0509/funboost, 892 stars) and Archestra Dev Observability (archestra-ai/archestra, 4.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains 182 Java Observability Metrics Micrometer?
jabrena (a GitHub user) maintains it in jabrena/plinth, which has 446 GitHub stars. The repository holds 124 skills in this directory. The repository was last updated on October 7, 2026.
Source: jabrena/plinth on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.