Automated summary
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.
Use this role when you need to analyze deployment incidents, check CI/CD pipeline status, or audit infrastructure changes.
Avoid this role if direct production or source code changes are required.
Security analysis
CautionAlthough 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.
- •Allows curl and edit of deployment configuration files (Dockerfile, fly.toml, .github/workflows/*.yml) which could potentially alter production state if executed.
Examples
Check the latest deployment status on Fly.io for my app.Investigate why the GitHub Actions workflow failed on the main branch.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
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/devops-engineer-analyst-mm78nn55/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/devops-engineer-analyst-mm78nn55' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/devops-engineer-analyst-mm78nn55/download' --output '.skill-downloads/devops-engineer-analyst-mm78nn55/SKILL.md.part' && mv '.skill-downloads/devops-engineer-analyst-mm78nn55/SKILL.md.part' '.skill-downloads/devops-engineer-analyst-mm78nn55/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.
Tools declared by the author (check availability in your agent): 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
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/devops-engineer-analyst-mm78nn55/SKILL.md' && test -s '.skill-downloads/devops-engineer-analyst-mm78nn55/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/analyst' && cp -R '.skill-downloads/devops-engineer-analyst-mm78nn55' '.claude/skills/analyst'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/devops-engineer-analyst-mm78nn55'openskills read 'devops-engineer-analyst-mm78nn55'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/devops-engineer-analyst-mm78nn55/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.