devex-review

Audit developer experience by timing onboarding flows and generating a DX scorecard.

1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/westn/gstack-pi-port --skill devex-review-westn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devex-review
Source: https://github.com/westn/gstack-pi-port/tree/main/port/gstack/devex-review
Command: npx skills add https://github.com/westn/gstack-pi-port --skill devex-review-westn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

DX teams spend hours verifying onboarding flows and finding hidden friction. This skill automates a live developer experience audit by navigating docs with the browse tool, timing interactions, and collecting evidence to produce a DX scorecard.

Core Features & Use Cases

  • Live DX audit by exploring docs and getting started flows using the browse tool.
  • Time-to-hello-work measurement and evidence collection to produce a scorecard.
  • Comparative evaluation against planned DX benchmarks to guide improvements.

Quick Start

Run the devex-review skill and use the browse tool to navigate docs and start the onboarding flow.

Frequently Asked Questions about devex-review

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

FAQPage Schema
How do I automate a developer experience audit for onboarding flows?

Automate a developer experience audit by navigating documentation with the browse tool, timing getting started interactions, and capturing evidence to produce a DX scorecard with actionable insights.

What is time-to-hello-work measurement in developer experience testing?

Time-to-hello-work measurement tracks the duration of a getting started flow during a DX audit, capturing timing data and evidence to evaluate onboarding friction and generate a scorecard.

How do I measure onboarding friction in getting started documentation?

Measure onboarding friction by using the browse tool to navigate getting started documentation, recording interaction timings, and capturing screenshots to identify hidden friction points.

Can I benchmark developer experience scorecards against planned DX targets?

Yes, the DX audit supports comparative evaluation against planned DX benchmarks, using captured timing and evidence from the onboarding flow to guide improvements.

Do I need the browse tool to run a DX audit scorecard?

Yes, the browse tool is required to navigate documentation, record timings, and capture screenshots during the live DX audit to generate the scorecard.

What are the limitations of automated developer experience testing?

This DX audit applies specifically to onboarding, getting-started flows, and developer-experience testing across the gstack-pi-port repository, requiring access to documentation and timing capabilities.