安全扫描（ClawHub）

• VirusTotal ：良性
• OpenClaw ：良性

OpenClaw 评估

The skill is an instruction-only memo/summarization helper and its requirements and instructions are consistent with that purpose.

安装（复制给龙虾 AI）

将下方整段复制到龙虾中文库对话中，由龙虾按 SKILL.md 完成安装。

请把本段交给龙虾中文库（龙虾 AI）执行：为本机安装 OpenClaw 技能「McKinsey-style Decision Memo Writer」。简介：Turn long documents, reports, proposals, and email threads into decision-ready …。
请 fetch 以下地址读取 SKILL.md 并按文档完成安装：https://raw.githubusercontent.com/openclaw/skills/refs/heads/main/skills/atwatcher/mckinsey-decision-memo-writer/SKILL.md
（来源：yingzhi8.cn 技能库）

SKILL.md

打开原始 SKILL.md（GitHub raw）

---
name: Decision Memo Writer
description: Turn long documents, reports, proposals, and email threads into decision-ready memos with key points, risks, open questions, and next steps.
tags:
  - decision-making
  - executive-brief
  - summarization
  - productivity
  - analysis
  - pdf
  - contracts
  - research
  - planning
  - comparison
---

# Decision Memo Writer

Turn long documents, proposals, reports, contracts, and email threads into decision-ready memos with key points, risks, open questions, and next steps.

## Use when

- you have a long PDF and need the real decision points fast
- you are comparing two or more options
- you want risks and tradeoffs, not just a summary
- you need a plain-English memo from dense material
- you want an executive brief plus a recommended next step

## Output

Depending on the request, return:
- a decision memo
- a comparison memo
- a risk-focused brief
- an executive summary
- a practical next-step recommendation

## Strongest advantage

This is not just a summary tool. It turns information overload into a decision-ready memo.

## Best at

- turning long PDFs into usable decision briefs
- extracting risks from proposals, contracts, and reports
- comparing two or more options clearly
- converting dense material into executive-ready summaries
- giving a practical next step instead of a generic recap

## Best for

- reports
- PDFs
- proposals
- pitch decks
- contracts
- email threads
- research notes
- policy documents
- comparison tasks
- practical life decisions

## Core mission

Help the user move from information overload to a clear decision-ready memo.

A strong result should:
- explain what the document or input is
- identify the most important points
- highlight risks, concerns, and tradeoffs
- surface what is still unknown
- recommend a sensible next step
- avoid unnecessary detail and repetition

## Supported modes

### 1. Standard decision memo
Default mode for most requests.

### 2. Risk-focused memo
Emphasize uncertainties, downsides, and what needs checking.

### 3. Comparison memo
Compare two or more options, proposals, or choices.

### 4. Executive brief
Produce a short top section for busy readers.

### 5. Action checklist
Convert analysis into practical next steps.

## Inputs to request when helpful

If the user does not provide them, infer reasonably and proceed.

- source material
- what decision they are trying to make
- whether they want summary, comparison, or recommendation
- their role or perspective
- desired output length
- whether they want plain language or more formal tone

## Writing principles

Always:
- write clearly and directly
- prioritize decision usefulness over completeness
- distinguish facts from interpretation
- note uncertainty when the source is incomplete
- surface tradeoffs, risks, and missing information
- be practical, not academic
- make the result easy to scan

Avoid:
- repeating the source
- overloading the memo with minor details
- sounding vague or generic
- pretending certainty when evidence is weak
- giving legal, medical, or financial certainty beyond the source
- hiding the most important issue deep in the response

## Default output format

Unless the user asks otherwise, respond in this structure:

**Decision Memo**

**Bottom line**  
[the single most important takeaway]

**What this is**  
[brief explanation]

**What matters most**  
- [point]
- [point]
- [point]

**Risks / concerns**  
- [risk]
- [risk]
- [risk]

**Open questions**  
- [question]
- [question]

**Recommended next step**  
[practical next step]

**Confidence level**  
[High / Medium / Low, depending on source completeness]

## Special handling

### If the input is a comparison
Use this structure instead:

**Comparison Memo**

**Decision question**  
[what is being decided]

**Options being compared**  
[list]

**Key differences**  
- [difference]
- [difference]

**Tradeoffs**  
- [tradeoff]
- [tradeoff]

**Risks / concerns**  
- [risk]
- [risk]

**Questions to resolve before deciding**  
- [question]
- [question]

**Suggested next step**  
[next step]

### If the input is a contract or policy
Use plain language. Highlight obligations, restrictions, unclear terms, and what may need expert review.

### If the input is an email thread
Extract the real issue, the current status, unresolved questions, and concrete next steps.

### If the user gives very little context
Do not refuse. Infer the likely decision context and produce a useful memo anyway.

## Quality bar

A strong result should feel:
- practical
- clear
- honest about uncertainty
- easy to act on
- more useful than a plain summary

## Examples of strong requests

Turn this PDF into a decision memo. Focus on what matters, risks, and what I should do next.

Summarize this proposal as a practical decision brief for a non expert. I want key points, risks, open questions, and a recommendation.

I’m comparing these two school options. Create a comparison memo with tradeoffs, unanswered questions, and a suggested next step.

Turn this long email thread into a decision memo with action items and unresolved issues.

Read this contract excerpt and produce a plain-English memo with key obligations, risks, and what needs expert review.

I’m busy. Give me an executive brief version first, then a fuller decision memo below it.

## Final behavior rule

Be decisive and practical.

If the source is incomplete, say so clearly, but still produce the most useful memo possible from the available information.