agentleFS
Pranav-Patel-SimformPranav-Patel-Simform/claude-skills/skills/devops/SKILL.md

devops

Skill0 starsChanged 7 months agoMITView on GitHub

Replaces and automates the full DevOps role. Use this skill whenever the user wants to: write Dockerfiles, create docker-compose setups, write CI/CD pipelines (GitHub Actions, GitLab CI, CircleCI), provision infrastructure as code (Terraform, Pulumi, Ansible), configure Nginx/Caddy/Apache, set up Kubernetes manifests (Deployments, Services, Ingress, HPA), write shell/bash automation scripts, handle environment variable management, set up monitoring (Prometheus, Grafana, Loki), configure cloud services (AWS, GCP, Azure), or debug deployment failures. Trigger even if the user says "deploy", "pipeline", "container", "server", "cloud", "infra", or "prod". If any DevOps task is mentioned — use this skill.

56 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use Problem-Solving Techniques, community-led-growth and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • truongtv22Skill

    Problem-Solving Techniques

    Apply systematic problem-solving techniques for complexity spirals (simplification cascades), innovation blocks (collision-zone thinking), recurring patterns (meta-pattern recognition), assumption constraints (inversion exercise), scale uncertainty (scale game), and dispatch when stuck. Techniques derived from Microsoft Amplifier project patterns adapted for immediate application.

    Also in 5 projects that use this

  • nicepkgSkill

    community-led-growth

    Expert in community-led growth (CLG) - leveraging user communities to drive acquisition, retention, and expansion. Covers building developer communities, user groups, ambassador programs, and turning customers into advocates. Knows the difference between community as a feature vs community as a growth engine, and how to measure community ROI. Use when "community-led, CLG, ambassador program, champion program, user community, developer community, word of mouth, user group, " mentioned.

    Also in 5 projects that use this

  • nicepkgSkill

    ph-community-outreach

    Engage Reddit, Indie Hackers, Hacker News and other communities for Product Hunt launches. Use this skill to identify relevant communities, craft appropriate posts, and drive cross-platform engagement without appearing spammy.

    Also in 5 projects that use this

  • xfstudioSkill

    micro-saas-launcher

    Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software. Covers idea validation, MVP development, pricing, launch strategies, and growing to sustainable revenue. Ship in weeks, not months. Use when: micro saas, indie hacker, small saas, side project, saas mvp.

    Also in 5 projects that use this

  • mastepanoskiSkill

    ux-audit-rethink

    Comprehensive UX audit using IxDF's 7 factors, 5 usability characteristics, and 5 interaction dimensions. Holistic evaluation with redesign proposals based on user-centered design principles.

    Also in 5 projects that use this

  • ncklrsSkill

    seo-content-strategist

    Expert SEO content strategy for SaaS and B2B sites. Use when doing keyword research, planning content clusters, creating pillar pages, optimizing on-page SEO, fixing technical SEO issues, building links, refreshing content, implementing programmatic SEO, mapping search intent, optimizing for SERP features, or measuring content performance. Use for SEO audits, content gap analysis, and organic growth strategy.

    Also in 5 projects that use this

  • +6 more from nicepkg

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. 0 are common, 5 are distinctive, and 8 are very specific to this project.

  • 0

    Common

    Most of the 40 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 8

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Always write multi-stage Dockerfiles to minimize image size

    line 23
  2. Very specific:

    Use specific version tags (never latest)

    line 24
  3. Very specific:

    Run as non-root user (USER appuser)

    line 25
  4. Very specific:

    Add .dockerignore with node_modules, .git, *.log

    line 26
  5. Distinctive:

    When writing GitHub Actions:

    line 30
  6. Very specific:

    Use environment secrets (${{ secrets.KEY }})

    line 33
  7. Distinctive:

    Add branch protection rules in comments

    line 34
  8. Very specific:

    Always include variables.tf, outputs.tf, main.tf

    line 38
  9. Distinctive:

    Use remote state (S3 + DynamoDB for AWS)

    line 39
  10. Very specific:

    Always set resources.requests and resources.limits

    line 44
  11. Very specific:

    Use livenessProbe and readinessProbe

    line 45
  12. Very specific:

    Use ConfigMap for non-sensitive config, Secret for credentials

    line 47
  13. Distinctive:

    Use least-privilege IAM roles

    line 52

“Common” is measured: kept by at least 6 in 10 of the 40 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

DevOps Skill

You are acting as a senior DevOps engineer. Your job is to produce production-ready, security-hardened, and efficient infrastructure code and configuration.

Core Responsibilities

1. Containerization

  • Always write multi-stage Dockerfiles to minimize image size
  • Use specific version tags (never latest)
  • Run as non-root user (USER appuser)
  • Add .dockerignore with node_modules, .git, *.log
  • Include health checks (HEALTHCHECK CMD ...)

2. CI/CD Pipelines

When writing GitHub Actions:

  • Cache dependencies (actions/cache)
  • Separate build, test, deploy jobs
  • Use environment secrets (${{ secrets.KEY }})
  • Add branch protection rules in comments
  • Include rollback step on failure

3. Infrastructure as Code (Terraform)

  • Always include variables.tf, outputs.tf, main.tf
  • Use remote state (S3 + DynamoDB for AWS)
  • Tag all resources with env, project, owner
  • Never hardcode credentials

4. Kubernetes

  • Always set resources.requests and resources.limits
  • Use livenessProbe and readinessProbe
  • Configure HPA (min 2 replicas in prod)
  • Use ConfigMap for non-sensitive config, Secret for credentials
  • Add PodDisruptionBudget

5. Security Defaults

  • Enable HTTPS only; redirect HTTP → HTTPS
  • Use least-privilege IAM roles
  • Rotate secrets using external secret managers (Vault, AWS Secrets Manager)
  • Scan images with Trivy in CI

Output Format

Always deliver:

  1. The file(s) with correct names and paths
  2. A quick-start command block to run/apply
  3. What to change (env-specific variables clearly marked with # TODO:)
  4. Verification command to confirm it's working

Example Triggers

  • "Dockerize my Node.js app"
  • "Write a GitHub Actions pipeline for my Python project"
  • "Set up Nginx as reverse proxy"
  • "Create Terraform for AWS ECS"
  • "Deploy to Kubernetes"

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.