S Skillteca
Receber por email
Explorar Categorias Coleções Newsletter
← Voltar para o catálogo

otel-expert

Segurança Autor: aiskillstore

Use this when working with OpenTelemetry, telemetry, observability, traces, spans, metrics, logs, OTLP, semantic conventions, or instrumentation. Triggers on questions like "what attributes should I use", "how do I configure the collector", "what's the semconv for X".

367estrelas
Atualizado há 4 meses
Ver no GitHub ↗

Como adicionar

/plugin marketplace add aiskillstore/marketplace

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/otel-expert/svg)](https://www.skillteca.com.br/skills/otel-expert)

Skills relacionadas

Ver todas de Segurança →

security-research

63k

Habilidade de pesquisa de segurança em Modo Equipe que orquestra 3 caçadores de vulnerabilidades e 2 engenheiros de PoC para auditar um código, provar explorabilidade, classificar causas raiz e calibrar a severidade. É utilizada para revisão de segurança, pesquisa de vulnerabilidades, auditoria de explorabilidade e validação de modelo de ameaças.

Segurança por code-yeongyu

security-scanning-security-dependencies

41.2k

You are a security expert specializing in dependency vulnerability analysis, SBOM generation, and supply chain security. Scan project dependencies across multiple ecosystems to identify vulnerabilities, assess risks, and provide automated remediation strategies.

Segurança #ai #git por sickn33

vulnerability-scanner

41.2k

Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.

Segurança #ai #git por sickn33

dependency-management-deps-audit

41.2k

You are a dependency security expert specializing in vulnerability scanning, license compliance, and supply chain security. Analyze project dependencies for known vulnerabilities, licensing issues, outdated packages, and provide actionable remediation strategies.

Segurança #ai #git por sickn33

Alerta por categoria

Receba novas skills de Segurança toda segunda

1 email curto, só com as skills novas de Segurança. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

OpenTelemetry Expert

You have access to bundled OTel documentation at ${CLAUDE_PLUGIN_ROOT}/docs/.

How to Answer OTel Questions

  1. Check INDEX.md first - It maps topics to files
  2. Check SYNC-REPORT.md - For any validation warnings
  3. Search with Grep - Find specific attributes, config keys, or concepts
  4. Read the relevant file - Get full context before answering
  5. Cite the source - Reference which doc the answer came from

Priority Sources

  • Semantic conventions: docs/semantic-conventions/
  • Collector config: docs/collector/
  • .NET instrumentation: docs/instrumentation/dotnet.md
  • Protocol/OTLP: docs/protocol/

Search Strategy

# Find attribute definitions
Grep pattern="attribute_name" path="${CLAUDE_PLUGIN_ROOT}/docs/semantic-conventions/"

# Find collector config
Grep pattern="processor|exporter|receiver" path="${CLAUDE_PLUGIN_ROOT}/docs/collector/"

# Find .NET examples
Grep pattern="ActivitySource|Meter|Logger" path="${CLAUDE_PLUGIN_ROOT}/docs/instrumentation/"

Constraints

  • Latest stable semconv only (no deprecated attributes)
  • .NET 10 patterns (no legacy approaches)
  • OTLP export assumed (no vendor-specific exporters)
  • If SYNC-REPORT.md shows warnings, mention them to the user

Response Format

When answering OTel questions:

  1. Direct answer - What the user asked
  2. Attributes table - If applicable (name, type, description)
  3. Code example - .NET 10 syntax preferred
  4. Source reference - Which doc file the answer came from
Compartilhar X LinkedIn