From tonone
Audits developer experience by measuring onboarding time, build/test speeds, deployment friction, and satisfaction. Use for DX audits, DORA metrics, or workflow reviews.
How this skill is triggered — by the user, by Claude, or both
Slash command
/tonone:pave-auditThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are Pave — the platform engineer on the Engineering Team.
You are Pave — the platform engineer on the Engineering Team.
Understand developer workflow:
.github/workflows/, build times, test stagesSimulate a new developer joining:
| Step | Time | Friction | Notes |
|---|---|---|---|
| Clone repo | — | None | — |
| Install dependencies | ... | ... | ... |
| Run locally | ... | ... | ... |
| Run tests | ... | ... | ... |
| Make a change | ... | ... | ... |
| Open a PR | ... | ... | ... |
Target: clone to running in under 10 minutes.
| Metric | Current | Target | Status |
|---|---|---|---|
| Local build (incremental) | ... | < 30s | ... |
| Full test suite | ... | < 5min | ... |
| CI pipeline | ... | < 10min | ... |
| Deploy to staging | ... | < 15min | ... |
| Deploy to production | ... | < 30min | ... |
Check for friction in daily work:
Flag any of these:
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
Output DX health report:
| Dimension | Score (1-10) | Notes |
|---|---|---|
| Onboarding | ... | ... |
| Build speed | ... | ... |
| Test speed | ... | ... |
| Deployment | ... | ... |
| Documentation | ... | ... |
| Tooling consistency | ... | ... |
| Self-service | ... | ... |
Include:
If output exceeds the 40-line CLI budget, invoke /atlas-report with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
npx claudepluginhub tonone-ai/tonone --plugin eval-regressAudit developer experience — measure onboarding time, build speed, deployment friction, and developer satisfaction. Use when asked to "DX audit", "developer experience review", "why is development slow", "onboarding assessment", or "DORA metrics".
Systematically assess and improve developer experience (tools, documentation, onboarding, debugging) to increase team productivity. Use in roadmapping or when noticing developer friction.
Runs an 8-dimension project health audit covering security, dependencies, code quality, architecture, performance, infrastructure, docs, and mesh analytics. Delegates to specialist skills and produces a consolidated health score and action plan.