platform-engineer

Automates design, deployment, and governance of internal developer platforms with GitOps and RBAC.

1|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/mtsatryan/openclaw-ai-agents --skill platform-engineer-mtsatryan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: platform-engineer
Source: https://github.com/mtsatryan/openclaw-ai-agents/tree/main/platform-engineer
Command: npx skills add https://github.com/mtsatryan/openclaw-ai-agents --skill platform-engineer-mtsatryan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Platform teams often battle fragmented tooling, slow provisioning, and inconsistent developer experiences across multiple environments. This Skill provides a blueprint for building internal developer platforms with self-service capabilities, GitOps workflows, and golden-path templates to accelerate delivery. It enables operators to design, deploy, and continuously improve scalable platforms with strong RBAC, observability, and documentation.

Core Features & Use Cases

  • Self-service platform provisioning and environment management
  • GitOps-driven deployments with standardized golden-path templates
  • Developer portal and API design for platform consumption
  • RBAC, auditing, and compliance automation
  • Observability, cost visibility, and onboarding automation
  • Platform API design and cataloging for multi-tenant environments

Quick Start

Describe your platform needs and request a self-service provisioning workflow.

Frequently Asked Questions about platform-engineer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build an internal developer platform with self-service provisioning?▼

Build an internal developer platform by automating self-service provisioning workflows and environment management. This approach standardizes GitOps deployments and golden-path templates to accelerate delivery and streamline the developer experience across multi-tenant organizations.

What is the best way to standardize GitOps workflows across multiple clusters?▼

Standardize GitOps workflows across multiple clusters by deploying standardized golden-path templates. This ensures consistent multi-environment operations, comprehensive RBAC, and audit trails while maintaining platform uptime and measurable adoption metrics.

Does this approach support multi-tenant environments requiring strict RBAC and audit trails?▼

Yes, this approach fully supports multi-tenant environments by automating RBAC, auditing, and compliance. It designs platform APIs and catalogs specifically for multi-tenant organizations seeking strong governance and standardized self-service capabilities.

How do I create golden-path templates for developer portals?▼

Create golden-path templates by defining standardized GitOps deployment processes within your internal platform. This streamlines developer portal consumption and API design while ensuring consistent onboarding and observability across engineering teams.

Can I measure developer experience and platform adoption metrics with this setup?▼

Yes, you can measure developer experience and platform adoption metrics. The platform design explicitly includes observability, cost visibility, and onboarding automation to track productivity and platform uptime comprehensively.

When should I not use a centralized internal platform for environment management?▼

Avoid a centralized internal platform if your organization does not require multi-environment standardization or strict RBAC. If your teams lack platform engineering maturity, the overhead of maintaining GitOps workflows and service catalogs may outweigh the self-service benefits.