Automated summary
This skill helps set up monitoring, structured logging, distributed tracing, and alerting for applications and infrastructure.
Strengths
- Covers the three pillars of observability (logs, metrics, traces)
- Provides concrete Python code examples
- Includes Golden Signals configuration for reliability
Limitations
- Examples are limited to Python, no other languages
- Does not cover integration with specific cloud providers
- Assumes basic knowledge of observability concepts
Use when starting observability in a new application or improving an existing stack.
Avoid if you already have a full observability solution and need advanced fine-tuning.
Security analysis
SafeThe skill provides guidance on observability patterns and includes Python code snippets for logging, metrics, and tracing. It does not instruct harmful actions like executing shell commands or exfiltrating data. No tools are declared, so the AI agent cannot run code.
No concerns found
How this analysis is madeExamples
Set up structured JSON logging for my Python service.Add Prometheus metrics to track HTTP requests and latency.Implement OpenTelemetry distributed tracing for my microservices.name: observability-specialist description: Use this for setting up monitoring, logging, distributed tracing, and alerting for applications and infrastructure.
Observability Specialist
You ensure systems are observable, debuggable, and reliable through metrics, logs, and traces.
When to use
- "Set up monitoring for this app."
- "Create an alert for high latency."
- "Debug this production issue using logs."
- "Implement distributed tracing."
Instructions
- Structured Logging:
- Use JSON format for logs.
- Include essential fields: timestamp, level, service, trace_id, message.
- Log at appropriate levels (ERROR for faults, INFO for state changes, DEBUG for details).
- Metrics:
- Track the "Golden Signals": Latency, Traffic, Errors, and Saturation.
- Use Prometheus-style metrics (Counters, Gauges, Histograms).
- Tracing:
- Implement OpenTelemetry or similar for distributed tracing.
- Ensure trace context propagates across service boundaries.
- Dashboards & Alerts:
- Create dashboards to visualize system health.
- Define alerts on meaningful symptoms (user error rate) rather than just internal causes (CPU high).
Examples
1. Structured Logging with JSON
import logging
import json
from datetime import datetime
class JSONFormatter(logging.Formatter):
def format(self, record):
log_data = {
"timestamp": datetime.utcnow().isoformat(),
"level": record.levelname,
"service": "my-service",
"message": record.getMessage(),
"trace_id": getattr(record, 'trace_id', None)
}
return json.dumps(log_data)
logger = logging.getLogger(__name__)
handler = logging.StreamHandler()
handler.setFormatter(JSONFormatter())
logger.addHandler(handler)
logger.setLevel(logging.INFO)
# Usage
logger.info("User logged in", extra={"trace_id": "abc123"})
2. Prometheus Metrics
from prometheus_client import Counter, Histogram, Gauge, start_http_server
import time
# Define metrics
request_count = Counter('http_requests_total', 'Total HTTP requests', ['method', 'endpoint', 'status'])
request_latency = Histogram('http_request_duration_seconds', 'HTTP request latency')
active_users = Gauge('active_users', 'Number of active users')
# Track metrics
@request_latency.time()
def handle_request(method, endpoint):
# Your logic here
time.sleep(0.1)
request_count.labels(method=method, endpoint=endpoint, status='200').inc()
# Start metrics server
start_http_server(8000)
3. OpenTelemetry Distributed Tracing
from opentelemetry import trace
from opentelemetry.sdk.trace import TracerProvider
from opentelemetry.sdk.trace.export import BatchSpanProcessor, ConsoleSpanExporter
# Setup
trace.set_tracer_provider(TracerProvider())
tracer = trace.get_tracer(__name__)
trace.get_tracer_provider().add_span_processor(
BatchSpanProcessor(ConsoleSpanExporter())
)
# Usage
with tracer.start_as_current_span("process_order") as span:
span.set_attribute("order.id", "12345")
# Your business logic
with tracer.start_as_current_span("validate_payment"):
# Payment validation logic
pass
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/observability-specialist-mma3jsvq/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/observability-specialist-mma3jsvq' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/observability-specialist-mma3jsvq/download' --output '.skill-downloads/observability-specialist-mma3jsvq/SKILL.md.part' && mv '.skill-downloads/observability-specialist-mma3jsvq/SKILL.md.part' '.skill-downloads/observability-specialist-mma3jsvq/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/observability-specialist-mma3jsvq/SKILL.md' && test -s '.skill-downloads/observability-specialist-mma3jsvq/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/observability-specialist' && cp -R '.skill-downloads/observability-specialist-mma3jsvq' '.claude/skills/observability-specialist'Cursor
test -f '.skill-downloads/observability-specialist-mma3jsvq/SKILL.md' && test -s '.skill-downloads/observability-specialist-mma3jsvq/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/observability-specialist' && cp -R '.skill-downloads/observability-specialist-mma3jsvq' '.cursor/skills/observability-specialist'Codex
test -f '.skill-downloads/observability-specialist-mma3jsvq/SKILL.md' && test -s '.skill-downloads/observability-specialist-mma3jsvq/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/observability-specialist' && cp -R '.skill-downloads/observability-specialist-mma3jsvq' '.agents/skills/observability-specialist'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/observability-specialist-mma3jsvq'openskills read 'observability-specialist-mma3jsvq'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/observability-specialist-mma3jsvq/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Configure a Chat Channel with SecretRefs
DevOps
Set up chat channels using non-interactive commands, with secrets only as SecretRefs. Covers gather, mutate, repair, and prove steps for reliable delivery.
Investigate ClickHouse CI Failures
DevOps
Investigate a ClickHouse CI failure end-to-end from a PR or S3 report URL. Fetches failed tests, classifies flaky vs real regression, and checks for existing issues/fixes.
Ansible PR Review
DevOps
Reviews an Ansible PR following the project's standardized process, including changelog checks, test coverage validation, and feedback tracking.