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".
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
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".
compatibility
["claude-code","gemini-cli","github-copilot"]
author
OpenDirectory
version
1.0.0
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)
Read all three reference files BEFORE scoring.references/scoring-rubric.md, references/roast-voice-guide.md, . The rubric is non-negotiable — use the exact 10 dimensions.
references/readme-template.md
Score every dimension on the 0–10 scale. Never skip. Missing data = score 0, not "N/A".
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".
Tone matters. Default honest. Switch voice per references/roast-voice-guide.md. Brutal is funny but never personal. Kind is encouraging but still specific.
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.
Never invent URLs. When writing ideal-readme.md, use <placeholder> syntax for missing links. Roast will tell maintainer to fill in.
Never name maintainers or contributors. Roast the work, not the people.
Output exactly four files in dx-roast/. Do not write to other locations. Do not skip files.
Step 1: Intake
Required:
repo — local path (default .) OR https://github.com/owner/repo URL
Optional:
Parameter
Default
Description
tone
honest
brutal / honest / kind
output_dir
dx-roast/
Where to write the 4 output files
compare_to
none
Optional second repo URL for benchmark comparison
If repo is a URL: clone to a temp dir using git clone <url> /tmp/dx-roast-<short-hash>. Scan from there. Delete temp dir after run.
If repo is . or local path: scan in place, do not modify anything.
Step 2: Discover
Read these files (each may be absent — note absence):
.github/workflows/*.yml (just names + brief CI presence check)
If repo is a URL, also fetch via gh:
gh api repos/<owner>/<repo> --jq '{stars: .stargazers_count, forks: .forks_count, watchers: .subscribers_count, pushed_at, description, homepage, topics, default_branch}'
gh api repos/<owner>/<repo>/commits --jq '.[0].commit.author.date' | head -1
gh api repos/<owner>/<repo>/contributors --paginate --jq '[.[] | .login] | length'
Catch and continue if any GitHub call fails.
Step 3: Score 10 dimensions
For each of the 10 dimensions in references/scoring-rubric.md, output {score: 0–10, evidence: [...]} where evidence is a list of 1–3 short strings citing what you found.
Example:
"visual_proof":{"score":4,"evidence":["Found 1 screenshot at line 89 (below the fold)","No animated demo / gif","No video"]}
Sum scores → total (0–100) → grade (A/B/C/D/F per rubric).
Save to dx-roast/score.json with this exact shape:
{"repo":"<owner/repo or local path>","scanned_at":"<ISO 8601 timestamp>","dimensions":{"time_to_first_success":{"score":7,"evidence":["..."]},"what_is_this_clarity":{"score":5,"evidence":["..."]},"visual_proof":{"score":4,"evidence":["..."]},"install_simplicity":{"score":9,"evidence":["..."]},"runnable_quick_start":{"score":8,"evidence":["..."]},"documentation_depth":{"score":6,"evidence":["..."]},"examples":{"score":5,"evidence":["..."]},"community_signals":{"score":3,"evidence":["..."]},"trust_signals":{"score":7,"evidence":["..."]},"marketing_signals":{"score":4,"evidence":["..."]}},"total":58,"grade":"D","tone":"honest"}
Step 4: Write the roast
Read references/roast-voice-guide.md. Apply the requested tone. Write 250–500 words to dx-roast/roast.md.
If compare_to was provided, add a comparison line:
Benchmark: <other repo> scores <X>/100 (grade <Y>) — gap of <delta> points.
Self-QA (every run, before printing the terminal summary)
All 10 dimensions in score.json have score + evidence
Total equals sum of dimensions
Grade letter matches the total per rubric thresholds
Roast references at least 3 evidence items from score.json
Roast does not name any maintainer / contributor
Action plan has 5–10 items, sorted desc by priority
Ideal README is < 100 lines
Ideal README uses <placeholder> for any URL not found in scan
All 4 files exist in output_dir
No <TBD> / <TODO> placeholders in roast.md or action-plan.md
If any check fails, fix and re-run that step.
Error handling
These four failure modes get explicit handling — never let the skill silently produce a partial output without surfacing the cause.
Case
Behavior
repo doesn't exist OR can't be cloned OR can't be read
Exit immediately with the message Repo not found or inaccessible: <repo>. Do not write any output files.
README.md is missing
Run anyway. Score what_is_this_clarity, visual_proof, runnable_quick_start, and marketing_signals near 0. Use the absence as the opening of the roast ("No README is its own statement").
Repo is private + no GitHub auth available
Try a local clone (git clone <url>); if it fails, exit with Repo is private and no authentication is available. Suggest the user set GITHUB_TOKEN or pass a local path.
Continue without the benchmark. Add a single line to the roast: Note: requested benchmark against <compare_to> could not be fetched. Omit the Benchmark: line from the terminal summary.
Any GitHub API error (rate limit, transient 5xx) during Step 2 metadata fetch is caught and logged in score.json under trust_signals.evidence as "github metadata unavailable". The rest of the run proceeds.
