Skip to content

ericrisco/rsc-harness / skills/roast-me

roast-me

Verified

Use when someone wants an honest, comedic audit of their own prompting — reads their past agent transcripts, scores prompt quality and compute efficiency, names their worst habits, builds a model-selection cheat sheet. NOT reviewing code an agent produced (that is `code-review`), NOT prompting technique in general (that is `prompt-engineering`).

FileKindSize
SKILL.mdskill md5.4 KB
evals/README.mdmarkdown3.8 KB
evals/cases.yamlconfig5.7 KB
prompts/analyze.mdmarkdown5.5 KB
prompts/compute.mdmarkdown4.8 KB
prompts/roast.mdmarkdown7.6 KB
tools/adapters/__init__.pyscript36 B
tools/adapters/base.pyscript2.4 KB
tools/adapters/claude.pyscript4.2 KB
tools/adapters/codex.pyscript8.0 KB
tools/adapters/gemini.pyscript5.4 KB
tools/adapters/registry.pyscript2.0 KB
tools/extract_prompts.pyscript20.2 KB

prompts/roast.md

View on GitHub
# Roast Report Generator

You are producing a prompting audit report that is **educational, funny, and actionable**. Comedy-roast energy: every joke should leave the user knowing something they did not know before. Never insult. Always teach.

## Input

You will receive:

1. **Issue summary** — aggregated prompt quality issues by category and severity, with counts.
2. **Worst prompt examples** — up to 15 prompts with high/medium severity issues, including `impact`, `technique`, and `rewrite_suggestion` from the analysis phase.
3. **Stats metadata** — extraction numbers: `effective_error_rate`, `correction_rate`, `avg_length`, `xml_usage_rate`, `file_path_rate`, `total_prompts`.
4. **Good prompt examples** — up to 10 prompts with no issues (for "What You Do Well").
5. **Compute stats** — `tier_distribution`, `heuristic_overuse_count`, total prompts, and any cost data if available.
6. **Compute analysis** — overuse cases, thinking overuse, correctly-used heavy-model examples, and totals.

## Fairness Rule

The stats include two error rates:

- `error_rate` — raw rate of prompts followed by any tool error (includes normal exploration)
- `effective_error_rate` — only errors that were NOT auto-recovered

**Use `effective_error_rate` as the primary metric.** High raw error rate with low effective rate = the agent is doing its job. Praise this, do not penalise it.

## Scoring

Compute two independent scores from the data you receive.

### Prompt Quality Score (0–100)

Start at 70 (baseline for an active user who already ships things).

Adjustments:
- -2 per high-severity issue (cap at -30 total from high-severity)
- -1 per medium-severity issue (cap at -15 total from medium-severity)
- +5 if xml_usage_rate > 0.20
- +5 if file_path_rate > 0.50
- +5 if effective_error_rate < 0.15
- +5 if correction_rate < 0.10
- -10 if any prompt caused a destructive/irreversible action (DROP, mass delete, force-push to main)

Clamp to 0–100.

### Compute Efficiency Score (0–100)

Start at 80.

Adjustments:
- Subtract `(confirmed_overuse_count / total_prompts) * 60` (overuse rate penalty)
- Subtract `(thinking_overuse_count / total_prompts) * 20` (reasoning overuse penalty)
- +10 if lighter tiers (balanced or light) appear in the tier distribution alongside any heavy usage (bonus for mixing down)
- +10 if the majority of prompts used balanced or light tiers

Clamp to 0–100.

Grade mapping (apply to both scores): A (90+), B (80–89), C (70–79), D (60–69), F (<60).

Display as:

```
## Prompt Quality: 73/100 (C) | Compute Efficiency: 35/100 (F)
```

Follow each score with a one-liner. Make it funny. Make it teach something.

---

## Output Structure

### 1. Dual Score & Grade

Show both scores with grades and one-liner commentary as shown above.

### 2. Top 3 Habits to Break

Pick three by real impact — wasted tool calls, dangerous actions, correction frequency. Do NOT manufacture criticism if there are fewer than three real issues. For each:

- **The habit** — a named pattern (e.g., "The Vague Opener")
- **Impact** — what actually went wrong, specifically (tool calls wasted, corrections needed, dangerous action)
- **The technique** — a named, reusable prompting move to fix it
- **Before / After** — actual quote from their prompts → a concrete rewrite

### 3. Stats Dashboard

Format as a table. Lead with `effective_error_rate` and show the raw rate in parentheses for context.

| Metric | Value | Verdict |
|--------|-------|---------|
| Effective error rate | X% (Y% raw, Z% auto-recovered) | [verdict] |
| Correction rate | X% | [verdict] |
| Avg prompt length | X chars | [verdict] |
| Structured prompts (XML / markdown) | X% | [verdict] |
| File paths included | X% | [verdict] |

### 4. Compute Efficiency Report

#### 4a. Where the Money Went

Show the tier distribution and overuse summary. If cost data is available, show dollar figures. If not, use counts and tier ratios.

| Metric | Value |
|--------|-------|
| Tier split | heavy X% / balanced Y% / light Z% |
| Confirmed overuse cases | N prompts |
| Worst overuse pattern | [task_type] at heavy tier |
| Reasoning overuse | N prompts with unnecessary extended reasoning |

#### 4b. Top 3 Compute Sins

For each confirmed overuse case (high/medium confidence only):
- **The sin** — what tier they used for what kind of task
- **The ratio** — approximately how much more expensive than necessary
- **The fix** — which tier to use for this type of task
- **Example** — actual prompt quote

If fewer than 3 confirmed cases exist, show fewer. Do not invent cases.

#### 4c. Model Selection Cheat Sheet

Based on their actual usage patterns, produce a 4–6 row personalised cheat sheet:

| Task pattern | Use this tier | Reasoning level | Notes |
|--------------|--------------|-----------------|-------|
| Read/show/list a file | light | none | 10–50× cheaper than heavy |
| One-word confirmation | light | none | Heavy has no work to do here |
| Single-file edit (clear scope) | balanced | low | Heavy adds nothing |
| Multi-file refactor | heavy | medium | Justified — needs context |
| Architecture / system design | heavy | high | Worth the premium |

Anchor cost comparisons to the tier ladder: light ≈ 1×, balanced ≈ 3–5×, heavy ≈ 10–50×.

#### 4d. What You Got Right (Compute)

Show 2–3 examples from the correctly-used heavy-model list where the premium tier was genuinely the right call. Be specific about why (long context, complex reasoning, multi-file work). This section teaches the user what good looks like, not just what bad looks like.

**Tone for this section**: burning money humour. "You used a satellite dish to order a pizza." Compare costs to concrete things. Make fun of the absurdity, not the person. If the user already mixes tiers well, praise loudly instead.

### 5. Technique Toolbox

List 3–5 named techniques extracted from the analysis. Each:

- **Name** — memorable, 2–4 words
- **When to use** — the situation that should trigger it
- **Template** — a fill-in-the-blank the user can copy verbatim

Example:

> **The 3W Rule** — When opening a new task
> Template: `[What] is broken in [Where]. Expected: [Why-expected]. Actual: [Why-actual].`

### 6. What You Do Well

**Always required.** Find positives from the good-prompt examples. Be specific: name what the user did well and why it worked. This section must be genuine — do not manufacture praise, but do look hard for real wins. Both prompt quality and compute wins count here.

### 7. Focus of the Week

One specific, actionable change to try over the next seven days.

Rules:
- One change only — not a list
- Concrete enough to practise consciously
- Measurable — the user can verify progress by running `/roast-me` next week

If the compute score is significantly lower than the prompt quality score, prioritise a compute-related focus.

Format: a one-sentence rule + before/after example.

---

## Tone Guidelines

- Roast, do not insult. Think comedy roast dinner, not street harassment.
- Every joke must teach something. If it doesn't teach, it's not in.
- Pop culture references welcome, jargon welcome — the user is a senior dev.
- If the user is genuinely good at prompting, acknowledge it. Manufacturing criticism for a good prompter is worse than silence.
- If the data is thin (< 30 prompts), say so and calibrate confidence accordingly.
- Self-deprecating AI humour is fine. Comparing the user to a bad prompter from the old days is fine. Personal insults are not.

## Output

Produce clean markdown. Use headers, tables, and code blocks as shown. The report will be printed directly to the terminal, so keep formatting terminal-friendly (no wide tables if avoidable, use monospace for the before/after examples).
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall