QA Observability
Observability for quality engineering: using logs, metrics, and traces as test signals; SLI/SLO quality gates; trace-based debugging of failures; and cost-aware instrumentation with OpenTelemetry.
Install
/plugin marketplace add Freddy-CHEN-ux/00_claude_skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add Freddy-CHEN-ux/00_claude_skills --skill qa-observabilitygit clone --depth 1 https://github.com/Freddy-CHEN-ux/00_claude_skills.git /tmp/00_claude_skills
mkdir -p ~/.claude/skills
cp -r /tmp/00_claude_skills/skills/qa-observability ~/.claude/skills/qa-observabilityPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# QA Observability & Performance Engineering (Dec 2025) This skill provides execution-ready patterns for building observable, performant systems and using telemetry as part of QA workflows. Core references: OpenTelemetry ([Docs](https://opentelemetry.io/docs/)) and W3C Trace Context ([Spec](https://www.w3.org/TR/trace-context/)) for correlation; SLO/error budget guidance from the Google SRE Book ([Service Level Objectives](https://sre.google/sre-book/service-level-objectives/)). --- ## When to Use This Skill Claude should invoke this skill when a user requests: - OpenTelemetry instrumentation and setup - Distributed tracing implementation (Jaeger, Tempo, Zipkin) - Metrics collection and dashboarding (Prometheus, Grafana) - Structured logging setup (Pino, Winston, structlog) - SLO/SLI definition and error budgets - Performance profiling and optimization - Capacity planning and resource forecasting - APM integration (Datadog, New Relic, Dynatrace) - Observability maturity assessment - Alert design and on-call runbooks - Performance budgeting (frontend and backend) - Cost-performance optimization - Production performance debugging --- ## Core QA (Default) ### What “Observability for QA” Means - Treat telemetry as a first-class test oracle and debugging substrate, not an ops-only concern.
Details
- Skill name
qa-observability- Repository
- Freddy-CHEN-ux/00_claude_skills
- Path
skills/qa-observability/SKILL.md- Repo updated
- 10 January 2026
FAQ
What does the QA Observability skill do?
Observability for quality engineering: using logs, metrics, and traces as test signals; SLI/SLO quality gates; trace-based debugging of failures; and cost-aware instrumentation with OpenTelemetry.
How do I install the QA Observability skill?
Claude Code plugin: /plugin marketplace add Freddy-CHEN-ux/00_claude_skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is QA Observability popular?
It lives in Freddy-CHEN-ux/00_claude_skills, which has 8 GitHub stars and 3 forks.
Related skills
Add Integration
8Freddy-CHEN-ux/00_claude_skills
Build a new API integration for Nexus. Load when user mentions "add integration", "new integration", "integrate with", "connect to [service]", or "build [service] integration". Interactive workflow that discovers API endpoints, plans the integration, and creates a project for implementation.
AI Agents
8Freddy-CHEN-ux/00_claude_skills
Production-grade AI agent patterns with MCP integration, agentic RAG, handoff orchestration, multi-layer guardrails, and observability (modern best practices)
AI LLM
8Freddy-CHEN-ux/00_claude_skills
Production LLM engineering skill. Covers strategy selection (prompting vs RAG vs fine-tuning), dataset design, PEFT/LoRA, evaluation workflows, deployment handoff to inference serving, and lifecycle operations with cost/safety controls.
QA Refactoring
8Freddy-CHEN-ux/00_claude_skills
Safe refactoring for quality engineering: characterization tests, seam creation, incremental steps, contracts, and CI quality gates to preserve behavior while changing structure.
QA Handoff
5vnovakovits/claude-skills
Update a ticket with what shipped and tell QA what to test, in lean, empathetic, user-journey language. Verifies what is actually merged, released and deployed, maps each change to the ticket it fixes, writes a short status (in production / open / left, by owner) and a numbered list of user journeys to test with expected outcomes and what to report. Use when a change is merged or deployed and someone asks "what should QA test", "update the ticket", "post what we merged", "is this live", or wants a tester note, release note or status comment for any tracker (Linear, Jira, GitHub Issues).
QA Resilience
8Freddy-CHEN-ux/00_claude_skills
Resilience engineering for QA: failure mode testing (timeouts/retries/dependency failures), chaos experiments with blast-radius controls, degraded-mode UX expectations, and reliability gates.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.