devex-review

Audit developer experience by testing onboarding and docs, capturing timing and evidence.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Buckeyes22/weather-app --skill devex-review-buckeyes22
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devex-review
Source: https://github.com/Buckeyes22/weather-app/tree/main/docs/corpora/gstack/devex-review
Command: npx skills add https://github.com/Buckeyes22/weather-app --skill devex-review-buckeyes22

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Live developer experience audit that uses the browse tool to test onboarding, navigate docs, capture timing, and record evidence. Produces a DX scorecard and helps compare against plan-devex-review benchmarks when they exist.

Core Features & Use Cases

  • Hands-on DX testing: navigates docs, tests getting started flows, captures screenshots, and notes error messages.
  • Evidence-based scoring: outputs a DX scorecard with concrete evidence and comparisons to existing plan-devex-review scores.
  • Use cases: when asked to test the DX, perform a DX audit, or evaluate onboarding, or proactively suggest improvements after shipping a developer-facing feature.
  • Voice triggers: supports speech-to-text aliases like "dx audit" and "developer experience test".

Quick Start

Invoke the devex-review skill to run a live DX audit on the current project 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 perform a developer experience audit to measure onboarding friction?

A developer experience audit tests onboarding flows by navigating docs, capturing screenshots, and recording timing and errors. This generates a DX scorecard with concrete evidence to identify and measure developer experience issues.

What is a DX scorecard and how does it evaluate developer onboarding?

A DX scorecard is an evidence-based report that evaluates developer onboarding by capturing timing, errors, and screenshots during live navigation tests. It provides structured comparisons against existing benchmarks to ensure repeatable results.

How do I test CLI help and docs navigation for developer experience issues?

Testing CLI help and docs navigation involves using browser-like navigation to simulate user flows, capturing screenshots, and noting error messages. This hands-on DX testing identifies friction points and assembles concrete evidence.

Can I compare my live DX audit results against existing benchmarks?

Yes, you can compare live DX audit results against existing plan-devex-review benchmarks. The audit performs a structured comparison against these plans to measure onboarding friction and ensure repeatable results.

When should I run a DX audit on my developer-facing project?

Run a DX audit when onboarding friction or CLI and doc issues are suspected, or proactively after shipping a developer-facing feature. It applies when asked to test the developer experience and identify areas needing improvement.

Does a developer experience audit require browser-like navigation and screenshot capture?

Yes, a developer experience audit requires browser-like navigation and screenshot capture to test getting started flows and assemble evidence. This approach captures real timing and errors to accurately measure DX issues.