Audit developer onboarding workflows and produce evidence-based DX scorecards.
npx skills add https://github.com/a29paul/hexlens --skill devex-review-a29paul
Please help me install this Agent Skill. Skill: devex-review Source: https://github.com/a29paul/hexlens/tree/main/.claude/skills/gstack/devex-review Command: npx skills add https://github.com/a29paul/hexlens --skill devex-review-a29paul
This skill eliminates guesswork in developer onboarding by actually testing getting started flows, timing tasks, and capturing real error states instead of relying on assumptions about what works for developers.
Use the devex-review skill to audit the getting started flow for the current project and produce a DX scorecard with evidence of any friction points.
High-intent search queries and answers about installing and using this skill.
Time-to-hello-world is measured by running a live developer experience audit that tests actual onboarding workflows, times getting started tasks, and captures real error states to validate API setup. The audit produces a structured DX scorecard with concrete evidence of friction points.
A developer experience audit tests real onboarding workflows instead of relying on assumptions by using a browse tool to navigate documentation and run getting started flows. It evaluates CLI help text clarity, captures screenshots of error messages, and produces an evidence-based DX scorecard with timing data.
To audit developer onboarding friction points, run a live DX testing session that navigates your documentation, executes the getting started flow, and captures real error states. This process identifies friction points and generates a structured DX scorecard with actionable reports for onboarding improvements.
You can benchmark developer experience scorecards by comparing current live DX testing results against past planned scores to track improvement over time. This allows teams to catch discrepancies, such as when a planned 3-minute onboarding flow actually takes 8 minutes during real-world validation.
You should run a DX audit after releasing new features for developer-facing tools, APIs, or libraries to catch onboarding issues before they cause developer churn. The audit provides evidence-based scorecards with screenshots and timing data to guide onboarding improvements.
A developer experience scorecard includes screenshots of error messages, time-to-hello-world timing data, and actionable friction point reports. It provides concrete evidence of onboarding gaps by capturing real error states and evaluating documentation clarity during live workflow testing.
binfen1Audit developer experience by testing onboarding and producing a DX scorecard.
uzumaki-incAudits live onboarding flows and generates DX scorecards with evidence.
adryanmoldokkr32-pixelSimulate onboarding and navigate docs to produce an evidence-backed DX scorecard.
robertzengcnAudit live developer onboarding workflows and generate evidence-based DX scorecards.
