pitch-vs-teach
Know which talk you're giving — the pitch (drive one decision) vs. the teach (build understanding) — because mixing their structures fails both, and most bad presentations are one wearing the other's clothes. Use when asked is this a pitch or a training, my informative deck didn't land the ask, my pitch felt like a lecture, or structure this talk for the right job. Produces the mode diagnosis, the structural implications, the mixed-mandate split, and the mode-check on an existing deck.
npx skills add mohitagw15856/pm-claude-skills --skill pitch-vs-teach --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Pitch Vs Teach Skill Two fundamentally different talks share the same slideware: the **pitch** exists to drive one decision (structure: tension → answer → evidence → ask; success: the yes) and the **teach** exists to build durable understanding (structure: foundation → layers → examples → practice; success: they can use it Tuesday). Most presentation failures are mode confusion — the pitch built like a lecture (comprehensive, balanced, ask-less: the room learned a lot and decided nothing) or the training built like a pitch (persuasive, thin, one-sided: the room was convinced but can't operate it). The diagnosis takes one question; the structures then diverge completely. ## What This Skill Produces - **The mode diagnosis** — pitch, teach, or genuinely-both (which means two segments, not a blend), from the success-question - **The structural implications** — what the diagnosed mode demands: sequence, density, evidence style, the ending - **The mode-check** — an existing deck audited for mode confusion, with the tells cited - **The split design** — for mixed mandates: the teach-then-pitch sequence with the seam handled ## Required Inputs Ask for these if not provided: - **The succes
- What This Skill Produces
- Required Inputs
- Framework: The Mode Rules
- Output Format
- The Success Question
- Structural Implications
- Mode-Check (existing deck)
- The Split (if both)
- Quality Checks
- Anti-Patterns
What does the pitch-vs-teach skill do?
Know which talk you're giving — the pitch (drive one decision) vs. the teach (build understanding) — because mixing their structures fails both, and most bad presentations are one wearing the other's clothes. Use when asked is this a pitch or a training, my informative deck didn't land the ask, my pitch felt like a lecture, or structure this talk for the right job. Produces the mode diagnosis, the structural implications, the mixed-mandate split, and the mode-check on an existing deck.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill pitch-vs-teach --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.