Pitchcraft Persuasive Briefings

What it does

When your agent uses it

• Preparing a project kickoff briefing for leadership
• Writing a status update that argues for continued investment
• Structuring an investor pitch or a solution-selling presentation
• Drafting a wrap-up or annual review with quantified outcomes

Example prompts

• “Help me prepare a kickoff briefing for the payments migration for our CTO and PMO.”
• “Turn my weekly notes into a status update for our VP, with risks and decisions needed.”
• “Structure an investor pitch for our scheduling app using the five-part framework.”
• “Write the annual review for the platform team and check it against the pre-submit list.”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

1. 1Their concerns first, your story second
2. 2Risks need judgment
3. 3Acknowledge peer teams first
4. 4Metrics need source and definition
5. 5Bad news early when it matters
6. 6No homework for the audience

What it can do on your machine

Read from SKILL.md and the folder at commit e27ca8a. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Ships 1 file in scripts/ (JavaScript), which the agent can run.

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Pitchcraft Persuasive Briefings loads about 2.4k tokens when it runs. Until then it costs about 91 tokens; SKILL.md has 537 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~91

When it runs · the whole SKILL.md, loaded when a task matches

~2.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from moshuying/pitchcraft at commit e27ca8a, republished under its Apache-2.0 licence (© moshuying). 537 words, ~2,409 tokens.

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.

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

# {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}

# {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 |
|---|---|---|---|

# {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

# {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}

# {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}

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 from leadership

  Wrap-up / annual:
  □ Original goals
  □ Quantified outcomes
  □ Lessons learned
  □ Next plan or handoff

  Pitch:
  □ Market data and reports
  □ Product demo or MVP status
  □ Competition
  □ Team intro
  □ Financials and forecast
  □ Funding ask and use of funds

  Solution selling:
  □ Customer background and pain
  □ Alternative solutions
  □ Our solution and capabilities
  □ Cases or POC plan
  □ Pricing or engagement model

  If user says "you know everything—just write":
  → Pull from memory and prior context
  → Open with "Based on available info; may be missing XX"

Step 4 — Draft to template
  Pick template; apply writing rules.
  After each part, ask: "Does this answer what they care about?"

Step 5 — Final check
  □ First 10 seconds feel relevant?
  □ Every number sourced and defined?
  □ Every risk has root cause + response?
  □ No vague "needs attention" without judgment?
  □ Cross-team mentions acknowledge others first?

Step 6 — User confirmation
  Present → "What should we adjust?"
  Format issues → add to format memory

© moshuying, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 13 other files (scripts) in the repository root of moshuying/pitchcraft.

• SKILL.md
• .claude-plugin/marketplace.json
• .claude-plugin/plugin.json
• .claude/skills
• .gitignore
• LICENSE
• README.md
• README.zh-CN.md
• commands/pitchcraft.md
• commands/pitchcraft.zh-CN.md
• package.json
• prompts/universal.md
• prompts/universal.zh-CN.md
• scripts/install.js

Open the folder on GitHubat commit e27ca8a

Used in 1 other repository

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in moshuying/pitchcraft, which our catalogue first saw on October 7, 2026.

• aiskillstore/marketplaceskills/moshuying/pitchcraft