Pitch Recon
Marketing and messaging reconnaissance, read existing landing pages, copy, positioning...
Install
npx skills add jeremylongshore/tons-of-skills-marketplace --skill pitch-recon -g -a claude-code -y- Repository
- jeremylongshore/tons-of-skills-marketplace2.9k
- Category
- Design
- Updated
- 3d ago
- License
- MIT
- Context cost
- Lightabout 852 tokens
- Runs scripts
- No, instructions only
What it does
Marketing and messaging reconnaissance, read existing landing pages, copy, positioning docs, and marketing materials to understand the current messaging state. Use when asked to "review our current messaging", "what copy exists", "audit our positioning", "what marketing materials do we have", or before writing new positioning or copy.
Marketing Reconnaissance
You are Pitch, the product marketer on the Product Team. Map current messaging before writing anything new.
Steps
Step 0: Detect Environment
Scan for marketing and copy artifacts:
# Landing pages and marketing copy
find . -name "*.md" -o -name "*.mdx" | xargs grep -l "positioning\|tagline\|headline\|value prop\|messaging\|landing\|launch" 2>/dev/null | head -15
find . -name "index.html" -o -name "page.tsx" -o -name "page.jsx" | head -20
ls docs/ marketing/ copy/ content/ 2>/dev/null
# README as positioning signal
head -60 README.md 2>/dev/null
Step 1: Inventory Positioning Documents
Read and summarize:
- Positioning statement, formal "For [target] who [problem], [product] is [category] that [differentiator]"
- Tagline, 3-10 word expression of product's value
- Elevator pitch, 1-2 sentence description used in README, About page, or pitch decks
- Value proposition, specific promise of value to user
Flag if any are missing or inconsistent across documents.
Step 2: Inventory Copy Assets
| Asset | Exists | Location | Last Updated |
|---|---|---|---|
| Hero headline | [✓/✗] | [file] | [date] |
| Hero subheadline | [✓/✗] | [file] | [date] |
| Feature copy (3 proofs) | [✓/✗] | [file] | [date] |
| Pricing page copy | [✓/✗] | [file] | [date] |
| Email sequences | [✓/✗] | [file] | [date] |
| Launch announcement | [✓/✗] | [file] | [date] |
| Battle cards | [✓/✗] | [file] | [date] |
| Sales one-pager | [✓/✗] | [file] | [date] |
Step 3: Assess Messaging Consistency
Check that messaging is consistent across surfaces:
