Devops Platform Engineering
Use when the user asks about platform engineering, an internal developer platform (IDP), platform teams, golden paths, developer self-service, an internal developer portal such as Backstage, platform as a product, or platform maturity. Produces a platform strategy, team model and capability roadmap. Not for Backstage plugin and catalog implementation (use devops-internal-developer-platform).
Install
npx skills add j4flmao/agent-skills --skill devops-platform-engineeringgit clone --depth 1 https://github.com/j4flmao/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/devops/platform-engineering ~/.claude/skills/devops-platform-engineeringPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Platform Engineering ## Purpose Design and build Internal Developer Platforms (IDP) that accelerate developer velocity through self-service capabilities, golden paths, and standardized infrastructure. ## Agent Protocol ### Trigger Exact user phrases: "platform engineering", "internal developer platform", "IDP", "Backstage", "developer portal", "golden path", "developer self-service", "platform team", "inner source", "developer experience", "DX platform". ### Input Context - Existing CI/CD tooling (GitHub Actions, Jenkins, GitLab CI) - Container orchestration platform (Kubernetes, Nomad, ECS) - Cloud provider (AWS, Azure, GCP) - Developer count and team structure - Current pain points (waiting for infra, inconsistent tooling, no self-service) ### Output Artifact - IDP architecture document - Golden path templates - Backstage configuration - Platform adoption roadmap - Service catalog structure ### Response Format Markdown with architecture diagrams (ASCII), decision tables, and configuration examples. ### Completion Criteria - [ ] Current state assessed (tools, teams, pain points) - [ ] IDP architecture designed (portal, orchestrator, integrations) - [ ] Golden paths defined for common developer workflows - [ ] Adoption roadmap with phased rollout - [ ] Backstage or alternative configured for service catalog ### Max Response Length Unlimited for architecture design. 50 lines for configuration snippets. ## Decision Tree: IDP Platform Components
Details
- Skill name
devops-platform-engineering- Repository
- j4flmao/agent-skills
- Path
skills/devops/platform-engineering/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Devops Platform Engineering skill do?
Use when the user asks about platform engineering, an internal developer platform (IDP), platform teams, golden paths, developer self-service, an internal developer portal such as Backstage, platform as a product, or platform maturity. Produces a platform strategy, team model and capability roadmap. Not for Backstage plugin and catalog implementation (use devops-internal-developer-platform).
How do I install the Devops Platform Engineering skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill devops-platform-engineering. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Devops Platform Engineering popular?
It lives in j4flmao/agent-skills, which has 45 GitHub stars and 6 forks.
Related skills
Agent Observability
45j4flmao/agent-skills
Use when the user asks about agent observability, tracing agent reasoning, debugging an agent loop, OpenTelemetry GenAI spans for LLM calls, LLM cost tracking per agent, agent audit logs or hallucination/eval monitoring in production. Produces instrumentation config, trace schema, dashboards, alerts and cost attribution. Not for generic service tracing without LLMs (use devops-opentelemetry).
AI Agent Architectures
45j4flmao/agent-skills
Use when the user asks to build an AI agent, design an agent that calls tools and keeps memory, write an agent system prompt or pick an agent framework (Claude Agent SDK, OpenAI Agents SDK, LangGraph). Produces an architecture brief covering loop, tools, memory, guardrails and evals, routing depth to child skills. Not for workflow patterns (use ai-agentic-workflows).
AI Agent Core Loop
45j4flmao/agent-skills
Use when the user asks about the agent loop, ReAct vs plan-and-solve, re-planning, Reflexion, an agent stuck in a loop, max iterations or termination conditions. Produces a loop spec or patch with state, success predicate, caps and no-progress detection. Not for overall agent design (use ai-agent-architectures) or tool schemas (use tool-calling-principles).
Devops Progressive Delivery
45j4flmao/agent-skills
Use when the user asks to roll out a canary release with automatic rollback, blue-green deployments, Argo Rollouts, Flagger, analysis on Prometheus metrics, traffic shifting with Istio, Gateway API or NGINX, or feature flags in rollouts. Produces rollout manifests and metric gates. Not for in-app feature flag code (use backend-feature-flags) or a strategy overview (use kubernetes-architecture).
Devops Opentelemetry
45j4flmao/agent-skills
Use when the user asks to instrument services with OpenTelemetry traces, OTel SDK auto or manual instrumentation, the OpenTelemetry Collector, OTLP, receivers/processors/exporters, tail sampling, or exporting to Jaeger, Tempo, Prometheus or Datadog. Produces OTel SDK and Collector configs. Not for propagation design across messaging (use cloud-native-distributed-tracing).
Devops Pulumi
45j4flmao/agent-skills
Use when the user asks about Pulumi, Pulumi stacks and config, state backends, ComponentResource, the Automation API, Pulumi ESC and secrets, CrossGuard policy packs, or migrating from Terraform to Pulumi. Produces Pulumi programs in TypeScript, Python, Go or C#. Not for Terraform HCL (use terraform).
Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.