agentleFS
th3r-devth3r-dev/th3-skills/skills/devops/SKILL.md

devops

Skill2 starsChanged 2 days agoMITView on GitHub

DevOps toolkit for a small platform team, generalised from a Thai-government integration project: (1) change — any infra work that touches a real machine (ssh via a jump host, kubectl, HAProxy / ingress / vault-backed secrets, incident root cause) done in a fixed order and closed with a before / steps / after / rollback report with a SEV level; (2) release-scope — what goes up in the next release and what is still pending, from git keys across the product's repos plus the issue boards, written as the PM list and checked against the customer message; (3) network-diagram — the team's system / network diagram as one draw.io file with a board per version, exported to a clean one-page PDF, rebuilt from a PDF, benchmarked. Use WHENEVER the work is "ssh to the server", "edit haproxy", "root cause / postmortem", "what's in release X", "release note for the PM", "update the system diagram", "export the drawio", "เขียน rootcause", "สรุป release ให้ PM", "แก้ diagram ระบบ". Read the sub-skill's SKILL.md before acting.

51 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

Files
SKILL.md

devops — sub-skills

When the work is…ReadScripts
"ssh to <ip>", "kubectl on the cluster", "edit haproxy.cfg", "root cause", "before/after/rollback report"change/SKILL.md + references/ (change template TH/EN, incident template)change/scripts/jssh.py (jump-host ssh from an ini, --sudo --kube --forward) · snapshot_haproxy.sh
"what's in v1.2.x", "pending for the next release", "summary for the PM", "check the PM's customer message"release-scope/SKILL.mdrelease-scope/scripts/release_scope.py (--repo × N, --key-regex, --board × N → scope.md + scope.json)
"update the system diagram", "export the drawio to one PDF", "rebuild the drawio from the PDF", "compare with the final PDF"network-diagram/SKILL.mdnetwork-diagram/scripts/drawio_board.py (list clone export trace compare) + assets/icons/

They chain: a change/ report links the diagram that explains it (rootcause.html, or a version board from network-diagram/); release-scope/ tells change/ which tag a prod deploy carries.

Rules every sub-skill keeps

  • Read the project's own docs/, changes/ and incidents/ before guessing about a machine. Facts about your fleet beat any generic cloud / Kubernetes advice.
  • Passwords never appear on a command line, in a report, or in chat. jssh.py reads them from ~/.config/devops/hosts.ini (chmod 600) and hands them to ssh through SSH_ASKPASS.
  • Evidence before change, same commands after. Snapshot the running config, md5, inode, start time and the numbers that will judge the result; verify by re-running them, not by "no errors".
  • Rollback is written before step 1, with the command that proves it worked.
  • Prod facts come from the owner (what prod runs, which hotfix never shipped), not from tags.
  • Diagrams are editable sources, exported to PDF — never the other way round, and never with icons cut from a PDF.
  • Scripts run with uv run <script> (PEP 723 inline dependencies); drawio_board.py also needs the draw.io desktop app.

Tests

cd skills/devops && python -m pytest -q     # needs: pytest pymupdf numpy pillow (git on PATH)

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.