skills.rest
Scivor
ScivorCOMMUNITY
Explore all skills by this author →
Website𝕏@Scivor_AIGitHub

devex-review

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

Updated Apr 11, 2026
Search Tags:#onboarding#cli#docs#dx#developer-experience#scorecard
One-click install
npx skills add https://github.com/Scivor/helm --skill devex-review-scivor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: devex-review
Source: https://github.com/Scivor/helm/tree/main/skills/gstack/devex-review
Command: npx skills add https://github.com/Scivor/helm --skill devex-review-scivor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates and streamlines evaluating developer experience by actively testing onboarding, docs, and CLI flows to surface friction and evidence for improvement.

Core Features & Use Cases

  • Live DX audit: navigate getting started, docs, and CLI help to surface blockers.
  • DX scorecard: collate findings with evidence and compare against plan-devex-review benchmarks when available.
  • Actionable improvements: generate concrete recommendations to reduce friction and improve developer productivity.

Quick Start

Ask me to run a DX audit on the current project and I will start a live developer experience test using the browse tool.

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 friction in onboarding flows?▼

A developer experience audit actively navigates getting started guides, documentation, and CLI help to surface friction and collect concrete evidence for an actionable DX scorecard.

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

A DX scorecard collates friction findings with concrete evidence gathered from live testing of developer tooling flows, comparing results against available benchmarks to highlight productivity blockers.

How do I test CLI help and documentation flows for developer friction?▼

You can test CLI help and documentation flows by running a live DX audit that uses browse capabilities to navigate commands and docs, automatically surfacing friction and collecting actionable evidence.

Can I benchmark developer experience findings against existing scorecards?▼

Yes, you can benchmark developer experience findings by comparing the generated DX scorecard against plan-devex-review benchmarks when available, providing relative context for your friction findings.

Does a developer experience audit require browse access to test docs?▼

Yes, the DX audit requires browse access to actively test documentation, commands, and onboarding flows, ensuring that friction is surfaced through real interaction rather than static analysis.

What are the limitations of automated developer experience audits?▼

Automated DX audits are limited to navigating docs, CLI help, and onboarding flows to surface friction, meaning they evaluate tooling evaluation paths but do not assess backend infrastructure or runtime performance.

Related Skills

Explore More Software Engineering Skills→
legotec73legotec73

devex-review

Audit onboarding flows, docs navigation, and CLI usage to generate a DX scorecard.

Community
Advanced
vnmoorthyvnmoorthy
2

plan-devex-review

Analyze developer experiences to identify friction points and improvement opportunities.

Community
Advanced
stayconnectquickstayconnectquick

devex-review

Automate live developer-experience testing by navigating docs and timing onboarding steps.

Community
Advanced
vib795vib795

devex-review

Quantify developer friction in docs navigation, getting-started flows, and CLI usage.

Community
Advanced