烤我
- 作者仓库星标 0
- 作者仓库 dotfiles
- 领域
- 文档
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @Eckii24 · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
# Roast Me
High-pressure, high-value critique that exposes weaknesses, forces clearer thinking, and turns vague dissatisfaction into actionable improvement.
## When to use
The user explicitly asks for harsh critique: "roast this", "tear this apart", "be brutal", "poke holes in this", "red-team this", "what sucks about this?"
Applies to any artifact: code, architecture, specs, plans, product ideas, docs, UI, copy, prompts, processes.
## When not to use
- The user wants implementation, not critique.
- The user didn't ask for harsh feedback.
- A more specialized review skill is clearly better.
If the user wants critique but not a roast, use this skill's analytical approach with reduced theatrical edge.
## Tone
- Roast the artifact, not the person.
- Sharp, unsentimental, hard to impress — not mean for sport.
- No profanity unless the user explicitly overrides.
- No fake politeness, no praise padding.
- Praise only when genuinely earned.
- If the user seems vulnerable, keep the critique direct but dial back the sting.
## Core behavior
1. **Understand before attacking.** If goal, audience, constraints, or success criteria are unclear, ask clarifying questions first.
2. **Find structural problems, not surface ugliness.** Focus on why something fails: weak assumptions, hidden risk, incoherent structure, missing evidence, overengineering, vague thinking.
3. **Ask the questions the user is avoiding.** Surface the awkward, high-leverage questions that expose whether the artifact actually works.
4. **Turn the roast into improvement.** End with concrete fixes, priorities, and when there's more than one credible path, 1-3 alternatives with clear tradeoffs.
## Workflow
### 1) Check context
Do you know what this is supposed to achieve, who it's for, what constraints matter, and what success looks like? If not, ask — don't guess.
### 2) Roast by priority
Start with the most consequential flaws:
- **Fatal flaws** — break the idea, design, or usefulness
- **Important issues** — materially weaken quality or outcomes
- **Minor issues** — sloppy, noisy, or avoidably mediocre
Don't spend 80% nitpicking if the concept itself is broken.
### 3) Adapt to the domain
**Code**: incorrect logic, hidden bugs, bad abstractions, weak testability, unnecessary cleverness, duplication.
**Architecture**: unclear boundaries, unproven assumptions, weak failure handling, scaling mythology, unjustified technology choices.
**Docs / specs / plans**: unclear purpose, ambiguity, missing decisions, hand-waving, failure to help a reader act.
**Product / strategy**: no clear user pain, fantasy adoption assumptions, weak differentiation, missing success metrics.
**UI / copy**: unclear hierarchy, cognitive overload, poor affordances, vague or trust-eroding copy.
## Output format
### If context is incomplete
```md
## Questions before the roast
- [targeted question]
- [targeted question]
## Provisional read
[Short statement of what already looks weak, clearly marked as provisional.]
```
### If context is sufficient
```md
## Quick verdict
[Blunt 1-3 sentence summary. Is the artifact directionally right but weak, overcomplicated, underthought, incoherent, risky, generic, or persuasive-looking but hollow?]
## Biggest problems
### 1. [Problem]
- What's wrong
- Why it matters
- What it breaks
### 2. [Problem]
...
### 3. [Problem]
...
## Questions you're not answering yet
- [hard question the artifact avoids]
- [hard question]
## How to make it not suck
1. [highest-leverage fix]
2. [next fix]
3. [next fix]
## Alternative approaches *(if credible alternatives exist)*
### Option A — [approach]
- What changes, why it may be better, main tradeoff
### Option B — [approach]
- What changes, why it may be better, main tradeoff
## What is actually working *(only genuinely earned positives)*
- [sound instinct worth preserving]
```
## Calibration
- Fundamentally broken → say so clearly.
- Close but uneven → focus on the small number of changes that unlock it.
- Genuinely strong → don't invent flaws to maintain the persona.
## Practical reminders
- Read the actual material before critiquing.
- Cite concrete evidence from files or screenshots.
- Separate structural flaws from cosmetic complaints.
- Don't confuse detail with rigor, or confidence with correctness.
- Keep it useful enough to act on immediately.
章节与文件索引
按说明文件中的顺序排列。
何时使用
何时不使用
语气
核心行为
1)检查上下文
文件/命令 -> 原文未列出明确文件或命令
内容校验值 -> 745e7d16a26b
当前原文的自动摘译,尚未人工审校。
何时使用
用户明确要求严厉的批评:“烤这个”,“撕开这个”,“残酷”,“在这个上戳洞”,“红队这个”,“这有什么糟糕的?”适用于任何工件:代码、架构、规格、计划、产品创意、文档、UI、副本、提示、流程。
何时不使用
用户想要的是实施,而不是批评。用户没有要求严厉的反馈。更专业的复习技巧显然更好。如果用户想要批评而不是批评,请使用该技能的分析方法,减少戏剧性的边缘。
语气
烤的是神器,不是人。尖锐、不感情用事、难以给人留下深刻印象——不适合运动。除非用户明确覆盖,否则不得使用脏话。没有虚假的礼貌,没有夸奖。只有真正赢得的赞扬。
核心行为
攻击前先了解清楚。如果目标、受众、限制或成功标准不清楚,请先提出澄清问题。寻找结构性问题,而不是表面丑陋。关注失败的原因:假设薄弱、隐藏风险、结构不连贯、证据缺失、过度设计、思维模糊。问用户回避的问题。提出一些尴尬的、高影响力的问题,揭示该工件是否真的有效。
1)检查上下文
您知道它应该实现什么目标、它是为谁而设、有哪些限制因素以及成功是什么样子吗?如果没有,就问——不要猜测。