Devops

Skill sirius-zuo/devops-skills/skills/devops

A collection of DevOps skills designed for LLM-powered agents and AI workflows. This repository provides reusable capabilities, tools, prompts, and best-practice patterns to help automate infrastructure operations, CI/CD pipelines, cloud management, observability, security, and platform engineering tasks.

Install

npx -y skills add sirius-zuo/devops-skills --skill devops

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when a user asks to set up CI/CD, Dockerize a project, add a deployment pipeline, configure GitHub Actions / GitLab CI / CircleCI, review existing DevOps config, or says "we have no CI", "no pipeline", "need to containerize this", or "help with deployments". Proactively suggest when source code is present but no devops/ folder or CI config files exist.

SKILL.md

3.3 KB, as published. Nobody here has run it

DevOps Setup

Overview

Detects which of three scenarios applies, confirms with the user, then calls sub-skills in sequence to produce working config files and an HTML report.

Scenario Detection

Scan the working directory before doing anything else:

Signal	Scenario
Design/arch docs found, no source code	1. Design-stage
Source code found, no `devops/` folder	2. Code-complete
Source code + `devops/` folder both found	3. DevOps-review

Design docs signals: files named *.md containing architecture, ADR, design decision keywords; files in docs/, design/, spec/ folders; no .py/.ts/.js/.go/.java/.rb/.rs/.cs source files present.

Source code signals: presence of .py, .ts, .js, .go, .java, .rb, .rs, .cs files outside of docs/.

DevOps folder signal: devops/ directory exists with at least one config file inside.

If ambiguous (source code + design docs, no devops/): ask — "I see both design docs and source code but no devops/ folder. Should I base recommendations on: (A) The design docs — Scenario 1, or (B) The existing codebase — Scenario 2?"

Stack Detection

While scanning, note:

Language: file extensions
Framework: imports in source files (express, fastapi, gin, spring, rails, etc.)
Database: ORM config files, connection strings, docker-compose services
Cloud: SDK imports (boto3/aws-sdk → AWS; google-cloud → GCP; azure → Azure)
CI/CD: presence of .github/, .gitlab-ci.yml, .circleci/
Containers: Dockerfile, docker-compose.yml, k8s/ directory

Announcement & Confirmation

Before calling any sub-skill, announce to the user:

Detected scenario: [show only the detected scenario name, e.g. "2. Code-complete"]
Detected stack: [language] + [framework] | DB: [database] | Cloud: [cloud or "none detected"]

I will now:
1. Analyze the project and ask a few targeted questions → devops/report/analysis.json
2. Run a security review → devops/report/security-findings.json
3. Generate config files → devops/working/
4. Produce an HTML report → devops/report/index.html

Proceed? (yes/no)

Wait for confirmation before proceeding. If the user declines, summarize the detected scenario and stack, and stop. Do not generate any files.

Pipeline

Call these sub-skills in order. State flows through files on disk — devops/report/analysis.json (written by devops-analyze) and devops/report/security-findings.json (written by devops-security) — not through Skill tool args. Each sub-skill reads the files left by the previous one.

Invoke devops-analyze
Invoke devops-security
Invoke devops-generate
Invoke devops-report

Output Locations

Config files: devops/working/ (relative to project root)
JSON data files: devops/report/ (analysis.json, security-findings.json)
HTML report: devops/report/index.html
Create both directories if they don't exist.

Gives 0 of the 12 instructions most ci cd skills give

Counted across 392 of the 394 authors here whose files we hold, read 2026-08-06

pin third-party actions to full commit SHAsin 33 of 392
cache dependencies appropriatelyin 24 of 392, across 12 files
optimize pipelines exceeding ten minutesin 20 of 392, across 6 files
enforce all quality gates before mergein 20 of 392, across 7 files
Configure branch protection rulesin 19 of 392, across 5 files
use environments for deployment trackingin 19 of 392, across 7 files
implement manual gates for productionin 19 of 392, across 7 files
implement security scanningin 18 of 392, across 5 files
fix failing code instead of disabling checksin 18 of 392, across 4 files
use CI/CD variables for secretsin 18 of 392, across 6 files
move checks upstream in the pipelinein 17 of 392, across 3 files
use specific image tagsin 17 of 392, across 5 files

Said here and by no other author read

scan the working directory first
detect scenario from directory contents
ask if scenario is ambiguous
announce detected scenario and stack
wait for confirmation before proceeding
stop if the user declines

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.