opentelemetry-principal-engineer
Principal/Senior-level OpenTelemetry playbook for traces, metrics, logs, semantic conventions, collector pipelines, sampling, data governance, and production observability architecture. Use when: instrumenting services, designing collector topologies, standardizing telemetry, debugging context propagation, or building large-scale observability platforms.
What this skill does
# OpenTelemetry Mastery (Senior → Principal) ## Operate - Start from what must be explainable in production: request flow, failure attribution, dependency latency, and causality. - Treat telemetry schemas, propagation, sampling, and collector design as platform architecture. - Prefer standardized semantic conventions over one-off instrumentation creativity. - Design for correlation across traces, metrics, and logs without uncontrolled cost. ## Default Standards - Context propagation must be reliable across service and async boundaries. - Sampling policy should match debugging and business-critical workflows. - Collector pipelines should be simple enough to operate and debug. - Telemetry attributes are a cost and governance budget. - Vendor portability should not mean lowest-common-denominator blindness. ## References - Tracing model and span design: [references/tracing-model-and-span-design.md](references/tracing-model-and-span-design.md) - Context propagation and async boundaries: [references/context-propagation-and-async-boundaries.md](references/context-propagation-and-async-boundaries.md) - Semantic conventions and schema governance: [references/semantic-conventions-and-schema-governance.md](references/semantic-conventions-and-schema-governance.md) - Sampling strategy and cost control: [references/sampling-strategy-and-cost-control.md](references/sampling-strategy-and-cost-control.md) - Collector architecture and pipelines: [references/collector-architecture-and-pipelines.md](references/collector-architecture-and-pipelines.md) - Metrics, logs, and correlation: [references/metrics-logs-and-correlation.md](references/metrics-logs-and-correlation.md) - Reliability and operations: [references/reliability-and-operations.md](references/reliability-and-operations.md) - Incident runbooks: [references/incident-runbooks.md](references/incident-runbooks.md)
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.