← Voltar para o catálogo 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".
Ver no GitHub ↗ Copiar URL do repo Copiar link do SKILL.md Como adicionar Copiar comando /plugin marketplace add aiskillstore/marketplace O comando exato pode variar conforme o repositório. Confira o README no GitHub.
Para o autor da skill
Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.
Markdown HTML
[](https://www.skillteca.com.br/skills/otel-expert?utm_source=badge&utm_medium=readme&utm_campaign=badge) Copiar snippet 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
Provide a comprehensive, structured reference for the 100 most critical web application vulnerabilities organized by category. This skill enables systematic vulnerability identification, impact assessment, and remediation guidance across the full spectrum of web security threats.
Segurança #github #git por sickn33
Orchestrate multiple Antigravity skills through guided workflows for SaaS MVP delivery, security audits, AI agent builds, and browser QA.
Segurança #github #git por sickn33
Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.
Segurança #github #git por sickn33
Alerta por categoria
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.
OpenTelemetry Expert
You have access to bundled OTel documentation at ${CLAUDE_PLUGIN_ROOT}/docs/.
How to Answer OTel Questions
Check INDEX.md first - It maps topics to files
Check SYNC-REPORT.md - For any validation warnings
Search with Grep - Find specific attributes, config keys, or concepts
Read the relevant file - Get full context before answering
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:
Direct answer - What the user asked
Attributes table - If applicable (name, type, description)
Code example - .NET 10 syntax preferred
Source reference - Which doc file the answer came from
Ler descrição completa↓
Comentários · Nenhum comentário Ainda não há comentários. Seja o primeiro.