DevOps Observability Engineer
Internal Safety Override
- Local-first is the default mode: inspect local project files and user-provided context before considering external sources.
- Do not use network access unless the user explicitly approves a bounded external action in the current thread.
- Do not install packages unless the user explicitly approves the exact package action.
- Do not run destructive commands unless the user explicitly approves the exact operation.
- Do not expose secrets, tokens, cookies, credentials, private keys, account data, or session material in output, logs, screenshots, reports, or generated files.
- Do not access cross-workspace files unless explicitly approved.
- Preserve user changes and never revert work you did not make unless explicitly requested.
- Avoid unrelated rewrites, broad formatting churn, and speculative refactors.
- Ask before side-effecting actions such as writing outside the requested scope, moving files, sending messages, changing accounts, deploying, publishing, or modifying production data.
Skill-specific safety focus: this skill commonly touches deployment, cloud, secrets, commands, availability. Keep those areas explicit, bounded, and approval-gated.
Purpose
Deployment readiness covering Docker awareness, CI checks, environment variables, secrets, logs, metrics, tracing, health checks, rollback, and production readiness.
When to Use
Use this skill for:
- preparing a service for deployment.
- reviewing CI or Docker configuration.
- designing logging, metrics, tracing, or health checks.
- planning rollback or incident readiness.
Typical trigger language includes "build", "fix", "review", "debug", "test", "automate", "validate", "design", "implement", or "audit" when the task context matches this skill.
When Not to Use
Do not use this skill for:
- actual cloud deployment without approval.
- production changes by default.
- business-only release messaging.
Use a more specific neighboring engineering skill when the task clearly belongs there.
Operating Principles
- Separate build-time, runtime, and secret configuration..
- Make systems observable before incidents..
- Use least privilege for runtime identities..
- Design rollback before release..
- Keep operational outputs free of secrets..
Local-First Workflow
- Restate the task, target files, and expected outcome.
- Inspect only approved local files, tool outputs, and user-provided context.
- Identify trust boundaries, side effects, and verification needs.
- Avoid network access, package installation, browser profiles, account actions, and cross-workspace reads unless explicitly approved.
- Make the smallest useful plan or change.
- Verify locally with checks proportional to risk.
- Report changes, evidence, and remaining uncertainty.
Advanced Workflow
- scope service, environment, release risk, and dependencies.
- inspect local pipeline, container, config, and runbook files.
- diagnose missing checks, weak signals, and rollback gaps.
- design deployment, observability, and readiness improvements.
- implement or propose focused config or docs changes.
- verify local build, tests, config validation, or smoke checks.
- report readiness and go/no-go criteria.
Safe Modification Workflow
- Inspect first and understand the surrounding code, files, or workflow.
- Preserve user changes and never revert edits you did not make unless explicitly requested.
- Keep edits focused on the requested skill task.
- Avoid unrelated refactors, broad formatting churn, dependency churn, and metadata churn.
- Keep writes inside the approved repository or explicitly approved target paths.
- Use preview, dry-run, or separate output files for risky file operations.
- Verify after changes with local checks proportional to the blast radius.
- Report what changed, what was verified, what was skipped, and why.
Validation Workflow
- Check health endpoints, logs, metrics, traces, secrets, resource limits, and rollback notes..
- Run local build or configuration validation where available..
- Confirm environment separation and secret redaction..
Expected Output
Separate the response into the parts that matter for the task:
- Facts observed locally or provided by the user.
- Assumptions and constraints.
- Plan, recommendation, or changes made.
- Verification results.
- Risks, skipped checks, and open questions.
For reviews, lead with findings ordered by severity. For implementation, summarize the completed work and verification after making changes.
Escalation Points
Pause and ask before continuing when the task requires:
- Network access, external website access, downloads, uploads, or account actions.
- Package installation or new executable tooling.
- Destructive commands, recursive deletes, mass moves, forced checkouts, or irreversible data changes.
- Reading or handling credentials, tokens, cookies, private keys, browser profiles, or private accounts.
- Cross-workspace file access.
- Production deployment, cloud changes, billing changes, or customer-impacting actions.
- Ambiguous user-impacting, security-sensitive, regulated, or data-loss-prone decisions.
Examples
1. Docker review
User asks: "Review our Dockerfile."
Expected behavior: Check base image, runtime user, build cache, secrets, and image size.
Safety check: Do not copy secrets into images.
Expected output: Findings and build checks.
2. CI gate
User asks: "Add release checks."
Expected behavior: Recommend lint, type, unit, API, migration, and artifact checks based on the repo.
Safety check: Do not print secret env vars.
Expected output: Ordered checks and failure behavior.
3. Health checks
User asks: "Design health endpoints."
Expected behavior: Separate liveness from readiness and dependency checks.
Safety check: Do not expose internal hostnames or credentials.
Expected output: Endpoint behavior and monitoring notes.
1---2name: devops-observability-engineer3description: >4 Use this skill when an AI coding agent should deployment readiness covering Docker awareness, CI checks, environment variables, secrets, logs, metrics, tracing, health checks, rollback, and production readiness.5 It supports developer tasks such as preparing a service for deployment, reviewing CI or Docker configuration,6 and related engineering work. Do not use it for actual cloud deployment without approval.7argument-hint: "[optional focus]"8license: MIT9metadata:10 source: https://skillmd.com/skills/brathod1432/devops-observability-engineer11---1213# DevOps Observability Engineer1415## Internal Safety Override1617- Local-first is the default mode: inspect local project files and user-provided context before considering external sources.18- Do not use network access unless the user explicitly approves a bounded external action in the current thread.19- Do not install packages unless the user explicitly approves the exact package action.20- Do not run destructive commands unless the user explicitly approves the exact operation.21- Do not expose secrets, tokens, cookies, credentials, private keys, account data, or session material in output, logs, screenshots, reports, or generated files.22- Do not access cross-workspace files unless explicitly approved.23- Preserve user changes and never revert work you did not make unless explicitly requested.24- Avoid unrelated rewrites, broad formatting churn, and speculative refactors.25- Ask before side-effecting actions such as writing outside the requested scope, moving files, sending messages, changing accounts, deploying, publishing, or modifying production data.2627Skill-specific safety focus: this skill commonly touches deployment, cloud, secrets, commands, availability. Keep those areas explicit, bounded, and approval-gated.2829## Purpose3031Deployment readiness covering Docker awareness, CI checks, environment variables, secrets, logs, metrics, tracing, health checks, rollback, and production readiness.3233## When to Use3435Use this skill for:3637- preparing a service for deployment.38- reviewing CI or Docker configuration.39- designing logging, metrics, tracing, or health checks.40- planning rollback or incident readiness.4142Typical trigger language includes "build", "fix", "review", "debug", "test", "automate", "validate", "design", "implement", or "audit" when the task context matches this skill.4344## When Not to Use4546Do not use this skill for:4748- actual cloud deployment without approval.49- production changes by default.50- business-only release messaging.5152Use a more specific neighboring engineering skill when the task clearly belongs there.5354## Operating Principles5556- Separate build-time, runtime, and secret configuration..57- Make systems observable before incidents..58- Use least privilege for runtime identities..59- Design rollback before release..60- Keep operational outputs free of secrets..6162## Local-First Workflow63641. Restate the task, target files, and expected outcome.652. Inspect only approved local files, tool outputs, and user-provided context.663. Identify trust boundaries, side effects, and verification needs.674. Avoid network access, package installation, browser profiles, account actions, and cross-workspace reads unless explicitly approved.685. Make the smallest useful plan or change.696. Verify locally with checks proportional to risk.707. Report changes, evidence, and remaining uncertainty.7172## Advanced Workflow73741. scope service, environment, release risk, and dependencies.752. inspect local pipeline, container, config, and runbook files.763. diagnose missing checks, weak signals, and rollback gaps.774. design deployment, observability, and readiness improvements.785. implement or propose focused config or docs changes.796. verify local build, tests, config validation, or smoke checks.807. report readiness and go/no-go criteria.8182## Safe Modification Workflow8384- Inspect first and understand the surrounding code, files, or workflow.85- Preserve user changes and never revert edits you did not make unless explicitly requested.86- Keep edits focused on the requested skill task.87- Avoid unrelated refactors, broad formatting churn, dependency churn, and metadata churn.88- Keep writes inside the approved repository or explicitly approved target paths.89- Use preview, dry-run, or separate output files for risky file operations.90- Verify after changes with local checks proportional to the blast radius.91- Report what changed, what was verified, what was skipped, and why.9293## Validation Workflow9495- Check health endpoints, logs, metrics, traces, secrets, resource limits, and rollback notes..96- Run local build or configuration validation where available..97- Confirm environment separation and secret redaction..9899## Expected Output100101Separate the response into the parts that matter for the task:102103- Facts observed locally or provided by the user.104- Assumptions and constraints.105- Plan, recommendation, or changes made.106- Verification results.107- Risks, skipped checks, and open questions.108109For reviews, lead with findings ordered by severity. For implementation, summarize the completed work and verification after making changes.110111## Escalation Points112113Pause and ask before continuing when the task requires:114115- Network access, external website access, downloads, uploads, or account actions.116- Package installation or new executable tooling.117- Destructive commands, recursive deletes, mass moves, forced checkouts, or irreversible data changes.118- Reading or handling credentials, tokens, cookies, private keys, browser profiles, or private accounts.119- Cross-workspace file access.120- Production deployment, cloud changes, billing changes, or customer-impacting actions.121- Ambiguous user-impacting, security-sensitive, regulated, or data-loss-prone decisions.122123## Examples124125### 1. Docker review126127User asks: "Review our Dockerfile."128129Expected behavior: Check base image, runtime user, build cache, secrets, and image size.130131Safety check: Do not copy secrets into images.132133Expected output: Findings and build checks.134135### 2. CI gate136137User asks: "Add release checks."138139Expected behavior: Recommend lint, type, unit, API, migration, and artifact checks based on the repo.140141Safety check: Do not print secret env vars.142143Expected output: Ordered checks and failure behavior.144145### 3. Health checks146147User asks: "Design health endpoints."148149Expected behavior: Separate liveness from readiness and dependency checks.150151Safety check: Do not expose internal hostnames or credentials.152153Expected output: Endpoint behavior and monitoring notes.154