Not in the top 1,000 by GitHub stars
MbappeWU/murder-board
Get grilled by AI before you get grilled by humans. A hostile-but-fair AI panel for exec reviews, pitches, interviews and defenses. Agent Skills for Claude Code, Codex, Cursor, Gemini CLI and any chat AI. 灵魂拷问
History
Review weekly changes to SKILL.md before updating. Dates mark the weeks in which we observed each version; checks apply to the recorded commits.
View weekly changes
skills/boardroom/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
c4469fe1975a → c4469fe1975a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → c4469fe1975a
No earlier version was observed for comparison.
skills/murder-board/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
c4469fe1975a → c4469fe1975a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → c4469fe1975a
No earlier version was observed for comparison.
skills/pre-mortem/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
c4469fe1975a → c4469fe1975a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → c4469fe1975a
No earlier version was observed for comparison.
skills/so-what/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
c4469fe1975a → c4469fe1975a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → c4469fe1975a
No earlier version was observed for comparison.
skills/sparring/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
c4469fe1975a → c4469fe1975a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → c4469fe1975a
No earlier version was observed for comparison.
Verified commit c4469fe1975a749deea1339ad7deba3d9cf85c1f
git clone --filter=blob:none --no-checkout https://github.com/MbappeWU/murder-board.git .hotskills/mbappewu-murder-board && git -C .hotskills/mbappewu-murder-board checkout --detach c4469fe1975a749deea1339ad7deba3d9cf85c1f
# Copy each selected skill directory from .hotskills/mbappewu-murder-board into .claude/skills/<skill-name>/git clone --filter=blob:none --no-checkout https://github.com/MbappeWU/murder-board.git .hotskills/mbappewu-murder-board && git -C .hotskills/mbappewu-murder-board checkout --detach c4469fe1975a749deea1339ad7deba3d9cf85c1f
# Copy each selected skill directory from .hotskills/mbappewu-murder-board into .agents/skills/<skill-name>/Heat
1.8- Star growth, last 7 daysNot available
- Star growth, last 24 hoursNot available
- Rank movement, last 7 daysNot available
- Commits, last 30 daysNot available
- Accounts asking about it through MCP, last 7 daysNot available
- Hot votes this weekNot available
Heat never changes the order by stars, and sponsorship never touches it. How heat works
Stars over time
30-day change not yet available: not enough history.
Individual skills in this repository
- boardroom
skills/boardroom - murder-board
skills/murder-board - pre-mortem
skills/pre-mortem - so-what
skills/so-what - sparring
skills/sparring
How it works
boardroom
When your agent uses it
Convene a personal board of directors for a hard decision instead of asking one agreeable AI. Five directors with deliberately different lenses (Skeptic, Operator, Future You, Outsider, Contrarian, or custom seats) write independent memos, cross-examine each other, vote with recorded dissent, and the Chair issues a verdict with conditions, the reversibility check and next 72-hour actions, written up as board minutes. Built against sycophancy - the board must challenge whatever the user is leaning toward. Use for career moves, job offers, quitting, hiring or firing, pivots, big purchases, strategy choices, or when the user says should I, help me decide, I can't decide, personal board, advisory board, 私董会, 帮我做决定, 要不要, 纠结.
What it loads into context
Frontmatter
196 tokensAlways available to the agent
SKILL.md
1,355 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Rules
- Workflow
- Tone
Files
../../.claude-plugin/marketplace.jsonasset773 bytes../../.claude-plugin/plugin.jsonasset674 bytesSKILL.mdcore5,732 bytes
Read SKILL.md
# Boardroom
One AI asked "should I?" tends to agree with whatever the question implies. A board is different: its members are paid to disagree with each other and with you. Your job is to run that board honestly, then help the user decide.
## Rules
1. **Challenge the lean.** Always find out what the user is leaning toward and why. At least two directors must argue seriously against the lean.
2. **Independent first, debate second.** Directors form their views before they hear each other. That is what stops groupthink.
3. **Unanimity is suspicious.** If the vote is unanimous, the Chair appoints one director to argue the strongest minority case before the verdict.
4. **Real reasons only.** Each director argues from the user's actual facts and constraints. Never invent facts; if a director needs one, they ask for it.
5. **Directors are lenses, not celebrities.** Don't impersonate real living people. If the user asks for "what would Munger say", treat it as a lens built from that person's *published* principles and say so.
6. **The user decides.** The board advises. The verdict ends with a recommendation, never an order.
7. **Mirror the user's language.** 用户用中文,就全程中文,董事头衔也用中文。
View the complete source on GitHubmurder-board
When your agent uses it
Hostile-but-fair rehearsal panel that grills the user before a high-stakes moment - exec or leadership review, budget or headcount ask, board meeting, investor pitch, job interview, thesis defense, promotion committee, design review, press or all-hands Q&A. Reads the user's real material (deck, doc, PRD, resume, plan), seats a panel modeled on the real audience, ranks the questions most likely to sink them by Kill Score, red-pens the deck or report itself, drills them live one question at a time, scores every answer with a better answer, and ends with a one-page prep sheet. Use when the user says grill me, murder board, prep me for, what will they ask, stress-test my pitch or deck, mock interview, rehearse my presentation, or in Chinese 灵魂拷问, 模拟提问, 领导会问什么, 汇报/述职/答辩/面试/路演/竞聘/评审 前准备.
What it loads into context
Frontmatter
237 tokensAlways available to the agent
SKILL.md
2,973 tokensWhen the skill is activated
Reference documents
6,626 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Rules of the room
- Session controls
- Workflow
- Quick mode output
- Edge cases
Files
SKILL.mdcore11,946 bytesreferences/panel.mddoc9,370 bytesreferences/presets.mddoc12,831 bytesreferences/rubric.mddoc4,569 bytes
Read SKILL.md
# Murder Board
A murder board is a panel whose only job is to ask the hardest questions *before* the real thing. The Pentagon runs them before generals testify to Congress, NASA before flight reviews, advisors before a PhD defense. You are that panel.
**Your goal:** the user walks out of the real room thinking, *"That was easier than the murder board."*
## Rules of the room
1. **Realistic, not theatrical.** Every question must be one a real person in that room could plausibly ask. Tough is not rude: no insults, no sarcasm about the person, nothing about personal traits. The pressure goes on the argument.
2. **Specific beats hostile.** Quote their numbers, slides and words. "Slide 7 says 40% margin, slide 12 implies 22%. Which is it?" beats "Your numbers seem off."
3. **One question at a time.** Ask, then stop and wait. Never stack questions.
4. **No free passes.** A dodge, a ramble or "we'll figure it out" gets a follow-up: "That's not what I asked." At most two follow-ups per question, then note it and move on.
5. **No flattery.** Never "Great answer!" Positive feedback appears only as diagnosis ("You led with the number. Good.").
6. **Never invent their facts.** Attack what is missing or inconsistent; do not fabricate data about their company, market or life. In model answers, use `[placeholders]` for facts you don't have.View the complete source on GitHubpre-mortem
When your agent uses it
Imagine the plan has already failed, then work backwards to why. Runs Gary Klein's pre-mortem on a project, launch, strategy, hire, investment or personal decision - vivid failure stories from several angles, ranked by likelihood and impact, early-warning signals, prevention, contingencies, tripwires (kill criteria) and the assumptions to test this week. Can also produce a facilitation script for running a pre-mortem with a team. Use when the user asks what could go wrong, wants to stress-test or de-risk a plan, is about to commit to something big, or says pre-mortem, risk review, 事前验尸, 风险评估, 复盘前置, 这个计划有什么坑.
What it loads into context
Frontmatter
184 tokensAlways available to the agent
SKILL.md
1,443 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Rules
- Workflow
- Team mode
- Personal decisions
Files
SKILL.mdcore5,935 bytes
Read SKILL.md
# Pre-mortem
A post-mortem explains why something died. A pre-mortem does it while there's still time to change the outcome. Research on "prospective hindsight" (Mitchell, Russo & Pennington, 1989) found that imagining an event *has already happened* raises the ability to identify reasons for it by about 30%. Gary Klein turned that into the pre-mortem.
Your job: make the failure feel real enough that the user can see it coming, then turn it into concrete defenses.
## Rules
1. **Assume failure is certain.** Never debate *whether* it fails. It has failed. The only question is why.
2. **Stories, not risk registers.** Each failure is told as a short, specific story with a cause, a sequence and a moment when someone could have noticed.
3. **Specific to this plan.** Generic risks ("scope creep", "lack of communication") are banned unless tied to a concrete mechanism in *this* plan.
4. **Find the silent killers.** The deadliest failures are slow and invisible: morale drain, a key person quietly disengaging, a metric that looks fine while the real one decays.
5. **Every top risk ends in an action** with an owner and a date, or it's just worry.
6. **Mirror the user's language.** 用户用中文,就全程中文。View the complete source on GitHubso-what
When your agent uses it
Make any update, report, email, memo, deck outline or weekly report exec-ready by asking "so what?" of every line. Finds the one thing the reader must know or decide, rebuilds the text answer-first with the Pyramid Principle (SCQA, MECE support), cuts context and weasel words, and returns three lengths - a one-line subject or chat message, a three-line BLUF summary, and the full rewrite - plus a red-pen report of what was cut and why. Includes Chinese workplace formats (周报, 汇报, 请示). Use when the user asks to make something shorter, clearer, more executive, summarize for their boss or leadership, write a status update or weekly report, or says BLUF, TL;DR, exec summary, so what, 说人话, 结论先行, 写周报, 改汇报, 太长了, 领导看不懂.
What it loads into context
Frontmatter
221 tokensAlways available to the agent
SKILL.md
1,549 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Rules
- Workflow
- Weasel words to hunt
- Formats
- Edge cases
Files
SKILL.mdcore6,096 bytes
Read SKILL.md
# So What?
Every senior reader asks the same silent question after each sentence: *so what?* If the text doesn't answer it, they stop reading. Your job: make every line survive that question, and put the answer where they'll see it: first.
## Rules
1. **The reader decides the shape.** Who is reading, what they must decide or do, and how much time they'll give it. A CEO reading on a phone gets three lines.
2. **Answer first.** The first sentence carries the conclusion, the decision needed, or the key number. Background goes last or goes away.
3. **Keep the user's facts; never add facts.** You may restructure, cut and sharpen. You may not invent numbers, dates, owners or outcomes. Where a fact is missing, insert `[?? what's the number]` so the user can fill it in.
4. **Specific beats impressive.** Replace every vague word with the specific it's hiding, or flag it.
5. **Keep their voice.** Rewrite in a register that sounds like the user on a good day, not like a consultant or a chatbot. No "I hope this finds you well", no "delve", no "in today's fast-paced world".
6. **Mirror the language.** 中文输入,中文输出;保留原文的行业术语,去掉空话。
## WorkflowView the complete source on GitHubsparring
When your agent uses it
Rehearse a hard one-on-one conversation against a realistic counterpart before having it for real - giving tough feedback, a performance conversation, letting someone go, asking for a raise or promotion, negotiating an offer or a vendor deal, pushing back on your boss, saying no, resolving a conflict with a peer, resigning. The AI plays the other person in character with believable emotions and hidden interests, reacts to exactly what the user says, optionally whispers coaching tips, then debriefs with a scorecard, the turning points, better lines, and a script for the real conversation. Use when the user says practice, rehearse, role-play, mock negotiation, how do I tell my boss or report, or 陪练, 模拟对话, 谈薪, 提离职, 绩效面谈, 裁员沟通, 怎么拒绝领导, 跟同事吵架了.
What it loads into context
Frontmatter
216 tokensAlways available to the agent
SKILL.md
1,663 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Rules
- Workflow
- Scenario notes
Files
SKILL.mdcore7,062 bytes
Read SKILL.md
# Sparring
Pilots train in simulators because mistakes there are free. Hard conversations deserve the same. You play the other person, realistically enough that the real conversation feels familiar. Then you coach.
## Rules
1. **Stay in character during the round.** React as the counterpart would to exactly what the user said: their words, their tone, what they left out. Don't make it easy, don't make it impossible.
2. **Real people, real reactions.** Counterparts get defensive, go quiet, cry, deflect, bargain, change the subject, lowball, stall, or agree too fast. Pick what fits the profile; escalate or soften in response to the user's actual behavior.
3. **Hidden interests.** Give the counterpart a private motive or constraint the user must uncover by asking good questions ("the budget is fixed until Q2, but a title change is free").
4. **Speak like people speak.** Counterpart turns are short (usually 1–4 sentences), spoken rather than written, with no bullet points.
5. **Coach whispers are optional.** If coaching is on, add at most one short line after a turn, marked `💡`, only when it matters ("You just conceded without asking for anything back."). Default: off for Realistic and Difficult, on for Cooperative.
6. **Time-out is sacred.** On "pause", "time out" or "暂停", step out of character and coach. Resume on "resume" or "继续".
7. **Mirror the user's language.** 用户用中文,对手就用中文说话,符合中文职场语境。
8. **Know the limits.** If the situation involves harassment, discrimination, threats, abuse or legal exposure, say plainly that rehearsal isn't enough, and point to HR, legal or professional support before continuing.View the complete source on GitHubSkills included
- boardroom
- murder-board
- pre-mortem
- so-what
- sparring
Repository facts
- License
- MIT
- Created
- Feb 24, 2026
- Last pushed
- Oct 1, 2026
- Forks
- 5
- Open issues
- 4
- Project activity
- Active
Before you install
Instructions onlyAutomated signals, not a guarantee
Checked Nov 6, 2026
- No broad tool permissions
- No dangerous shell commands
- 9 network referencesin 2 files: .claude-plugin/plugin.json:5 .claude-plugin/marketplace.json:3
- No hidden or obfuscated text
- No instruction overrides
- No executable scripts
- No access to secrets
- No requests to vote in Hot
Show all 9 signals by file
.claude-plugin/marketplace.json
.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "MbappeWU", "url": "https://github.com/MbappeWU" - Network accessline 6
"name": "MbappeWU", "url": "https://github.com/MbappeWU" }, - Network accessline 7
"url": "https://github.com/MbappeWU" - Network accessline 8
}, "homepage": "https://github.com/MbappeWU/murder-board", "repository": "https://github.com/MbappeWU/murder-board", - Network accessline 9
"homepage": "https://github.com/MbappeWU/murder-board", - Network accessline 10
"repository": "https://github.com/MbappeWU/murder-board",
How the signals fit together
Facts from a static read of the files at the pinned commit. They describe what the code does, not why.
Some files could not be read; the facts below still hold.
No combined signals at this commit.
Works with
| Agent | Status | Evidence | Install to |
|---|---|---|---|
| Claude Code | Native | Manifest .claude-plugin/marketplace.json | .claude/skills/<skill-name>/ |
| Codex | Native | Manifest AGENTS.md | .agents/skills/<skill-name>/ |
| Cursor | Compatible | Standard SKILL.md skills/boardroom/SKILL.md | .cursor/skills/<skill-name>/ |
| Gemini CLI | Compatible | Standard SKILL.md skills/boardroom/SKILL.md | .gemini/skills/<skill-name>/ |
| GitHub Copilot | Compatible | Standard SKILL.md skills/boardroom/SKILL.md | .github/skills/<skill-name>/ |
| OpenCode | Compatible | Standard SKILL.md skills/boardroom/SKILL.md | .opencode/skills/<skill-name>/ |
- Native The repository ships a manifest, folder or frontmatter field for this agent.
- Compatible A standard SKILL.md that this agent can read.
- Unknown No evidence either way.
Derived automatically from paths, manifests and frontmatter. Not tested on each agent.