Claude Code plugins
32 plugins from public Claude Code marketplaces. Each one bundles skills, slash commands, agents, hooks or MCP servers that install together.
Showing 32 plugins that match these filters.
32 plugins from public Claude Code marketplaces. Each one bundles skills, slash commands, agents, hooks or MCP servers that install together.
Showing 32 plugins that match these filters.
Submit the repo with .claude-plugin/marketplace.json and we list every plugin.
Submit marketplaceCLI toolbox for Observability-Driven Development (ODD): coding agents observe local runs on an OpenTelemetry/Grafana stack - or remote ones on any OpenTelemetry backend - and feed the next spec-driven improvement loop.
observabilityDistributed tracing tests with OpenTelemetry: assert span names, attributes, parent links and status, and query Jaeger, Zipkin or Tempo in CI. Validates OpenTelemetry Collector pipelines and writes per-feature trace specs. A review agent (trace-coverage-reviewer) finds untraced critical paths and spans missing semantic-convention attributes.
backend-distributedLLM observability with Langfuse — OpenTelemetry-based tracing, evaluations, prompt management, datasets, and production best practices
Operate the observability stack that deploys as one unit: Prometheus scrape configuration, recording and alerting rules, relabeling, retention, and high availability; OpenTelemetry Collector pipelines (receivers, processors, exporters, sampling, trace/span correlation); and Loki ingest, LogQL, retention, and label design — with a bundled read-only telemetry-check script for Prometheus rule sanity and scrape-target reachability. Use when running, tuning, or troubleshooting a Prometheus, OpenTelemetry Collector, or Loki deployment, or reviewing the collection/ingest/retention layer, including bounded PromQL and LogQL query construction, semantic review, and no-data diagnosis. Do not use for observability strategy, SLI/SLO design, or paging policy (that is platform-engineering), Grafana dashboards, panels, and Grafana-side alerting (that is grafana), or Tempo/tracing operations, which remain deferred to a future named-tool skill.
Use when you need to implement or improve distributed tracing with OpenTelemetry in Java — including trace/span modeling, context propagation, semantic conventions, span attributes/events/status, sampling strategy, baggage usage, privacy safeguards, and backend integration with OTLP collectors.
OpenTelemetry skills and reference documentation for AI coding assistants
instrumentationOpinionated guidance for clear and operationally useful OpenTelemetry instrumentation.
instrumentationVendor-neutral OpenTelemetry skills for AI coding agents, grounded in upstream sources: SDK setup per language, the Collector and OCB, OTTL, declarative configuration, semantic conventions, upgrades and migrations.
instrumentationOpenTelemetry signal quality with durable workflows and fresh, version-correct upstream evidence.
instrumentationOpenTelemetry skills for naming metrics and spans following OTel Semantic Conventions
instrumentationCLI toolbox for Observability-Driven Development (ODD): coding agents observe local runs on an OpenTelemetry/Grafana stack - or remote ones on any OpenTelemetry backend - and feed the next spec-driven improvement loop.
observabilityFind why an HTTP endpoint is slow and prove a fix: ping it by phase, load-test it, see which operation inside the service the time goes to (from its OpenTelemetry spans), and compare before and after. A skill and pepe's MCP server, under guardrails.
observabilityOpenTelemetry Collector component configuration: config keys, defaults, validation rules, signal support, stability, and gotchas. Progressive disclosure via components/<name>/README.md plus on-demand detail files.
Building custom OpenTelemetry Collector distributions with OCB: builder manifest authoring, core/contrib/provider version alignment, local component development, CI/Docker/multi-arch builds, and troubleshooting.
OpenTelemetry declarative YAML configuration for SDK setup (otelconf, OTEL_CONFIG_FILE, file_format). Points at upstream schema, env-var substitution, and configuration precedence.
OpenTelemetry Transformation Language (OTTL) expert for writing and debugging telemetry transformations in the Collector (transform, filter, routing, tail_sampling).
OpenTelemetry profiles signal and the eBPF profiler: deploying otelcol-ebpf-profiler on hosts and Kubernetes (including kind/k3d), version-pinned receiver keys, exporting OTLP profiles to backends, verification, and troubleshooting.
OpenTelemetry SDK, Collector, configuration schema, semantic conventions, and Weaver release version lookup.
OpenTelemetry semantic convention lookup and naming guidance for attributes, groups, and span naming.
Migrate OpenTelemetry Span Events (AddEvent, RecordException) to the Logs API following the OTEP 4430 deprecation plan.