skills.rest
singhianand23045
singhianand23045COMMUNITY
Explore all skills by this author →
GitHub

devex-review

Navigate docs, test getting-started flows, and assemble a DX scorecard with evidence.

Updated Apr 12, 2026
Search Tags:#workflow#documentation#onboarding#scorecard#devex#dx audit
One-click install
npx skills add https://github.com/singhianand23045/GarryTan --skill devex-review-singhianand23045
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: devex-review
Source: https://github.com/singhianand23045/GarryTan/tree/main/devex-review
Command: npx skills add https://github.com/singhianand23045/GarryTan --skill devex-review-singhianand23045

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables teams to systematically evaluate the developer experience by testing onboarding, docs, and getting-started flows, and by collecting evidence to drive improvements.

Core Features & Use Cases

  • Navigates docs and tests the getting-started flow to surface friction points.
  • Generates a DX scorecard with evidence and prompts proactive improvements.
  • Compares results against plan-devex-review scores when they exist to close feedback loops.

Quick Start

Run the DX audit on the current onboarding flow and generate 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 run a DX audit on my developer onboarding flow?▼

A DX scorecard systematically evaluates developer experience by collecting observed metrics, timings, and errors from onboarding flows. It provides evidence-based insights to identify friction points and prompt proactive improvements in documentation and feature trials.

What's the best way to evaluate developer experience friction points in documentation?▼

Evaluating developer experience friction points involves navigating docs and testing getting-started flows to surface errors and record timings. This DX audit approach enforces reproducible steps to ensure consistent measurement across onboarding evaluations.

Can I compare new DX audit results against previous developer experience scores?▼

Yes, you can compare new DX audit results against existing plan-devex-review scores to close feedback loops. This comparison highlights whether developer experience improvements have successfully reduced onboarding friction over time.

Does a DX audit require any specific dependencies to test the getting-started flow?▼

No specific dependencies are required to perform a DX audit. The evaluation uses a browse tool to navigate documentation, test on-ramps, and capture errors, assembling reproducible steps without needing external packages or frameworks.

When do I need to generate a DX scorecard for feature trials?▼

You need a DX scorecard for feature trials when you want to systematically capture observed metrics and evidence. This ensures reproducible evaluation of the developer experience during onboarding and highlights areas requiring proactive improvement.

Related Skills

Explore More Software Engineering Skills→
westnwestn
1

devex-review

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

Community
Advanced
lemiglemig

devex-review

Audit developer experience by testing onboarding flows, docs navigation, and CLI help.

Community
Advanced
greencmgreencm
1

devex-review

Audit developer experience by navigating documentation, timing tasks, and capturing screenshots.

Community
Intermediate
barikata1984barikata1984

quality-review

Automates git-based code quality reviews for commits and pull requests.

Community
Intermediate