fix: sync all skill updates and new skills into plugin bundles
- Synced 97 existing skill SKILL.md files from skills/ to their plugin bundle copies - Added 7 new skills to plugin bundles: - seo-content-brief, media-pitch -> pm-gtm - tax-planning-checklist -> pm-finance - change-management-plan -> pm-hr - sales-forecasting-model -> pm-sales - workshop-facilitation-guide -> pm-operations - teaching-lesson-plan -> pm-cross Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -0,0 +1,84 @@
|
||||
---
|
||||
name: media-pitch
|
||||
description: "Write a media pitch or press outreach email for any story or announcement. Use when asked to write a media pitch, journalist outreach email, press pitch, or story angle for PR. Produces a concise pitch with a compelling news angle, journalist-specific hook, and clear call to action."
|
||||
---
|
||||
|
||||
# Media Pitch Skill
|
||||
|
||||
Writes media pitches that journalists actually respond to — built around the story angle, not the company's desire for coverage. Most pitches fail because they are press releases in an email. Good pitches are a human proposing a story to another human.
|
||||
|
||||
## Required Inputs
|
||||
|
||||
Ask the user for these if not provided:
|
||||
- **The story** (what is the actual news or interesting angle?)
|
||||
- **Target publication or journalist** (who are you pitching to and what do they cover?)
|
||||
- **Company or organisation** (who is behind this?)
|
||||
- **Key proof point** (data, customer story, or exclusive that makes this credible)
|
||||
- **Why now** (why is this timely?)
|
||||
- **What you are offering** (interview / exclusive data / embargoed information / spokespeople)
|
||||
|
||||
## Output Structure
|
||||
|
||||
---
|
||||
|
||||
### Pitch: [Target journalist / outlet]
|
||||
|
||||
**Subject line:** [Under 10 words. The story angle, not the company name. Specific, not "Exciting news from [Company]"]
|
||||
|
||||
---
|
||||
|
||||
Hi [First name],
|
||||
|
||||
[Opening sentence — one hook that makes them want to read the next line. Reference their recent work if genuinely relevant: "I read your piece on X last week, which is why I thought you'd be interested in this."]
|
||||
|
||||
[Paragraph 1 — The story in 2–3 sentences. Lead with why the reader of [publication] would care. Not what the company does. The news angle, with the most interesting fact first.]
|
||||
|
||||
[Paragraph 2 — Why this is a story now. One data point, trend, or timely hook. Be specific: "In the last 6 months, X has increased by Y, according to [source]." Generic claims about "growing trends" are ignored.]
|
||||
|
||||
[Paragraph 3 — What you are offering. Interview with [specific person + their relevant credential]. Exclusive data / first look. Access to [specific thing]. One clear offering.]
|
||||
|
||||
[Brief company context — 1 sentence maximum. Journalists don't need your history; they need to know you're credible.]
|
||||
|
||||
Happy to send more details, connect you with [spokesperson], or share [specific exclusive asset] under embargo.
|
||||
|
||||
[Name]
|
||||
[Title, Company]
|
||||
[Mobile — journalists work on deadline and text faster than email]
|
||||
|
||||
---
|
||||
|
||||
## Pitch Rules
|
||||
|
||||
- Subject line is the pitch — if it doesn't earn a click, nothing else matters
|
||||
- The story angle is not "Company launches product" — it is what that product reveals about the world
|
||||
- One pitch, one journalist — mass BCC pitches are recognisable and ignored
|
||||
- Follow up once, after 3–5 business days, with new information (not "just checking in")
|
||||
- If offering an exclusive, name it explicitly and set a response deadline
|
||||
|
||||
## Angle Development Framework
|
||||
|
||||
If the user doesn't have a strong angle, help them find one:
|
||||
|
||||
| Angle type | Example | Works for |
|
||||
|---|---|---|
|
||||
| Data reveal | "Our research of 10,000 users shows X" | Survey findings, product insights |
|
||||
| Trend + proof | "This is happening and here is evidence" | Market trends, behaviour change |
|
||||
| Contrarian | "Everyone thinks X but actually Y" | Counter-intuitive findings |
|
||||
| Human story | "This person's experience illustrates X" | Customer stories, case studies |
|
||||
| Milestone | "First / fastest / largest in [category]" | Launches, records |
|
||||
|
||||
## Quality Checks
|
||||
|
||||
- [ ] Subject line is the story angle (under 10 words, no company name)
|
||||
- [ ] Opening doesn't start with "I'm reaching out" or "I hope this email finds you well"
|
||||
- [ ] The story angle is clear in the first two sentences
|
||||
- [ ] A specific exclusive or offer is named
|
||||
- [ ] Journalist's name is used (not "Hi there")
|
||||
- [ ] Mobile number included for deadline follow-up
|
||||
|
||||
## Example Trigger Phrases
|
||||
|
||||
- "Write a media pitch for [story or announcement]"
|
||||
- "Draft a journalist outreach email for [topic]"
|
||||
- "Help me pitch [story] to [type of journalist or outlet]"
|
||||
- "What is a good angle for a media pitch about [topic]?"
|
||||
@@ -0,0 +1,126 @@
|
||||
---
|
||||
name: seo-content-brief
|
||||
description: "Create a structured SEO content brief for any target keyword or topic. Use when asked to write an SEO brief, content brief, keyword brief, or content strategy document. Produces a complete brief with target keyword, search intent, outline, competitor insights, internal links, and on-page SEO guidance."
|
||||
---
|
||||
|
||||
# SEO Content Brief Skill
|
||||
|
||||
Produces a complete SEO content brief that writers can use to create content that ranks — combining search intent analysis, competitive insights, and on-page optimisation requirements into a single actionable document.
|
||||
|
||||
## Required Inputs
|
||||
|
||||
Ask the user for these if not provided:
|
||||
- **Target keyword or topic**
|
||||
- **Target audience** (who is searching for this?)
|
||||
- **Website or domain** (for internal linking context)
|
||||
- **Content goal** (rank for keyword / drive leads / build authority / support existing content)
|
||||
- **Current ranking or page** (if improving existing content — optional)
|
||||
- **Word count target or preference** (optional — if not provided, derive from search intent)
|
||||
|
||||
## Output Structure
|
||||
|
||||
---
|
||||
|
||||
# SEO Content Brief: [Target Keyword]
|
||||
|
||||
**Target keyword:** [Primary keyword]
|
||||
**Secondary keywords:** [Related terms to include naturally]
|
||||
**Search intent:** [Informational / Navigational / Commercial / Transactional]
|
||||
**Target word count:** [Range — e.g. 1,200–1,800 words]
|
||||
**Content type:** [Blog post / Landing page / Guide / Comparison / Listicle]
|
||||
**Audience:** [Who will read this]
|
||||
**CTA:** [What action should this page drive?]
|
||||
|
||||
---
|
||||
|
||||
## Search Intent Analysis
|
||||
|
||||
**What the searcher wants:** [What someone typing this keyword is actually trying to accomplish]
|
||||
|
||||
**What "good" looks like for this query:**
|
||||
- Format: [How results typically appear — guide, list, comparison table, etc.]
|
||||
- Depth: [Surface-level overview vs. comprehensive deep dive]
|
||||
- Tone: [Expert / Conversational / Technical / Beginner-friendly]
|
||||
|
||||
**User's next question:** [What they'll search for after reading a good answer — use for internal linking]
|
||||
|
||||
---
|
||||
|
||||
## Competitor Content Analysis
|
||||
|
||||
| Ranking page | Word count | Key sections covered | Gaps or weaknesses |
|
||||
|---|---|---|---|
|
||||
| [URL or description] | [~N words] | [Sections] | [What they're missing] |
|
||||
|
||||
**Opportunity to differentiate:** [Specific angle, data, or depth your content can add that competitors lack]
|
||||
|
||||
---
|
||||
|
||||
## Recommended Outline
|
||||
|
||||
Each heading is the exact H2/H3 to use (these are what Google reads):
|
||||
|
||||
**[H1: Title — include primary keyword, under 60 characters]**
|
||||
|
||||
**Introduction** (150–200 words)
|
||||
- Hook with the problem or question
|
||||
- State what the reader will learn
|
||||
- Include primary keyword naturally in first 100 words
|
||||
|
||||
**[H2: First main section]**
|
||||
- [Key points to cover]
|
||||
- [Include secondary keyword: X]
|
||||
|
||||
**[H2: Second main section]**
|
||||
- [Key points]
|
||||
|
||||
**[H2: Third main section]**
|
||||
- [Key points — consider a table or list here for featured snippet opportunity]
|
||||
|
||||
**[H2: FAQ section]** *(recommended for informational queries)*
|
||||
- Q: [Question from "People Also Ask" for this keyword]
|
||||
- Q: [Question 2]
|
||||
|
||||
**Conclusion** (100–150 words)
|
||||
- Summarise key takeaways
|
||||
- Include CTA
|
||||
|
||||
---
|
||||
|
||||
## On-Page SEO Requirements
|
||||
|
||||
| Element | Requirement |
|
||||
|---|---|
|
||||
| Title tag | [60 chars max — primary keyword near start] |
|
||||
| Meta description | [155 chars max — include keyword + benefit] |
|
||||
| H1 | [Match or close to title tag] |
|
||||
| Keyword density | [Use primary keyword 3–5x naturally; don't force it] |
|
||||
| Image alt text | [Describe image + include keyword where natural] |
|
||||
| Internal links | [3–5 internal links — see suggestions below] |
|
||||
| External links | [1–2 authoritative sources to cite] |
|
||||
|
||||
---
|
||||
|
||||
## Internal Linking Suggestions
|
||||
|
||||
| Anchor text | Link to | Why |
|
||||
|---|---|---|
|
||||
| [Relevant phrase] | [/page-path] | [Topic relevance] |
|
||||
|
||||
---
|
||||
|
||||
## Quality Checks
|
||||
|
||||
- [ ] Search intent is correctly identified (informational vs commercial)
|
||||
- [ ] Outline addresses the actual user question (not just the keyword)
|
||||
- [ ] Competitor gaps are specific and actionable
|
||||
- [ ] FAQ section addresses real "People Also Ask" questions
|
||||
- [ ] Title tag is under 60 characters and includes the keyword
|
||||
- [ ] Internal linking suggestions are relevant and specific
|
||||
|
||||
## Example Trigger Phrases
|
||||
|
||||
- "Write an SEO brief for the keyword [keyword]"
|
||||
- "Create a content brief for [topic]"
|
||||
- "What should I include in a blog post about [keyword]?"
|
||||
- "Build a content strategy brief for [topic]"
|
||||
Reference in New Issue
Block a user