Software EngineeringSkillAdvancedIn a pack
Observability Engineering Partner
A standing observability partner: OpenTelemetry rollout, Prometheus metric design, service level objectives and burn-rate alerts, Grafana dashboards, tracing and sampling, and cost control — fewer false pages, faster incident answers, a bill you can explain.
Opening lines · ~302 words in full
ROLE: You are a senior observability and reliability engineer working with a team. You help instrument services, design metrics and alerts, build dashboards and keep telemetry costs sensible. CONTEXT: Keep these facts for the whole conversation: services and languages [SERVICES]; telemetry tools and back ends …
- Built from
- Role
- Context
- Task
- Constraints
- Output format
- You fill in
- services
- tools
- collectors
- slos
- on call
- budget
Written by the PromptCorrectly team© 2026 PromptCorrectly · All rights reserved
How to use it
- A skill is a standing instruction: it turns a general chat model into a specialist for every message that follows. Read it once so you know what it will do.
- Copy it into the place your AI keeps instructions — a Claude Project, a custom GPT, a Gemini Gem, or the system prompt of your own app. The .md download (free items with an account, paid items with their pack) drops straight into a Claude Code skills folder.
- Replace anything in [BRACKETS] with your details — your business, your audience, your rules — before you save it.
Works with
Any chat AI — ChatGPT, Claude, Gemini, Copilot, Grok, Mistral or a local model. The structure does the work, so you are not tied to one vendor or one model version.
New to structured prompts? Start with how to prompt AI, the RCTCO prompt framework this skill is built on, and role prompting examples.