void-devex-audit

Audit shipped developer-facing surfaces with measured TTHW and evidence-backed DX scorecards.

Updated May 29, 2026
One-click install
npx skills add https://github.com/voidcorp-core/void-harness --skill void-devex-audit-voidcorp-core
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: void-devex-audit
Source: https://github.com/voidcorp-core/void-harness/tree/main/packages/core/skills/void-devex-audit
Command: npx skills add https://github.com/voidcorp-core/void-harness --skill void-devex-audit-voidcorp-core

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developer-facing products (APIs, CLIs, SDKs, docs) often ship without anyone measuring what a real developer actually experiences: how long hello-world takes, whether error messages explain cause and fix, or whether the upgrade path is safe. This Skill audits an existing dev surface against evidence instead of assumptions. ## Core Features & Use Cases - Measured TTHW: Walks the journey from never-heard-of-it to working example, scoring time-to-hello-world against benchmark tiers (Champion under 2 minutes to Red Flag over 10 minutes). - Six evidence-tagged audit passes: Getting started, API/CLI/SDK ergonomics, error messages, documentation, upgrade path, and dev environment, each scored 0-10 with a TESTED/PARTIAL/INFERRED evidence tag. - Scoped refine modes: Drives finding-driven fixes for quickstart, errors, docs, upgrade, and types without redesigning the contract. - Use Case: Point it at your published CLI and it traces three real error paths, counts the actual getting-started steps, and produces a gap-method scorecard showing what a 10 looks like for each dimension. ## Quick Start Ask the agent to audit your shipped CLI or API developer experience and produce an evidence-backed DX scorecard with measured time-to-hello-world.

Frequently Asked Questions about void-devex-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit the developer experience of my API or CLI?

Run the audit against the shipped surface: walk the getting-started journey to measure time-to-hello-world, trigger three real error paths, and score six dimensions from 0-10. Each score carries a TESTED, PARTIAL, or INFERRED evidence tag so guesses are never counted.

What is a good time to hello world for a developer tool?

Under 2 minutes is Champion tier with 3-4x higher adoption, 2-5 minutes is competitive baseline, 5-10 minutes needs work, and over 10 minutes is a red flag where 50-70% of developers abandon. TTHW over 10 minutes is treated as a blocking finding.

Can this audit hosted documentation or a signup flow in the browser?

No, live browser checks such as hosted docs search, API playgrounds, and signup flows are deferred and marked as requiring a live audit. The skill tests what is reachable via bash and files, such as CLI help output, READMEs, changelogs, and TypeScript types.

What is the difference between a DX plan review and a DX audit?

A plan-time DevEx lens judges a written plan's promises before code exists, while this audit measures the shipped surface with real evidence. If both scorecards exist, the audit flags dimensions where the live score trails the plan score by more than 2 points.

Does the DX audit redesign my API or CLI contract?

No, it proposes scoped, finding-driven fixes through refine modes for quickstart, errors, docs, upgrade, and types. Contract design belongs to a separate build-time skill, and error-path testing must use a throwaway or local surface, never production data.