dx-roaster
Brutally honest developer-experience audit for a GitHub repo. Scores 10 DX dimensions (time-to-first-success, README clarity, visual proof, install, quick-start, docs, examples, community, trust, marketing), writes a shareable roast in the requested tone (brutal/honest/kind), produces a prioritized action plan ranked by impact × effort, and sketches an ideal README. Trigger when user says "roast my repo", "audit my README", "dx audit", "developer experience review", "score my GitHub project", "before launch checklist", or "make my repo shareable".
npx skills add Varnan-Tech/opendirectory --skill dx-roaster --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# dx-roaster Roasts a GitHub repo's developer experience. Produces four files: `roast.md`, `action-plan.md`, `ideal-readme.md`, `score.json`. Built for OSS maintainers and dev-tool founders preparing for Show HN, Product Hunt, or any launch where the first five minutes matter. --- ## Critical rules (read before every run) 1. **Read all three reference files BEFORE scoring.** `references/scoring-rubric.md`, `references/roast-voice-guide.md`, `references/readme-template.md`. The rubric is non-negotiable — use the exact 10 dimensions. 2. **Score every dimension on the 0–10 scale. Never skip.** Missing data = score 0, not "N/A". 3. **Roast must cite specific findings.** Quote bad lines verbatim. Reference file paths. Cite line numbers when possible. Never write generic platitudes like "documentation could be better". 4. **Tone matters.** Default `honest`. Switch voice per `references/roast-voice-guide.md`. Brutal is funny but never personal. Kind is encouraging but still specific. 5. **Action plan is impact-ranked, not severity-ranked.** Use `impact × (1 / effort)`. A 5-minute fix that adds 10 points ranks above a 2-hour fix that adds 12 points. 6. **Never invent URLs.** When writing `
- Critical rules (read before every run)
- Step 1: Intake
- Step 2: Discover
- Step 3: Score 10 dimensions
- Step 4: Write the roast
- Step 5: Generate action plan
- Step 6: Generate ideal README
- Step 7: Terminal summary
- Self-QA (every run, before printing the terminal summary)
- Error handling
- Examples
- What this skill does NOT do
gh api repos/<owner>/<repo>/commits --jq '.[0].commit.author.date' | head -1 gh api repos/<owner>/<repo>/contributors --paginate --jq '[.[] | .login] | length'
What does the dx-roaster skill do?
Brutally honest developer-experience audit for a GitHub repo. Scores 10 DX dimensions (time-to-first-success, README clarity, visual proof, install, quick-start, docs, examples, community, trust, marketing), writes a shareable roast in the requested tone (brutal/honest/kind), produces a prioritized action plan ranked by impact × effort, and sketches an ideal README. Trigger when user says "roast my repo", "audit my README", "dx audit", "developer experience review", "score my GitHub project", "before launch checklist", or "make my repo shareable".
How do I install it?
Run `npx skills add Varnan-Tech/opendirectory --skill dx-roaster --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Varnan-Tech/opendirectory, a repository with 571 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.