devex-review

Audit developer onboarding flows and generate evidence-based DX scorecards.

Updated May 9, 2026
One-click install
npx skills add https://github.com/kk20300113-png/my-claude-skills --skill devex-review-kk20300113-png
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devex-review
Source: https://github.com/kk20300113-png/my-claude-skills/tree/main/devex-review
Command: npx skills add https://github.com/kk20300113-png/my-claude-skills --skill devex-review-kk20300113-png

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developer experience is often claimed but never measured. Teams ship features without knowing if onboarding actually works, leading to documentation that looks good but fails real users. This skill provides empirical, evidence-based DX auditing by actually testing workflows.

Core Features & Use Cases

  • Live DX Audit: Uses the browse tool to navigate documentation, try getting started flows, measure time-to-hello-world, and capture error screenshots.
  • Evidence-Based Scorecards: Compares planned vs actual metrics (for example, "plan said 3 minutes, reality says 8") to produce actionable DX scores.
  • Proactive Suggestions: Automatically recommends auditing after shipping developer-facing features to catch onboarding regressions early.

Quick Start

Use the devex-review skill to audit the current project's developer onboarding flow and generate a DX scorecard with empirical evidence.

Frequently Asked Questions about devex-review

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

FAQPage Schema
How do I measure developer experience for my SDK onboarding flow?

You measure developer experience by empirically testing documentation and onboarding flows to capture actual time-to-hello-world metrics and error screenshots. This Skill navigates getting started guides to produce evidence-based DX scorecards comparing planned versus actual timing.

What is an empirical developer experience audit and how does it work?

An empirical developer experience audit tests live workflows rather than reviewing documentation statically. It uses browsing tools to navigate CLI usability and onboarding flows, capturing timing metrics and screenshots to generate actionable DX scorecards with improvement recommendations.

How do I audit CLI usability and documentation after shipping a new API feature?

You audit CLI usability by running a live DX review that navigates your developer-facing features and onboarding workflows. This Skill proactively captures errors and measures actual onboarding time to catch regressions immediately after shipping pre-release features.

Can I use this developer experience scorecard for periodic API documentation audits?

Yes, this Skill applies to periodic audits of SDK or API onboarding experiences as well as pre-release validation. It empirically tests your developer workflows to generate scorecards containing timing metrics, error screenshots, and recommendations for DX improvements.

What is the best way to catch onboarding regressions in developer-facing features?

The best way to catch onboarding regressions is through proactive DX auditing that empirically tests workflows after shipping. This Skill automatically recommends auditing developer-facing features to compare planned versus actual onboarding metrics and capture real usability errors.

Do I need any specific testing dependencies to run a live DX audit?

No dependencies are required to run a live DX audit. This Skill operates independently to navigate your documentation and CLI workflows, measuring actual developer experience and generating evidence-based scorecards without needing external testing components.