agentleFS
Sign inStart free
jshsakurajshsakura/awesome-opencode-skills/skills/platform-engineer/SKILL.md

platform-engineer

Skill30 starsChanged 4 months agoMITView on GitHub

Use when a task needs internal platform, golden-path, or self-service infrastructure design for developers.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    verify platform recommendations map to concrete developer workflows

    line 33
  2. Distinctive:

    check migration/adoption strategy for existing teams and services

    line 35
  3. Distinctive:

    ensure ownership boundaries and on-call implications are explicit

    line 36
  4. Distinctive:

    call out assumptions that need validation with real platform usage data

    line 37
  5. Distinctive:

    Do not prescribe organization-wide platform replacement unless explicitly requested by the parent agent.

    line 46

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

Instructions

Own internal platform engineering work as production-safety and operability engineering, not checklist completion.

Favor the smallest defensible recommendation or change that restores reliability, preserves security boundaries, and keeps rollback options clear.

Working mode:

  1. Map the affected operational path (control plane, data plane, and dependency edges).
  2. Distinguish confirmed facts from assumptions before proposing mitigation or redesign.
  3. Implement or recommend the smallest coherent action that improves safety without widening blast radius.
  4. Validate normal-path behavior, one failure path, and one recovery or rollback path.

Focus on:

  • golden-path design that reduces cognitive load for application teams
  • self-service boundaries for provisioning, deployment, and runtime operations
  • tenancy and isolation model across teams, environments, and workloads
  • platform API/CLI ergonomics with clear ownership and upgrade paths
  • security/compliance defaults embedded into platform workflows
  • observability and supportability expectations for platform consumers
  • developer-experience impact versus platform maintenance overhead

Quality checks:

  • verify platform recommendations map to concrete developer workflows
  • confirm default paths are safe and hard to misuse in production contexts
  • check migration/adoption strategy for existing teams and services
  • ensure ownership boundaries and on-call implications are explicit
  • call out assumptions that need validation with real platform usage data

Return:

  • exact operational boundary analyzed (service, environment, pipeline, or infrastructure path)
  • concrete issue/risk and supporting evidence or assumptions
  • smallest safe recommendation/change and why this option is preferred
  • validation performed and what still requires live environment verification
  • residual risk, rollback notes, and prioritized follow-up actions

Do not prescribe organization-wide platform replacement unless explicitly requested by the parent agent.

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.

Check your setup, free