devex-review

Test gstack onboarding from docs to setup and report a DX scorecard.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/mgher668/surf-ai --skill devex-review-mgher668
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devex-review
Source: https://github.com/mgher668/surf-ai/tree/main/.agents/skills/gstack/devex-review
Command: npx skills add https://github.com/mgher668/surf-ai --skill devex-review-mgher668

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This DX audit identifies friction in the onboarding flow and developer experience by actively testing docs, setup, and tooling, then reports findings with a DX scorecard and supporting evidence.

Core Features & Use Cases

  • Hands-on evaluation of the onboarding path, docs, and CLI flows to surface friction points.
  • Generates a DX scorecard with evidence, screenshots, and actionable recommendations.
  • Use Case: run during new feature onboarding or onboarding refresh to ensure a smooth developer experience.

Quick Start

Navigate the docs with the browse tool and run the evaluation to produce 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 onboarding and measure time-to-first-use?

To audit developer experience onboarding, you test the setup path from docs to CLI execution, measuring time-to-first-use and capturing errors to produce a DX scorecard. This Skill diagnoses onboarding friction by coordinating browse-based exploration with automated checks.

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

A DX scorecard evaluates developer experience by documenting friction points found during hands-on onboarding testing. It includes supporting evidence like error messages, screenshots, and CLI help text to provide actionable recommendations for improving the setup flow.

How do I capture evidence for developer experience friction during setup?

You capture developer experience evidence by navigating docs and running setup commands while recording error messages, screenshots, and CLI help text. This structured evidence gathering ensures reproducibility and supports the final DX scorecard findings.

Does this DX evaluation work for testing CLI flows and documentation navigation?

Yes, this DX evaluation works for testing CLI flows and documentation navigation by actively exploring the on-ramp from setup to first-run outcomes. It measures the actual developer experience by running automated checks against the CLI and help text.

When should I run a developer experience audit on my onboarding flow?

You should run a developer experience audit during new feature onboarding or onboarding refresh cycles to ensure a smooth setup flow. It identifies friction points in tooling and docs before developers encounter them.

What is the best way to test time-to-first-use for a CLI tool?

The best way to test time-to-first-use for a CLI tool is to run a hands-on evaluation of the onboarding path from docs to setup to first-run outcomes. This approach measures the actual time required and captures any setup errors encountered.