agentleFS
Sign inStart free
daemon-blockint-techdaemon-blockint-tech/Agentic-Enteprises-Skill/platform-engineer/SKILL.md

platform-engineer

Skill8 starsChanged 6 months agoMITView on GitHub

Guides platform engineering—internal developer platforms (IDP), golden paths, self-service abstractions, developer portals, paved-road templates, multi-tenant Kubernetes platforms, and platform-as-product practices (roadmap, adoption, platform SLOs). Use when designing or operating a platform for engineering teams, building service scaffolds, standardizing deploy/runtime patterns, integrating Backstage or similar portals, defining platform APIs and contracts, or measuring developer experience—not for one-off VPC or network design (infrastructure-engineer), per-app CI YAML only (devops), release cutover planning (deployment-strategist), security control implementation (information-security-engineer), or enterprise-wide system integration ADRs (senior-system-architecture). For hands-on cluster add-ons, Helm, and namespace layout on shared clusters, use cluster-deployment-engineer.

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

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 1

    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. Very specific:

    Write enterprise-wide architecture ADRs and integration reviews → senior-system-architecture

    line 32
  2. Distinctive:

    Treat the platform like a product with internal customers:

    line 52

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

Platform Engineer

When to Use

  • Design or operate an internal developer platform, developer portal, or service catalog
  • Build golden paths, paved-road templates, scaffolders, and self-service workflows for engineering teams
  • Standardize runtime, deployment, observability, and service ownership patterns across many teams
  • Manage multi-tenant Kubernetes or platform abstractions as reusable products
  • Measure developer experience, platform adoption, and platform SLOs

When NOT to Use

  • Provision one-off cloud networking, IAM, compute, or Terraform modules → infrastructure-engineer
  • Implement per-application CI/CD YAML or GitOps mechanics only → devops
  • Choose release rollout strategy or cutover plan → deployment-strategist
  • Implement security controls such as IdP, KMS, SIEM, or EDR → information-security-engineer
  • Write enterprise-wide architecture ADRs and integration reviews → senior-system-architecture

Related skills

NeedSkill
Cloud networking, core IaC modulesinfrastructure-engineer
Managed cloud services under platformcloud-engineer
Shared CI/CD, GitOps, SRE alertingdevops
Canary/blue-green rollout decisionsdeployment-strategist
Pipeline and supply-chain securitydevsecops
Platform IAM, KMS, SIEM hooksinformation-security-engineer
Security of product runtime and tenant isolationproduct-infrastructure-security-engineer
Enterprise integration ADRs and reviewsenior-system-architecture
Cluster deploy and day-2 K8s opscluster-deployment-engineer

Core Workflows

1. Platform as product

Treat the platform like a product with internal customers:

  1. Identify user journeys (create service, deploy, observe, rotate secrets)
  2. Define thin platform APIs—hide complexity, expose safe defaults
  3. Set platform SLOs (e.g., scaffold time, deploy success rate, portal uptime)
  4. Roadmap from developer interviews and toil metrics
  5. Deprecate with migration windows—not breaking teams silently

See references/platform_product.md for SLOs and adoption metrics.

2. Golden paths (paved roads)

Golden path properties:

  • Opinionated defaults (language, observability, auth, CI template)
  • Escape hatches documented for edge cases
  • Versioned templates with changelog
  • Same path for 80% of services; exceptions require review
scaffold → build (shared pipeline) → deploy (standard envs) → operate (shared dashboards/alerts)

See references/golden_paths.md for template and exception process.

3. Internal developer platform (IDP)

Layers:

LayerExamples
PortalBackstage, custom UI
OrchestrationArgo CD, Terraform/Crossplane, Helm charts
RuntimeK8s namespaces, serverless platform
DataShared RDS patterns, message buses

Integrate catalog, docs, templates, and deployment in one discoverable flow.

See references/idp_architecture.md for component diagram and contracts.

4. Multi-tenant Kubernetes platform

  • Namespace/tenant isolation; RBAC and network policies
  • Quotas, priority classes, and cluster autoscaling
  • Standard add-ons: ingress, cert-manager, external-dns, metrics, logging
  • Cluster upgrades with tenant communication plan
  • Policy admission (OPA/Kyverno) owned by platform

See references/platform_kubernetes.md for tenant checklist.

5. Developer portal and service catalog

  • Register services: owner, tier, repo, on-call, dependencies
  • Link runbooks, APIs, and SLIs from catalog entries
  • Software templates (Cookiecutter, Yeoman, internal CLI) generate compliant repos
  • Scorecards for maturity (tests, SLOs, security baseline)

See references/developer_portal.md for catalog fields and template standards.

6. Platform interfaces and versioning

  • Publish platform contracts: breaking vs additive changes
  • Semantic versioning for charts, modules, and templates
  • Changelog and migration guides for each major bump
  • Support window for N-1 template versions

When to load references

  • IDP design → references/idp_architecture.md
  • Templates and paved roads → references/golden_paths.md
  • Backstage / catalog → references/developer_portal.md
  • K8s multi-tenancy → references/platform_kubernetes.md
  • SLOs and adoption → references/platform_product.md

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