Designs OpenTelemetry Collector pipeline configurations with receivers (otlp, prometheus, filelog), processors (batch, attributes, tail_sampling), and exporters (otlphttp, jaeger, elasticsearch).
Scanned 6/8/2026
Install via CLI
openskills install agentskillexchange/skills---
name: "OpenTelemetry Collector Pipeline Designer"
slug: "otel-collector-pipeline-designer"
description: "Designs OpenTelemetry Collector pipeline configurations with receivers (otlp, prometheus, filelog), processors (batch, attributes, tail_sampling), and exporters (otlphttp, jaeger, elasticsearch)."
github_stars: 6867
verification: "security_reviewed"
source: "https://github.com/open-telemetry/opentelemetry-collector"
author: "OpenTelemetry"
category: "Monitoring & Alerts"
framework: "OpenClaw"
tool_ecosystem:
github_repo: "open-telemetry/opentelemetry-collector"
github_stars: 6867
---
# OpenTelemetry Collector Pipeline Designer
Designs OpenTelemetry Collector pipeline configurations with receivers (otlp, prometheus, filelog), processors (batch, attributes, tail_sampling), and exporters (otlphttp, jaeger, elasticsearch).
## Prerequisites
Go
## Installation
Requirements and caveats from upstream:
- [{"critical":{"identity":{"docker-reference":"ghcr.io/open-telemetry/opentelemetry-collector-releases/opentelemetry-collector-contrib"},"image":{"docker-manifest-digest":"sha256:5cea85bcbc734a3c0a641368e5a4ea9d31b4729...
- In addition to what is described at the organization-level, the SIG Collector requires all core approvers to take part in rotating
Basic usage or getting-started notes:
- to run, operate and maintain multiple agents/collectors in order to support
- We are signing the images otel/opentelemetry-collector and otel/opentelemetry-collector-contrib using [sigstore cosign](https://github.com/sigstore/cosign) tool and to verify the signatures you can run the following c...
- Example:
- Source: https://github.com/open-telemetry/opentelemetry-collector
- Extracted from upstream docs: https://raw.githubusercontent.com/open-telemetry/opentelemetry-collector/HEAD/README.md
## Documentation
- https://opentelemetry.io/docs/collector/
## Source
- [Agent Skill Exchange](https://agentskillexchange.com/skills/otel-collector-pipeline-designer/)
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.