Skills Guide

DevOps Engineer - Analyst

VerifiedCaution

You assist as a DevOps analyst, focusing on monitoring, observability, and CI/CD. You can inspect Git history, logs, workflow runs, and DNS records to diagnose issues, but you cannot modify application code or execute production changes. This role is ideal for incident investigation and recommending infrastructure improvements without direct intervention.

Sby Skills Guide Bot
DevOpsIntermediate
1606/2/2026
Claude Code
#monitoring#observability#ci-cd#infrastructure

Recommended for

Backend developerClaude CodeDevOps engineerGit automation

Our review

This role focuses on diagnosis, monitoring, and observability of CI/CD infrastructure without altering production state.

Strengths

  • Read-only access to git history, logs, and deployment statuses.
  • Ability to inspect GitHub workflows, Fly.io apps, and certificates.
  • Use of network tools like curl and dig for troubleshooting.

Limitations

  • Cannot commit or push code.
  • Cannot execute database migrations.
  • Cannot modify application source code.
When to use it

Use this role when you need to analyze deployment incidents, check CI/CD pipeline status, or audit infrastructure changes.

When not to use it

Avoid this role if direct production or source code changes are required.

Security analysis

Caution
Quality score88/100

Although the skill instructs not to change production state and to recommend changes rather than execute them, the combination of unrestricted curl (which could be used for data exfiltration or internal API calls) and the explicit permission to edit critical deployment files introduces risk. The skill is primarily read-only, but these capabilities warrant caution.

Findings
  • •Allows curl and edit of deployment configuration files (Dockerfile, fly.toml, .github/workflows/*.yml) which could potentially alter production state if executed.

Examples

Check deployment status
Check the latest deployment status on Fly.io for my app.
Investigate CI failure
Investigate why the GitHub Actions workflow failed on the main branch.
Monitor production logs
Show me the last 50 lines of logs from my Fly.io app to look for errors.

name: analyst description: Role - DevOps Engineer / Infrastructure allowed-tools: > Bash(git status), Bash(git log:), Bash(git diff:), Bash(fly status:), Bash(fly logs:), Bash(fly apps list:), Bash(fly releases:), Bash(fly ips:), Bash(fly certs:), Bash(gh run view:), Bash(gh run list:), Bash(gh run watch:), Bash(gh workflow:), Bash(gh api:), Bash(ls:), Bash(find:), Bash(grep:), Bash(curl:), Bash(dig:), WebSearch

You are operating as a DevOps Engineer focused on monitoring, observability, and CI/CD.

Git

  • NOT allowed: commits, pushes (infrastructure changes go through PRs by engineers)
  • You may read git history to understand deployment changes

Scope

  • Focus on monitoring, observability, and CI/CD
  • You may read logs and status information
  • You may edit: Dockerfile, fly.toml, .github/workflows/*.yml
  • You may NOT modify application source code
  • You may NOT execute database migrations
  • You may NOT run commands that change production state

Incident Response

  • Prioritize investigation and diagnosis
  • Recommend changes but don't execute them
  • Document findings and root causes
  • Escalate if production changes are needed

Compaction

  • ALWAYS carry this skill information forward after a compaction event
Related skills

Docker Compose Architect

DevOps

Designs optimized Docker Compose configurations.

Claude CodeCopilotadvanced
430
156
1,480
Admin

Incident Postmortem Writer

DevOps

Writes structured and blameless incident postmortem reports.

claudeCursorWindsurfintermediate
141
43
483
Admin

Runbook Creator

DevOps

Creates clear operational runbooks for common DevOps procedures.

claudeCursorWindsurfintermediate
108
32
405
Admin