devex-review

Audit developer experience by navigating docs, onboarding, and CLI help.

1|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/tblakex01/conductor-playground --skill devex-review-tblakex01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devex-review
Source: https://github.com/tblakex01/conductor-playground/tree/main/.claude/skills/gstack/devex-review
Command: npx skills add https://github.com/tblakex01/conductor-playground --skill devex-review-tblakex01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Live developer experience audits identify friction in docs, onboarding, and tooling by actively testing the developer journey and capturing evidence to drive improvements.

Core Features & Use Cases

  • Live DX audit uses the browse tool to navigate docs, verify getting started flows, and assess CLI help text.
  • Produces a DX scorecard with concrete evidence and compares results to plan-devex-review scores when available.
  • Provides actionable recommendations to improve onboarding and developer workflows, with follow-up tasks.

Quick Start

Invoke a live DX audit on your current project by triggering the dx audit workflow.

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 on my project?

A developer experience audit uses the browse tool to navigate documentation, verify getting started flows, and assess CLI help text. It actively tests the developer journey to identify friction and captures evidence to drive improvements.

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

A DX scorecard is a report generated after a live audit that quantifies developer experience quality. It provides concrete evidence from testing onboarding flows and CLI help, comparing results to planned scores when available.

Can I use this DX audit to test my CLI help text and documentation?

Yes, the DX audit uses the browse tool to navigate docs and assess CLI help text directly. It evaluates the actual developer journey, capturing evidence on friction points to produce actionable recommendations for improvement.

What's the best way to identify onboarding friction in developer documentation?

The best way to identify onboarding friction is a live DX audit that navigates getting started flows and verifies documentation. It actively tests the developer journey and returns a scorecard with evidence and next steps.

How does this live DX audit compare to planned developer experience review scores?

The live DX audit compares actual testing results to plan-devex-review scores when available. It generates a scorecard with concrete evidence from navigating docs and CLI help, returning actionable findings and suggestions for improvement.