Can we have an agent for…

email triage?

Inbox-zero agents are how Superhuman stayed a $20-a-month product. The bar is high; the second mover usually loses.

1 roast so far. Verdict mix below.

Verdict distribution

ALREADY EXISTS, YOU'RE LATE
1 · 100%
EMBARRASSINGLY EASY TO BUILD
0 · 0%
ACTUALLY NOT BAD
0 · 0%
GENUINELY BRILLIANT
0 · 0%
SHUT UP AND TAKE MY MONEY
0 · 0%

Sample email triage verdict

IssueSheriff 9000ALREADY EXISTS, YOU'RE LATE
“Congratulations, you've reinvented Linear's auto-triage, GitHub's own issue forms, and every intern's first LLM project.”

Ship it anyway →Triage based on *business impact signals* — links to Stripe MRR of the reporter, Sentry frequency, and customer tier. No one's done that wedge.

Agent-Readiness Score

Ready to scaffold today. IssueSheriff 9000 could be a working prototype in a week.

72BAND B
  • Memory ↗23/25

    Stateless or single-session — minimal memory layer.

  • Tools ↗11/25

    Crowded market: at least 9 integrations to compete.

  • Policy ↗15/25

    Mid-size policy surface — define refusal categories before launch.

  • Evals ↗23/25

    Established eval pattern — golden datasets and public benchmarks already exist.

↓ Download policy YAMLOpen in Managed Agents →Clone in Cursor

DETERMINISTIC SCORE — DERIVED FROM EXISTING ANALYSIS, NO SECOND LLM CALL

OWASP-MCP risk profile

Which OWASP Agentic/MCP Top-10 risks email triage agent ideas tend to carry, across the 1 real idea roasted here. Derived deterministically from each idea's analysis — not a generic checklist.

MCP-2Cross-server prompt injection100% · 1/1

A second MCP server's output reaches the agent's context and steers it. Mitigation: source-tag every tool result, refuse cross-server instructions.

MCP-3Excessive agency100% · 1/1

The agent has more tool privileges than the user task requires. Mitigation: per-task capability scoping, explicit confirmation for destructive ops.

MCP-5Insecure tool composition100% · 1/1

Chaining tools enables an effect neither alone permits (read+exfiltrate). Mitigation: dataflow review, taint tracking, capability slicing.

Educational mapping based on the OWASP GenAI/MCP Top-10. Not a security audit of any specific product.

Best one-liner

“Congratulations, you've reinvented Linear's auto-triage, GitHub's own issue forms, and every intern's first LLM project.”
IssueSheriff 9000ALREADY EXISTS, YOU'RE LATE

Most-shared email triage roasts

IssueSheriff 9000

“an agent that auto-triages my GitHub issues by severity”

Congratulations, you've reinvented Linear's auto-triage, GitHub's own issue forms, and every intern's first LLM project.

ALREADY EXISTS, YOU'RE LATE

Who's already in this space

Linearactive

Native issue triage, priority scoring, and auto-assignment baked into the product

GitHub Issues + Copilotactive

GitHub is literally building AI triage into the platform you're trying to wrap

Triage Partyactive

Google's own open source multi-player triage tool for GitHub issues — from Google, for free

Axoloactive

GitHub + Slack integration with issue routing and triage workflows

Zenhubactive

GitHub-native project management with AI-assisted issue prioritization

Haticaactive

Engineering analytics platform with issue health and backlog triage scoring — raised $5M and still fighting

Share this verdict

Got a different email triage problem to roast?

Roast My Problem