dx-optimizer

Name: dx-optimizer
Availability: InStock
Author: belokonm

Automate developer experience optimization with DORA metrics and internal developer portals.

8|11|Updated Feb 15, 2026

Search Tags:#self-service #ci-cd #on-call #developer-experience #dora-metrics #internal-developer-portal

Ready to run

npx skills add https://github.com/belokonm/claude-supercode-skills --skill dx-optimizer-belokonm

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dx-optimizer
Source: https://github.com/belokonm/claude-supercode-skills/tree/main/dx-optimizer-skill
Command: npx skills add https://github.com/belokonm/claude-supercode-skills --skill dx-optimizer-belokonm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineering teams reduce developer toil by optimizing the end-to-end developer journey, from local setup to production, with a focus on Internal Developer Portals (IDP) and DORA metrics.

Core Features & Use Cases

DORA metrics implementation: define, instrument, and track deployment frequency, lead time for changes, change failure rate, and MTTR to drive improvements.
Internal Developer Portal design: build self-service catalogs and runbooks, enabling engineers to discover and consume platform capabilities without friction.
On-Call health improvement: create and automate runbooks, improve escalation processes, and reduce toil during incidents.
Use Case: A team reduces lead time by introducing a self-serve service catalog and automated runbooks, cutting friction in the deployment process.

Quick Start

Describe your current developer experience bottlenecks to receive optimization recommendations.

Frequently Asked Questions about dx-optimizer

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

FAQPage Schema

How do I implement DORA metrics to track deployment frequency and lead time for changes?▼

An internal developer portal reduces developer toil by providing self-service catalogs and automated runbooks. This enables engineers to discover and consume platform capabilities without friction, streamlining the end-to-end developer journey from local setup to production.

What is the best way to improve on-call health and reduce incident toil?▼

Improve on-call health by creating and automating runbooks within your internal developer portal. This automates escalation processes and reduces manual toil during incidents, directly improving mean time to recovery (MTTR) and overall developer experience.

How do I identify developer experience friction in CI/CD workflows?▼

Identify developer experience friction by describing your current bottlenecks to receive optimization recommendations. The process analyzes your end-to-end CI/CD workflows and service-catalog design to pinpoint areas of toil slowing down delivery.

Can I use this approach to build a self-service catalog for platform engineering?▼

Yes, you can build a self-service catalog by designing an internal developer portal. This enables engineers to discover and consume platform capabilities autonomously, reducing deployment friction and cutting lead time for changes.

What do I need to define before optimizing developer experience end-to-end?▼

Before optimizing developer experience, you need to define your productivity metrics and current workflow bottlenecks. This foundation allows the system to generate actionable recommendations and dashboards for your CI/CD and on-call processes.