pitchcraft skill
A skill for briefings to leadership and investors: builds the text on a five-part scheme and checks it against a checklist before you send it
- 201 ★ on the repository
- Last commit
- Apache-2.0
Minimal access
Why this level
- The skill consists of instructions and templates: it runs no code and makes no network calls on its own
- The draft is built from your materials, so give the agent confidential figures only in a trusted environment
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/pitchcraftDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- The skill consists of instructions and templates: it runs no code and makes no network calls on its own
- The draft is built from your materials, so give the agent confidential figures only in a trusted environment
This is third-party code. Review the repository files before installing.
What it does
pitchcraft guides work on a briefing that has to persuade. The skill distinguishes five scenarios: project kickoff, status update, wrap-up, investor pitch and solution selling. For each it builds the text on one five-part scheme: hook, context, proposal, evidence and ask. Before drafting, the agent checks what the materials lack and asks who will listen, what those people already know and what matters to them. Then it writes from the scenario template. A status update, for example, opens with a one-line summary, then progress, problems and the decisions needed from leadership. Each problem comes with options and a recommendation, so no open question goes to leadership. The finished text goes through a checklist: figures need a source and problems need an assessment. The skill starts on phrases such as status update, project kickoff, wrap-up, pitch and solution selling, and Chinese trigger phrases are listed too. If leader context, business positioning and format preferences are configured, the skill takes them into account.
Who it is for. Tech leads, product managers and founders who report to leadership: kicking off, reporting, closing a phase or raising money.
Good fit when
- You have to defend a project kickoff before a director and need a briefing that runs from the problem to a request for people and budget
- The weekly status has become a list of done items while leadership wants a one-line summary and decisions
- You are wrapping up the year and the results must be expressed in sourced figures
- You are preparing a pitch for investors or partners with a market, a moat and an ask
- Before sending, you want to check the briefing: every problem has an assessment and every figure a source
Not a fit when
- You only need a log of completed work with no aim to persuade: the five-part scheme is too heavy for that
- You need finished slides as a file: the skill writes the text of the briefing and does not draw the deck
- The talk is on another subject, such as a technical deep dive for developers: the scenarios target executives, investors and customers
Example request
Prepare a status update for the director from my notes: a one-line summary, problems with options, and what I need from themLimitations
- The skill structures the briefing; figures and facts come from your materials. If data is missing, the agent asks for it and does not invent it.
- The Claude Code plugin installs the English `SKILL.md`. For Chinese, copy `SKILL.zh-CN.md` over `SKILL.md` by hand.
- Cursor, Codex and web chats get no skill: paste the `prompts/universal.md` file into the prompt or rules instead.
- Memory about the leader and format works only when you have configured it.
How to disable. Delete the `~/.claude/skills/pitchcraft/` folder or run `/plugin uninstall pitchcraft` in Claude Code. In Cursor and Codex remove the pasted `prompts/universal.md` from the rules.
FAQ
What parts make up a briefing in the pitchcraft scheme?
Five: hook, context, proposal, evidence and ask. The emphasis shifts: a kickoff hooks with a pain or opportunity, a status update with the headline of the period, a pitch with market size.
How is pitchcraft different from an ordinary AI weekly report generator?
Ordinary generators fill blanks in a work log. pitchcraft first finds the gaps in the materials and who is listening, then builds the text around the decision you need.
How do I connect pitchcraft to Claude Code?
Run `/plugin marketplace add moshuying/pitchcraft`, then `/plugin install pitchcraft` and restart Claude Code. The skill starts on phrases such as status update or project kickoff.
How do I use pitchcraft in Cursor or Codex?
Paste `prompts/universal.md` into Cursor's rules or into Codex CLI system instructions. A Chinese version sits next to it as `universal.zh-CN.md`.
What license does pitchcraft use?
Apache License 2.0. The license text is in the repository's LICENSE file.
Discussion
No questions or reviews yet.
Related
SkillsA skill that cross-examines a plan before work starts: numbered questions in rounds with a recommended answer and no changes until you confirm
A set of 13 SKILL.md skills: research, a product doc, decks, articles and audits for any compatible agent
Skills that turn a coding agent's output into plain language: honest reports, straight verdicts, followable steps
A large library of product frameworks as skills: discovery, strategy, PRDs, prioritization and unit economics
A skill that turns an agent into an MBB-grade strategy consultant: problem structuring, frameworks, market sizing, case work
An analytical skill that tests whether users will find value in a product idea: scenario, conditions, timing and delivery, with solidity ratings
README in short
The README explains why a briefing must persuade and compares pitchcraft with ordinary AI reports by scenarios, goal and the role of AI. It then covers the five-part scheme, a scenario table, installation routes, trigger phrases, the work steps and a table of English and Chinese files.
README badge
Original SKILL.md
--- 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