Verified:GitHub

devex-review

Measure developer experience friction in onboarding flows and CLI workflows.

Updated May 27, 2026

Search Tags:#developer tools #developer experience #workflow testing #dx audit #onboarding testing #time-to-hello-world #dx scorecard

Ready to run

npx skills add https://github.com/Shmurdoc/EasyRide-v1 --skill devex-review-shmurdoc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: devex-review
Source: https://github.com/Shmurdoc/EasyRide-v1/tree/main/.opencode/skills/gstack-devex-review
Command: npx skills add https://github.com/Shmurdoc/EasyRide-v1 --skill devex-review-shmurdoc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the gap between planned and actual developer experience by testing real user workflows instead of relying on static reviews of docs and onboarding flows. It catches hidden friction that causes developers to abandon your tool before they get value.

Core Features & Use Cases

Live Workflow Testing: Uses the browse tool to navigate docs, run the getting started flow, and measure time-to-hello-world (TTHW) as a real user would.
Evidence-Backed Reporting: Screenshots error messages, evaluates CLI help text, and generates a DX scorecard with concrete evidence of friction points.
Gap Analysis: Compares actual workflow performance against planned DX targets (e.g., a plan that says 3 minute onboarding vs. real 8 minute onboarding) to surface expectation-reality mismatches.
Use Case: Run this audit after shipping a new developer-facing feature to catch onboarding issues before they drive users away, or when a user asks to "test the DX" or "try the onboarding".

Quick Start

Use the devex-review skill to test your project's developer onboarding flow and generate a scorecard of friction points with supporting evidence.

Frequently Asked Questions about devex-review

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

FAQPage Schema

How do I test developer experience friction in my project's onboarding flow?▼

Testing developer experience friction involves executing live onboarding workflows rather than static reviews. This skill navigates docs, runs getting started flows, and measures time-to-hello-world to generate evidence-backed DX scorecards highlighting friction points.

What is a time-to-hello-world test for SDK onboarding?▼

A time-to-hello-world test measures the actual time a developer takes to reach a successful first API call. This skill executes the onboarding workflow as a real user, capturing performance metrics and error screenshots to validate getting started guides against planned targets.

How do I find expectation-reality gaps in my API documentation?▼

Finding expectation-reality gaps requires comparing actual workflow performance against planned DX targets. This skill evaluates CLI help text and onboarding flows, generating a DX scorecard that contrasts expected onboarding times with real user behavior results.

Can I audit CLI workflows and error messages for developer friction?▼

Auditing CLI workflows for developer friction involves capturing live error messages and evaluating help text. This skill runs CLI commands as a real user, taking screenshots of errors and measuring performance to build an evidence-backed DX scorecard.

What is the best way to run a DX scorecard audit after shipping a feature?▼

Running a DX scorecard audit post-launch involves testing real developer workflows to catch onboarding issues. This skill measures time-to-hello-world, screenshots friction points, and compares actual results against planned developer experience targets.

When should I not rely on static documentation reviews for developer onboarding?▼

Static documentation reviews miss hidden developer experience friction that causes user abandonment. You should move beyond static reviews when validating post-launch features, testing SDK onboarding, or checking if actual workflow performance matches planned DX targets.