What it does
汇报.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.
- Connects Instruction files the AI reads
- Account or key No key found in README or SKILL.md
- Category Coding
For makers: add a badge to your README
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/skills/moshuying-pitchcraft)Use together with
MCP servers that connect the AI to services for the same work
Fallow
Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.
Desktop Commander
MCP server for terminal commands, file operations, and process management
Similar Skills
Same kind of work, ordered like the Skills list
| This one pitchcraft | rea | andrej-karpathy-skills | graphify | MoneyPrinterTurbo | |
|---|---|---|---|---|---|
| Maker | moshuying | morluto | multica-ai | Graphify-Labs | harry0703 |
| Skills | 1 | 1 | 1 | 1 | 1 |
| GitHub stars | 202 | 468,733 | 234,332 | 150,287 | 144,566 |
| Last code change | Jun 29, 2026 | Nov 19, 2026 | Apr 20, 2026 | Nov 18, 2026 | Nov 18, 2026 |
| License | Apache-2.0 | MIT | – | Apache-2.0 | MIT |
1 skills (instruction sets) by moshuying that an AI reads and follows · not an MCP server
How a Skill differs from MCP
MCP = the hands
Connects the AI to an outside service or data, such as reading Notion or creating an invoice. A program or server has to be running.
Skill = the manual
A text file that teaches the AI how to do a task. It connects to nothing.
Some overlap: a few Skills run scripts that call tools, and a few MCP servers only send knowledge. Start from the task you want done.
Works with
Claude CodeCodexCursor
From the maker’s README and the folders in the repo
Install
Is it safe?
- Who made it
GitHub account moshuying (person), 8 years old
- Use and upkeep
★ 202 stars, few users so far · code last changed Jun 29, 2026
- Any scripts?
1 scripts that can run on a computer: scripts/install.js
- Uses the internet?
No internet calls found in the scripts
- Changes machine-wide settings?
No hooks or writes to machine settings found
Checked automatically from the repo files at commit e27ca8a (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
First: which AI do you use?
Pick your app and this page shows only how to install it there
Option 1Upload to claude.ai (web and app)
Uploading to claude.ai would fail: the description is over 200 characters (353). Use "Let the AI install it" instead
Option 1Let Claude Code install it
Copy this sentence and paste it into a Claude Code chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Restart Claude Code, then type /pitchcraft or ask for a matching task and Claude picks it up
Checked against official docs Nov 12, 2026 · Source: code.claude.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
The maker’s recommended way
Install Node.js (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
node -v- A version number such as v26.13.1 = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Checking the commands · copy buttons appear once they pass
Copied from the maker’s README; it downloads and runs the maker’s code
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.claude/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
Checking the commands · copy buttons appear once they pass
Restart Claude Code, then type /pitchcraft or ask for a matching task and Claude picks it up
ChatGPT desktop app
The ChatGPT desktop app has Codex built in, and Codex reads skills from ~/.agents/skills
Option 1Let ChatGPT install it
Open Codex in the ChatGPT desktop app and paste this sentence into the chat
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Option 2Put the folder there yourself
Put the pitchcraft folder at ~/.agents/skills/pitchcraft
~ is your home folder ($HOME)
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.agents/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
Checking the commands · copy buttons appear once they pass
After installing
- ChatGPT desktop app: open Skills in the sidebar to see that the skill is there
- To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
- Codex picks up newly installed skills by itself; if one does not show up, restart Codex
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
ChatGPT on the web and mobile
Skills you install yourself do not work here; only skills that come with a plugin from the directory
To use this skill with ChatGPT, use the ChatGPT desktop app as above
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
Option 1Let Codex install it
Copy this sentence and paste it into a Codex chat · Works in Codex inside the ChatGPT desktop app, Codex CLI and the IDE extension
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex picks up newly installed skills by itself; if one does not show up, restart Codex · To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.agents/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
Checking the commands · copy buttons appear once they pass
Restart Codex, then ask for a matching task; Codex lists the skill
Option 1Let Cursor install it
Copy this sentence and paste it into a Cursor chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
In Cursor’s Agent chat, type / and pick pitchcraft
Checked against official docs Nov 12, 2026 · Source: cursor.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.cursor/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
Checking the commands · copy buttons appear once they pass
In Cursor’s Agent chat, type / and pick pitchcraft
Option 1Let the AI install it
For other apps that read skills. The sentence gives the paths for Claude Code, Codex and Cursor so the AI picks the one for your app · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs Nov 12, 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com
For Terminal users
Other apps that support Agent Skills (such as Gemini CLI or GitHub Copilot) use different folders. Check that app’s guide, then copy the folder with the SKILL.md there.
Skill folders checked against the official Claude Code, Codex and Cursor guides on Nov 11, 2026
View the original SKILL.md
The text below comes from the maker’s repo, not from PopNx MCP
Showing the first 8,000 characters · Open the full file on 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 frDiscussion
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
From GitHub
- GitHub stars
- 202
- Maker
- moshuying
- License
- Apache-2.0
- Last code change
- Jun 29, 2026
- SKILL.md files in the repo (including translated copies and templates)
- 2
- Topics
- agent, agent-skills, claude-skill, report, skill