REA
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
汇报.skill · pitchcraft — Structured persuasion for tech leads, PMs, and founders: kickoff, status, wrap-up, pitch, and solution selling on one 5-part framework (Hook→Context→Proposal→Evidence→Ask), with AI material intake and a pre-submit checklist. Works with Claude Code, Cursor, Codex, and more.
作者提供的原文
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/skills/moshuying-pitchcraft)在同一工作中把 AI 连到服务的 MCP
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.
MCP server for terminal commands, file operations, and process management
同类工作,排序与 Skill 列表相同
| 本项 pitchcraft | rea | andrej-karpathy-skills | graphify | MoneyPrinterTurbo | |
|---|---|---|---|---|---|
| 作者 | moshuying | morluto | multica-ai | Graphify-Labs | harry0703 |
| Skill 数 | 1 | 1 | 1 | 1 | 1 |
| GitHub 星标 | 202 | 468,733 | 234,332 | 150,287 | 144,566 |
| 最近代码更新 | 2026年6月29日 | 2026年11月19日 | 2026年4月20日 | 2026年11月18日 | 2026年11月18日 |
| 许可证 | Apache-2.0 | MIT | – | Apache-2.0 | MIT |
moshuying 提供的 1 个 Skill(指令集),AI 读取后照做 · 不是 MCP server
MCP = 手
把 AI 连到外部服务或数据,例如读取 Notion 或开发票。需要有程序或服务器在运行。
Skill = 手册
教 AI 怎么做某项工作的文本文件,不连接任何服务。
有些会重叠:少数 Skill 带有调用工具的脚本,少数 MCP 只提供知识。请从你想完成的工作出发。
Claude CodeCodexCursor
依据开发者 README 和 repo 中的文件夹
GitHub 账号 moshuying(个人),已创建 8 年
★ 202 星,目前用户较少 · 代码最近更新 2026年6月29日
有 1 个可以在电脑上运行的脚本:scripts/install.js
脚本中没有发现联网命令
没有发现 hook 或写入电脑设置的操作
根据仓库 commit e27ca8a 中的文件自动检查(只读取文件,没有运行任何内容)。这不是安全保证,请自己阅读后再决定
第一步:你用哪个 AI?
选择你用的应用,本页只显示该应用的安装方法
无法上传到 claude.ai,因为描述超过 200 个字符(353 个字符)。请改用"让 AI 帮你安装"
复制这句话,粘贴到 Claude Code 的对话中
如果只用于一个项目,请粘贴到在该项目文件夹中打开的对话里 · AI 在安装前一定会先告诉你路径
AI 会先说明要做什么,每一步都会征求你的同意
重新打开 Claude Code,输入 /pitchcraft,或直接提出相关任务,Claude 会自动选用
Checked against official docs 2026年11月12日 · Source: code.claude.com
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
正在检查命令 · 通过后才会显示复制按钮
摘自开发者 README,会下载并运行开发者的代码
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
正在检查命令 · 通过后才会显示复制按钮
ChatGPT 桌面应用内置 Codex,Codex 从 ~/.agents/skills 文件夹读取 Skill
在 ChatGPT 桌面应用中打开 Codex,把这句话粘贴到对话中
AI 在安装前一定会先告诉你路径
AI 会先说明要做什么,每一步都会征求你的同意
把 pitchcraft 文件夹放到 ~/.agents/skills/pitchcraft
~ 是你的主文件夹($HOME)
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
正在检查命令 · 通过后才会显示复制按钮
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
不能使用你自己安装的 Skill,只能使用目录中插件自带的 Skill
想在 ChatGPT 中使用这个 Skill,请按上面的方法使用 ChatGPT 桌面应用
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
复制这句话,粘贴到 Codex 的对话中 · 适用于 ChatGPT 桌面应用中的 Codex、Codex CLI 和 IDE 扩展
如果只用于一个项目,请粘贴到在该项目文件夹中打开的对话里 · AI 在安装前一定会先告诉你路径
AI 会先说明要做什么,每一步都会征求你的同意
Codex 会自动发现新安装的 Skill;如果没有出现,请重启 Codex · 使用方法:在 ChatGPT 中输入 @ 并选择 Skill · 在 Codex CLI 或 IDE 扩展中运行 /skills,或输入 $ 加 Skill 名称
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
正在检查命令 · 通过后才会显示复制按钮
复制这句话,粘贴到 Cursor 的对话中
如果只用于一个项目,请粘贴到在该项目文件夹中打开的对话里 · AI 在安装前一定会先告诉你路径
AI 会先说明要做什么,每一步都会征求你的同意
在 Cursor 的 Agent 聊天中输入 / 并选择 pitchcraft
Checked against official docs 2026年11月12日 · Source: cursor.com
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
正在检查命令 · 通过后才会显示复制按钮
适用于其他能读取 Skill 的应用。这句话列出了 Claude Code、Codex 和 Cursor 的路径,AI 会按你的应用选择 · 复制这句话,粘贴到应用的对话中
如果只用于一个项目,请粘贴到在该项目文件夹中打开的对话里 · AI 在安装前一定会先告诉你路径
AI 会先说明要做什么,每一步都会征求你的同意
Checked against official docs 2026年11月12日 · Source: code.claude.com, learn.chatgpt.com, cursor.com
其他支持 Agent Skills 的应用(如 Gemini CLI、GitHub Copilot)使用不同文件夹,请查看该应用的指南,再把含 SKILL.md 的文件夹复制过去。
已于 2026年11月11日 对照 Claude Code、Codex 和 Cursor 官方指南核实 skill 文件夹
以下文字来自开发者的 repo,不是 PopNx MCP 的指令
显示前 8,000 个字符 · 在 GitHub 打开完整文件
---
name: pitchcraft
description: Structured persuasion for tech leads, PMs, and founders—not activity logs. Five scenarios (kickoff, status update, wrap-up, investor pitch, solution selling) on one 5-part framework (Hook→Context→Proposal→Evidence→Ask). AI prompts for missing materials and audience context; pre-submit checklist. Claude Code plugin; Cursor, Codex, and chat via prompts.
---
**Languages:** English (this file) · 简体中文 → `SKILL.zh-CN.md`
# Persuasive briefings · Workflow
## Essence
This is not report writing—it is **persuasion**. In every scenario you do the same thing:
> In limited time, help a specific audience understand context, trust your judgment, and provide the support you need.
## Users & scenarios
| Role | Scenarios | Audience |
|---|---|---|
| Tech lead / engineering manager | Kickoff, milestone review, wrap-up | Business leaders, CTO, PMO |
| PM / product lead | Quarterly review, annual summary, requirements review | Director, VP |
| Founder / business owner | Investor pitch | Investors, partners |
| Pre-sales / solutions | Solution selling | Customer execs, technical evaluators |
---
## Core: 5-part persuasion framework
All briefing types share one backbone; section emphasis differs.
```
Part 1 · Hook
→ Why should they keep listening?
→ Opportunity / pain / urgency
Part 2 · Context
→ What is the situation?
→ What we have done and what we have
Part 3 · Proposal
→ What we will do / did?
→ Scope, path, pace
Part 4 · Evidence
→ Why we can succeed / succeeded?
→ Data, moat, team, cases
Part 5 · Ask
→ What do we need from them?
→ Decision / resources / partnership / investment
```
---
## Briefing types & templates
Each type is an instance of the 5-part framework.
### Project kickoff
**Goal:** Get leadership to approve start and allocate people and budget.
| Part | Section | Focus |
|---|---|---|
| Hook | Background & opportunity | Market, pain, competition, why now |
| Context | What we already have | Team, tech, data, prior assets |
| Proposal | Goals & scope | In/out of scope, milestones |
| Evidence | Why us | Differentiation, moat |
| Ask | Resources & risks | Support needed, top risks and mitigation |
```
# {Project} · Kickoff
## Background & opportunity
{Why now: market, pain, competition—2–4 sentences.
This is the persuasion entry—create “we should do this.”}
## What we already have
{Team, tech, data, business assets—not bragging, but trust.
Pattern: “We already have X, so this is not from zero.”}
## Goals & scope
**In scope**: {capabilities}
**Out of scope**: {explicit exclusions—prevent scope creep}
{Milestones and timeline}
## Why us
{Core difference vs alternatives. Moat: why others can’t or won’t match.}
## Resources & risks
{People / budget / cross-team needs
Top risk and mitigation}
```
### Status update
**Goal:** Convince leaders and stakeholders the work is on track and worth continued investment.
| Part | Section | Focus |
|---|---|---|
| Hook | One-line summary | 1–2 most important facts this period |
| Context | Period context | Position vs last period |
| Proposal | Key progress | By milestone or module |
| Evidence | Key metrics | Progress, quality, efficiency |
| Ask | Risks & decisions | Decisions and coordination needed |
```
# {Project} · Status update
## One-line summary
{1–2 facts; audience grasps core in 10 seconds}
## Key progress
{Completed items and metrics by milestone or module}
## Risks & response
Formula per item: {symptom} → {root cause} → {mitigation} → {status}
Decisions: options + recommendation—no open homework:
❌ "Dependency X uncertain—please advise"
✅ "Dependency X slipped 2 weeks. Option A (add people) vs B (move milestone). Recommend A; need Team Y support."
## Next phase
| Item | ETA | Dependencies | Risk |
|---|---|---|---|
```
### Wrap-up / annual review
**Goal:** Show delivered value and assets retained.
| Part | Section | Focus |
|---|---|---|
| Hook | Goal attainment overview | Did we succeed overall? |
| Context | Original goals | What we committed to |
| Evidence | Quantified outcomes | Data-led |
| Proposal | Lessons & assets | What remains |
| Ask | Next phase or handoff | What happens next |
```
# {Project} · Wrap-up / {Year} annual review
## Goal attainment
| Goal | Target | Actual | % | Notes |
|---|---|---|---|---|
Underperformance: root cause and improvement—say it before they ask.
## Core deliverables
3–5 items, each: {what} + {metric} + {business impact}
## Lessons
- **What worked**: reusable methods / architecture / process
- **What failed**: root cause + prevention
- **Assets left**: code / data / docs / team capability
## Next
If continuing → direction, goals, key results, resources
If ending → handoff so nothing is left unsupported
```
### Investor pitch
**Goal:** Spark interest for a deeper conversation.
| Part | Section | Focus |
|---|---|---|
| Hook | One-liner | Elevator pitch |
| Context | Market opportunity | Size, pain, why now |
| Proposal | Product | Solution, core features, stage |
| Evidence | Moat & traction | Tech, data, growth, team |
| Ask | Funding / partnership | Amount, use, milestones |
```
# {Project} · Pitch
## One-liner
{What we do, for whom, what value}
## Market opportunity
{Size, persona, pain, why now}
## Product
{How we solve, core features, architecture (brief), stage}
## Moat & traction
**Moat**: {tech / data / network / team—why others can’t}
**Metrics**: {users, growth, retention, revenue}
**Team**: {why this team can execute}
## Funding ask
{Amount, use of funds, milestones, next round goal}
```
### Solution selling
**Goal:** Convince customer executives your solution is the best fit.
| Part | Section | Focus |
|---|---|---|
| Hook | Pain alignment | Their problem in their words |
| Context | Current state | Gaps in status quo |
| Proposal | Solution | How we solve |
| Evidence | Cases & data | Proof |
| Ask | Partnership | How to start |
```
# {Project} · Proposal
## Pain alignment
{Customer language for the problem—accuracy builds trust fast}
## Current state
{Why status quo fails: features, cost, efficiency, risk}
## Our solution
{How we solve; capabilities and differentiation}
## Proof
{Same-industry cases with metrics}
{If no case: POC plan or demo roadmap}
## Partnership
{Engagement model, timeline, what we need from them}
```
---
## Writing rules
### 1. Their concerns first, your story second
❌ Five minutes on how hard the team worked and how clever the architecture is
✅ First sentence answers “why should I care?”
### 2. Risks need judgment
❌ "Servers occasionally timeout—please monitor"
✅ "Connection pool exhaustion; scaling in progress; expected recovery tomorrow"
### 3. Acknowledge peer teams first
❌ "We filled a gap no one else addressed"
✅ "Team X has a mature Y; we extend with Z"
### 4. Metrics need source and definition
❌ "Conversion improved 20%"
✅ "Conversion +20% (June vs May, same account pool)"
### 5. Bad news early when it matters
❌ Wins first, then buried "but we slipped"
✅ Lead with material risks, then progress
### 6. No homework for the audience
❌ "Next: keep pushing forward"
✅ "Integration Wed; risk is dependency Y—owner aligned"
---
## Workflow
```
Step 1 — Load memory
Read leader context, business positioning, format prefs.
Missing → ask user to supply.
Step 2 — Scenario & audience
User picks type (kickoff / status / wrap-up·annual / pitch / solution selling).
Probe audience:
□ Role and level?
□ How much do they already know?
□ Top concerns (tech / business / cost / time)?
Step 3 — Material intake
Check completeness by type; ask for gaps:
Kickoff:
□ Background / market analysis
□ Competitive landscape
□ Team capabilities
□ Goals and KPIs
□ Resources and budget
□ Timeline
Status:
□ Completed work this period
□ Key metrics (progress / quality / efficiency)
□ Risk list with judgment and mitigation
□ Next-phase plan
□ Decisions needed fr提问、分享技巧或报告无法使用。按“有帮助”数量排序。