agentleFS
chuckplayerchuckplayer/claude-agent-pack/skills/devops/SKILL.md

devops

Skill8 starsChanged 35 days agoMITView on GitHub

Use when unsure whether a request is a GitHub or Azure DevOps operation, or when someone says "devops help", "connect to devops", "check my work items or PRs", "devops?". Routes to devops-github or devops-azure based on intent. Also use as a fallback when a request doesn't clearly map to either one.

53 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

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 39 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the request doesn't already make it obvious, ask the user one question:

    line 26
  2. Distinctive:

    If signals conflict or neither is present, ask directly rather than guessing.

    line 37
  3. Very specific:

    Env vars are each sub-skill's own concern: Don't check GITHUB_REPOS/AZURE_DEVOPS_PROJECTS here — route first, and let the target skill …

    line 49

“Common” is measured: kept by at least 6 in 10 of the 39 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 Help

The DevOps skill family reads and writes GitHub and Azure DevOps directly via their native CLIs (gh and az) — no MCP server required. Each sub-skill owns one platform, handles its own first-time setup and auth, and applies the same strict-targeting and preview-and-confirm discipline before any write.

The two skills

SkillUse when
/devops-githubGitHub PRs and issues — repos configured in GITHUB_ORG/GITHUB_REPOS
/devops-azureAzure DevOps work items and PRs — org/projects configured in AZURE_DEVOPS_ORG/AZURE_DEVOPS_PROJECTS

1. Identify intent

If the request doesn't already make it obvious, ask the user one question: "GitHub or Azure DevOps?"

Listen for these signals first, since they often make the question unnecessary:

  • GitHub signals: "issue", "pull request", "PR #N", a repo name matching GITHUB_REPOS → /devops-github
  • Azure DevOps signals: "work item", "board", "sprint", "bug/defect", a project name matching AZURE_DEVOPS_PROJECTS (e.g. "<project-a>"), or the configured AZURE_DEVOPS_ORG → /devops-azure

If signals conflict or neither is present, ask directly rather than guessing.

2. Route and hand off

Once intent is clear, tell the user which skill handles it and invoke it. For example: "That's Azure DevOps — starting /devops-azure now."

Gotchas

  • Do not attempt the operation yourself. This skill only identifies intent and routes. /devops-github and /devops-azure handle setup, auth, targeting, and execution independently.
  • Env vars are each sub-skill's own concern. Don't check GITHUB_REPOS/AZURE_DEVOPS_PROJECTS here — route first, and let the target skill handle its own first-run setup if they're unset.
  • "I want to do both" — route to whichever the user mentioned first, and note the other skill is available as a separate follow-up. Don't try to interleave both platforms in one pass.

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.