media-relations▌
refoundai/lenny-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Help users pitch journalists and build lasting media relationships using proven outreach strategies.
- ›Follow a three-step framework: prepare your story and assets, identify reporters who cover your space, then pitch with exclusives one outlet at a time
- ›Avoid mass pitching and generic angles; frame stories around reader interests and trends, not your company's announcement
- ›Build relationships before you need coverage by engaging with journalists' work and becoming a trusted source over
Media Relations
Help the user build effective relationships with journalists and secure press coverage using insights from 2 product leaders.
How to Help
When the user asks for help with media relations:
- Understand their goal - Ask what kind of coverage they're seeking (launch announcement, thought leadership, feature story) and what stage they're at
- Prepare the story - Help them craft a compelling angle that's newsworthy, not just promotional
- Identify the right targets - Guide them on finding the right reporters and publications for their story
- Execute the pitch - Help them write effective pitches and manage the outreach process
Core Principles
Offer exclusives, pitched one at a time
Emilie Gerber: "I stagger it because we're offering exclusives, and I highly recommend offering exclusives." Don't blast your story to every reporter simultaneously. Offer an exclusive to your top target, wait for their response, then move to the next.
Follow the prep-target-pitch framework
Jason Feifer: "Step one is prep... Step two is figuring out who to pitch... Step three is the actual pitch." Preparation means having your story, angles, and assets ready. Targeting means finding reporters who actually cover your space. Pitching means concise, relevant outreach.
Build relationships before you need them
The best media relationships are built over time, not when you need coverage. Engage with journalists' work, provide helpful information even when you don't have news, and become a trusted source.
Think about what's interesting to readers, not you
Reporters care about their readers, not your company. Frame your story around trends, problems, or insights that their audience cares about. Your product is the supporting detail, not the headline.
Questions to Help Users
- "What's the angle that makes this newsworthy beyond just being your announcement?"
- "Who are the specific reporters who cover companies like yours? Have you read their recent work?"
- "Do you have assets ready - images, quotes, data - that make the reporter's job easier?"
- "Are you offering this as an exclusive? Who's your top target outlet?"
- "What's your timeline? Do you have flexibility to work with the reporter's schedule?"
Common Mistakes to Flag
- Mass pitching - Sending the same pitch to dozens of reporters signals you don't understand how press works. Pitch one at a time with exclusives
- Leading with the company, not the story - Reporters don't care about your funding or launch. They care about what's interesting to their readers
- Rigid timelines - Prioritize getting the right coverage over hitting an arbitrary date. Be flexible with reporter schedules
- No preparation - Having to scramble for images, quotes, or details after a reporter expresses interest signals you're not ready
Deep Dive
For all 2 insights from 2 guests, see references/guest-insights.md
Related Skills
- Launch Marketing
- Positioning & Messaging
- Brand Storytelling
- Content Marketing
How to use media-relations on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add media-relations
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches media-relations from GitHub repository refoundai/lenny-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate media-relations. Access the skill through slash commands (e.g., /media-relations) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★47 reviews- ★★★★★Isabella Perez· Dec 20, 2024
We added media-relations from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★James Jain· Dec 16, 2024
Keeps context tight: media-relations is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Chaitanya Patil· Dec 8, 2024
Useful defaults in media-relations — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Dev Desai· Dec 4, 2024
media-relations is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Piyush G· Nov 27, 2024
media-relations has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Isabella Tandon· Nov 23, 2024
media-relations fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Lucas Shah· Nov 19, 2024
Registry listing for media-relations matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Amina Park· Nov 11, 2024
Keeps context tight: media-relations is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Amina Taylor· Nov 7, 2024
We added media-relations from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Anika Perez· Oct 26, 2024
media-relations fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 47