devex-review

Audit developer experience by live-testing onboarding flows and generating a DX scorecard.

3|14|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/cegit27/moodle-proctor --skill devex-review-cegit27
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devex-review
Source: https://github.com/cegit27/moodle-proctor/tree/main/.claude/skills/gstack/devex-review
Command: npx skills add https://github.com/cegit27/moodle-proctor --skill devex-review-cegit27

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developer experience is often an afterthought, leading to frustrating onboarding, unclear documentation, and wasted time for new users. This Skill automates the auditing process by actually testing the getting started flow, timing tasks, and capturing real error messages to produce an objective, evidence-based scorecard.

Core Features & Use Cases

  • Live Onboarding Testing: Navigates documentation and executes the actual getting started flow to identify friction points.
  • Performance Timing: Measures time-to-hello-world and compares it against planned benchmarks to spot unrealistic expectations.
  • Error Capture: Screenshots and records error messages, CLI help text, and broken links for concrete feedback.
  • Use Case: A team shipping a new CLI tool can run this audit to discover that the install command fails on fresh machines, or that the docs reference a flag that doesn't exist, fixing these issues before they lose users.

Quick Start

Use the devex-review skill to audit the developer experience of this project by testing the onboarding flow and generating a DX scorecard.

Frequently Asked Questions about devex-review

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

FAQPage Schema
How do I audit developer experience and onboarding flows for a new CLI tool?

A developer experience audit live-tests getting started flows by executing installation commands and navigating documentation to capture real error messages. It measures time-to-hello-world against planned benchmarks to generate an evidence-based scorecard highlighting friction points.

What is time-to-hello-world and how does it measure developer onboarding friction?

Time-to-hello-world measures the duration required to complete a project's getting started flow and successfully execute a basic command. Comparing this timing against planned benchmarks spots unrealistic expectations and reveals onboarding friction points.

How do I test documentation accuracy and capture broken links automatically?

Testing documentation accuracy requires browser automation to navigate docs, execute installation commands, and capture error states. The audit records broken links, CLI help text, and real error messages to provide concrete feedback for documentation fixes.

Does a DX audit work for developer-facing libraries and platforms, or just CLI tools?

A DX audit applies to developer-facing tools, libraries, and platforms where first-run setup, CLI usability, and documentation accuracy determine adoption. It evaluates the getting started flow across any software project requiring onboarding automation.

Do I need browser automation to run a developer experience scorecard audit?

Yes, browser automation is required to navigate documentation, execute installation commands, capture error states, and measure time-to-hello-world. This live testing approach ensures the scorecard reflects real user conditions on fresh machines.