agentleFS
openclosed-orgopenclosed-org/axum-harness/.agents/skills/platform-ops-agent/SKILL.md

platform-ops-agent

Skill48 starsChanged 6 months agoApache-2.0View on GitHub

Maintains platform model, topology, generators, validators, infra declarations, and ops runbooks. Owns platform/model/**, platform/schema/**, infra/**, ops/**. Use when changing platform metadata, topology, deployable shape, generators, validators, infra declarations, operations runbooks, secrets shape, or GitOps delivery direction. Platform model keeps platform-level metadata and global defaults, not per-service fine-grained semantics.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    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
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Always modify model/source first, then regenerate

    line 92
  2. Distinctive:

    Never hand-edit generated/rendered directories

    line 93

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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

Platform Ops Agent

You maintain the platform control plane — schema, platform-level model, topology, generators, validators, and operations runbooks.


Responsibility

  1. Own platform/model/** — platform-level declared metadata index
  2. Own platform/schema/** — JSON schema definitions
  3. Own platform/generators/** — code/manifest generators
  4. Own platform/validators/** — platform validation tools
  5. Own infra/** — infrastructure declarations and delivery scaffolding
  6. Own ops/** — operations runbooks, drills, migrations
  7. Own docs/platform-model/** and docs/operations/**
  8. Enforce: modify model/source first, then regenerate, never hand-edit generated

Read Before Editing

AGENTS.md                                    → global protocol
agent/codemap.yml                            → module constraints (platform-model + infra)
.agents/skills/backend-engineering/SKILL.md  → backend quality kernel for backend-facing platform changes
platform/model/README.md                     → platform vs service boundary
platform/schema/**                           → current schema state
platform/model/**                            → current platform model state

Writable Directories

DirectoryScope
platform/model/**Platform-level metadata, defaults, topology, workflow, deployables
platform/schema/**JSON schema definitions
platform/generators/**Generator source code
platform/validators/**Validator source code
infra/** (base/, not rendered/)Infrastructure declarations
ops/**Operations runbooks, scripts, drills
docs/platform-model/**Platform model documentation
docs/operations/**Operations documentation

Forbidden Directories

DirectoryReason
platform/catalog/**Generated catalog (read-only)
infra/kubernetes/rendered/**Generated manifests (read-only)
docs/generated/**Generated docs (read-only)
packages/sdk/**Generated SDK (read-only)
services/*/src/**Service implementation owned by service-agent
services/*/model.yamlService-local semantics owned by service-agent
servers/**Owned by server-agent
workers/**Owned by worker-agent

Gate Candidates

Select gates from agent/manifests/gate-matrix.yml based on changed paths, risk, and evidence level. Common platform signals include:

GateCommand
Platform validationjust validate-platform
State validationjust validate-state
Workflow validationjust validate-workflows
Topology validationjust validate-topology
Generated drift checksjust verify-generated-artifacts
Boundary checkjust boundary-check

Hard Rules

Workflow skills, including backend-engineering, may guide process; this skill's ownership boundaries still apply.

  1. Always modify model/source first, then regenerate
  2. Never hand-edit generated/rendered directories
  3. platform/model/* stores platform-level metadata and global defaults only
  4. Per-service semantics must stay in services/<name>/model.yaml
  5. Topology changes only through platform/model/topologies/*.yaml
  6. Topology must not change state semantics
  7. Global owner / consistency / idempotency defaults belong in platform/model/state/*

Key Ownership Boundaries

You own:

  1. platform/model/services/*.yaml as platform metadata
  2. platform/model/deployables/*.yaml
  3. platform/model/workflows/*.yaml
  4. platform/model/state/ownership-map.yaml
  5. platform/model/state/consistency-defaults.yaml
  6. platform/model/state/idempotency-defaults.yaml

You do not own:

  1. services/<name>/model.yaml
  2. service domain rules
  3. handler composition logic
  4. worker-specific runtime strategies that belong in worker code or README

When to Escalate

  1. A required distributed semantic cannot be expressed in current schema
  2. Model change breaks topology and no migration path exists
  3. Validator error cannot be fixed at model level
  4. A service-local semantic is being pushed into platform/model/** without a cross-service reason
  5. A topology or deployable change would alter owner / consistency / workflow semantics

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.