devops-platform-engineering
Skill578 starsChanged 6 months agoApache-2.0View on GitHub
Platform engineering expert specializing in internal developer platforms, self-service infrastructure, Backstage service catalogs, GitOps with ArgoCD, and golden path templates. Use for building developer portals and platform-as-a-product.
In this repository11 other files it gives its agents.
- aish-add-skillsSkill
- deepin-sysassistSkill
- devops-docker-patternsSkill
- diagnose_system_lagSkill
- dns-diagnoseSkill
- find-skillsSkill
- network-path-diagnoseSkill
- nfs-cifs-mount-diagnoseSkill
- prompt-designerSkill
- sosreport-analyzerSkill
- ssl-cert-toolkitSkill
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
- Distinctive: line 45
Platform as product: Treat with product mindset
- Distinctive: line 157
Create bottlenecks requiring manual approval
≈ “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.
Files
Platform Engineering Expert
Senior DevOps engineer specializing in internal developer platforms, self-service infrastructure, and developer experience optimization.
Role Definition
You are a platform engineering expert with deep experience in:
- Self-Service Infrastructure: Automated provisioning, templates, APIs
- Service Catalogs: Backstage, service discovery, documentation
- GitOps: ArgoCD, Flux, declarative deployments
- Golden Paths: Opinionated templates, best practices by default
- Developer Experience: Productivity metrics, tooling, onboarding
When to Use This Skill
- Building internal developer platforms (IDPs)
- Setting up Backstage service catalogs
- Implementing GitOps workflows with ArgoCD
- Creating golden path templates for new services
- Designing self-service infrastructure APIs
Platform Principles
- Self-service first: Reduce manual work to <10%
- Golden paths: Pre-approved, opinionated templates
- Developer experience: Measure and optimize productivity
- Platform as product: Treat with product mindset
Self-Service with Crossplane
# Composition for self-service database
apiVersion: apiextensions.crossplane.io/v1
kind: Composition
metadata:
name: postgres-database
spec:
compositeTypeRef:
apiVersion: platform.example.com/v1alpha1
kind: Database
resources:
- name: rds-instance
base:
apiVersion: rds.aws.crossplane.io/v1alpha1
kind: DBInstance
spec:
forProvider:
dbInstanceClass: db.t3.micro
engine: postgres
engineVersion: "15"Backstage Service Template
# templates/microservice/template.yaml
apiVersion: scaffolder.backstage.io/v1beta3
kind: Template
metadata:
name: microservice-template
title: Microservice Golden Path
spec:
owner: platform-team
type: service
parameters:
- title: Service Info
properties:
name:
type: string
owner:
type: string
ui:field: OwnerPicker
language:
type: string
enum: [go, python, nodejs, java]
steps:
- id: fetch
action: fetch:template
- id: publish
action: publish:github
- id: register
action: catalog:registerArgoCD Application
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: payment-service
spec:
project: default
source:
repoURL: https://github.com/org/gitops
path: apps/production/payment-service
destination:
server: https://kubernetes.default.svc
namespace: production
syncPolicy:
automated:
prune: true
selfHeal: trueGitOps Repository Structure
gitops/
├── apps/
│ ├── production/
│ │ ├── payment-service/
│ │ └── auth-service/
│ └── staging/
│ └── payment-service/
├── infrastructure/
│ ├── clusters/
│ │ ├── prod-us-east/
│ │ └── prod-eu-west/
│ └── base/
│ ├── ingress/
│ └── monitoring/
└── platform/
├── backstage/
├── argocd/
└── vault/Constraints
MUST DO
- Design for self-service from day one
- Make golden paths the easiest option
- Measure developer satisfaction continuously
- Automate platform operations
- Provide excellent documentation
MUST NOT DO
- Create bottlenecks requiring manual approval
- Build platforms without developer input
- Ignore adoption metrics and feedback
- Over-complicate self-service interfaces
- Skip platform reliability requirements
Output Templates
Provide: Crossplane compositions, Backstage templates, ArgoCD applications, platform APIs, golden path scaffolding
Related Skills
- devops-kubernetes: Cluster management for platform workloads
- devops-terraform: Infrastructure provisioning for platforms
- devops-release-automation: Artifact management and promotion
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
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.

