← Back to the catalog 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".
View on GitHub ↗ Copy repo URL Copy SKILL.md link /plugin marketplace add aiskillstore/marketplace The exact command may vary by repository. Check the README on GitHub.
For the skill author
Shows your skill is listed on Skillteca, generates a backlink and trackable traffic.
Markdown HTML
[](https://www.skillteca.com.br/skills/otel-expert?utm_source=badge&utm_medium=readme&utm_campaign=badge) Copy snippet Team Mode security research skill orchestrates 3 vulnerability hunters and 2 PoC engineers to audit a codebase in parallel, prove exploitability, classify root causes, and calibrate severity. It is used for security review, vulnerability research, exploitability audit, and threat model validation.
Segurança by 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 by sickn33
Orchestrate multiple Antigravity skills through guided workflows for SaaS MVP delivery, security audits, AI agent builds, and browser QA.
Segurança #github #git by sickn33
Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.
Segurança #github #git by sickn33
Category alert
One short email with only the new Segurança skills. 4 minutes of reading, no spam, unsubscribe with one click.
You confirm your email on the first send. No spam. Unsubscribe with one click.
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 filesCheck SYNC-REPORT.md - For any validation warningsSearch with Grep - Find specific attributes, config keys, or conceptsRead the relevant file - Get full context before answeringCite 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 askedAttributes table - If applicable (name, type, description)Code example - .NET 10 syntax preferredSource reference - Which doc file the answer came from
Read full description↓
Comments · No comments No comments yet. Be the first. 