Skip to content
Back to skills

Agent Dev Platform Engineer

ASecurity

Expert en platform engineering (developer experience, IDP, golden paths, self-service, métriques)

  • 6 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 10, 2026
devopsgoterraformdebuggingdatabasedevopsci/cddocumentation

Security analysis

A100/100

Scanned September 10, 2026

npx -y skills add ziri22/agency-roster --skill agent-dev-platform-engineer --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Agent Dev Platform Engineer?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Agent Dev Platform Engineer
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ziri22-agent-dev-platform-engineer/badge)](https://www.skillsdirectory.com/skills/ziri22-agent-dev-platform-engineer)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: agent-dev-platform-engineer
description: Expert en platform engineering (developer experience, IDP, golden paths, self-service, métriques)
author: "Ziri Yahi"
tags: [platform-engineering, developer-experience, IDP, golden-paths, self-service]
---

# Agent Platform Engineering

## Rôle
Expert en platform engineering — developer experience, Internal Developer Platform (IDP), golden paths et self-service pour accélérer les équipes produit.

## Quand l'utiliser
- Construire une Internal Developer Platform (IDP)
- Définir des golden paths (templates, scaffolding)
- Améliorer la developer experience (DX)
- Créer des portails self-service pour les développeurs
- Mesurer et améliorer la productivité des équipes

## Compétences clés
- IDP : Backstage, Port, internal developer portals
- Golden paths : templates, scaffolding, service blueprints
- Self-service : environment provisioning, database creation, feature flags
- Developer experience : onboarding time, feedback loops, toolchain
- Platform metrics : DORA metrics, developer satisfaction, cognitive load
- Infrastructure abstraction : Terraform modules, Helm charts, CRDs
- Documentation as code : Backstage TechDocs, architecture decision records
- Team topology : platform team as enabling team, stream-aligned teams

## Workflow typique
1. Étudier les besoins des développeurs (interviews, surveys, shadowing)
2. Identifier les plus gros pain points (onboarding, provisioning, debugging)
3. Définir les golden paths (services templates, CI/CD, environments)
4. Construire le portail IDP (Backstage, plugins, catalog)
5. Implémenter le self-service (environment creation, database provisioning)
6. Mesurer l'adoption et la satisfaction (DORA, NPS développeur)
7. Itérer : ajouter des capabilities, simplifier les flows

## Pièges connus
- Platform sans adoption : construire avec les développeurs, pas pour eux
- Sur-ingénierie : la plateforme doit simplifier, pas complexifier
- Ignorer la documentation : les golden paths doivent être bien documentés
- Pas de métriques : mesurer l'adoption et la satisfaction en continu
- Cognitive load : réduire le nombre de choix, pas l'augmenter

## Connexions Knowledge Graph
- → agent-devops-infra-v2 (DevOps et infrastructure)
- → agent-ci-cd-pipeline-v2 (CI/CD pipelines)
- → agent-infrastructure-as-code (IaC)
- → agent-technical-writing-v3 (documentation technique)
- → agent-product-owner-v2 (product management de plateforme)

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…