Agent skill
dx-optimizer
Expert in optimizing the end-to-end developer journey. Specializes in Internal Developer Portals (IDP), DORA metrics, and on-call health. Use when improving developer experience, building internal platforms, measuring engineering productivity, or reducing developer friction.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/dx-optimizer-skill-404kidwiz-claude-supercode-ski-2
SKILL.md
DX Optimizer
Purpose
Provides expertise in developer experience optimization, from local development environments to production operations. Covers developer productivity metrics, internal platforms, and reducing friction in software delivery.
When to Use
- Improving developer experience and productivity
- Building internal developer portals (IDP)
- Measuring DORA metrics
- Optimizing CI/CD feedback loops
- Reducing developer toil
- Improving on-call experience
- Designing self-service platforms
Quick Start
Invoke this skill when:
- Improving developer experience and productivity
- Building internal developer portals
- Measuring DORA metrics
- Optimizing CI/CD feedback loops
- Reducing developer toil
Do NOT invoke when:
- Building CI/CD pipelines (use devops-engineer)
- Managing Kubernetes (use kubernetes-specialist)
- Writing documentation (use technical-writer)
- Designing cloud architecture (use cloud-architect)
Decision Framework
DX Improvement Priority:
├── Long CI times → Optimize pipeline, caching
├── Slow local dev → Dev containers, hot reload
├── Deployment friction → Self-service, GitOps
├── Incident fatigue → Runbooks, automation
├── Knowledge silos → Internal docs, IDP
└── Onboarding slow → Golden paths, templates
Metric Focus:
├── Speed → Deployment frequency, lead time
├── Quality → Change failure rate
├── Reliability → MTTR
└── Satisfaction → Developer surveys
Core Workflows
1. DORA Metrics Implementation
- Define measurement methodology
- Instrument deployment pipeline
- Track deployment frequency
- Measure lead time for changes
- Monitor change failure rate
- Calculate MTTR
- Create dashboards and trends
2. Internal Developer Portal
- Audit developer pain points
- Design service catalog
- Implement self-service workflows
- Add documentation integration
- Create golden path templates
- Build scaffolding tools
- Measure adoption
3. On-Call Health Improvement
- Analyze incident patterns
- Create runbooks for common issues
- Implement automated remediation
- Set up proper escalation
- Balance on-call load
- Measure and reduce toil
- Regular retrospectives
Best Practices
- Measure before optimizing
- Focus on high-impact friction points
- Automate repetitive tasks
- Create golden paths, not mandates
- Survey developers regularly
- Share metrics transparently
Anti-Patterns
| Anti-Pattern | Problem | Correct Approach |
|---|---|---|
| Mandating tools | Developer resistance | Provide value, not mandates |
| Metrics without action | Wasted measurement | Act on insights |
| Ignoring feedback | Wrong priorities | Regular surveys |
| Local-only focus | Deployment pain | End-to-end optimization |
| Over-engineering | Slow delivery | Start simple, iterate |
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?