add folders in plugins

2026-04-02 09:19:07 +01:00
parent 7ad6ec62fa
commit f9b79a48b9
39 changed files with 2465 additions and 0 deletions
@@ -0,0 +1,78 @@
+---
+name: competitor-teardown
+description: "Produce a structured competitive analysis for any product or market. Use when asked for a competitor analysis, competitive teardown, market comparison, SWOT, or positioning map. Generates a structured teardown with positioning map, feature comparison, messaging gaps, and strategic recommendations."
+---
+
+# Competitor Teardown Skill
+
+This skill produces a complete competitive analysis document — structured for use in strategy decks, investor materials, sales enablement, or product planning sessions.
+
+## Required Inputs
+
+Ask the user for these if not provided:
+- **Your product** (name + one-line description)
+- **Competitors to analyse** (list 2–5 names; if not provided, ask)
+- **Analysis depth** (quick overview / detailed teardown)
+- **Primary use case for this analysis** (e.g. sales enablement, investor deck, internal strategy, product planning)
+
+## Output Structure
+
+### 1. Competitive Landscape Overview
+
+One paragraph summarising the market dynamic: who the key players are, how the market is segmented, and where the white space sits. Keep this under 150 words — it's the exec summary.
+
+### 2. Positioning Map
+
+Describe a 2x2 positioning map in text form (since you can't render images):
+
+- Define the two axes relevant to this market (e.g. "Ease of Use vs. Depth of Features" or "Price vs. Enterprise Readiness")
+- Place each competitor in one quadrant with a one-sentence rationale
+- Place the user's product and highlight the strategic implication
+
+### 3. Feature Comparison Table
+
+| Feature / Capability | [Your Product] | [Competitor A] | [Competitor B] | [Competitor C] |
+|---|---|---|---|---|
+| [Feature] | ✅ / ❌ / 🟡 Partial | | | |
+
+Use ✅ (has it), ❌ (doesn't have it), 🟡 (partial/limited). Add a "Strategic Notes" column for features where the difference is a significant selling point or risk.
+
+Include 10–15 rows. If user hasn't provided feature details, note which cells need to be verified.
+
+### 4. Messaging Analysis
+
+For each competitor, analyse their public-facing messaging (website headline, tagline, primary value prop):
+
+**[Competitor Name]**
+- **Their primary claim:** [what they say they do]
+- **Target audience signal:** [who they seem to be targeting based on language/imagery]
+- **Emotional hook:** [fear / aspiration / authority / speed / simplicity]
+- **Gap or weakness in their messaging:** [what they don't address that your product could own]
+
+### 5. SWOT Summary
+
+Produce a clean SWOT for the user's product in the context of this competitive landscape:
+
+- **Strengths:** [2–3 genuine differentiators]
+- **Weaknesses:** [2–3 honest gaps or vulnerabilities]
+- **Opportunities:** [2–3 market gaps or competitor weaknesses to exploit]
+- **Threats:** [2–3 competitor moves or market shifts to watch]
+
+### 6. Strategic Recommendations
+
+3–5 actionable recommendations based on the analysis. Frame each as: **"Given [observation], [your product] should [action] to [outcome]."**
+
+## Quality Checks
+
+- [ ] Axes on positioning map are meaningful and specific to this market
+- [ ] Feature table includes strategic notes on key differentiators
+- [ ] Messaging analysis covers all named competitors
+- [ ] SWOT is honest — Weaknesses and Threats should not be softened
+- [ ] Recommendations are specific and actionable, not generic strategy advice
+
+## Example Trigger Phrases
+
+- "Do a competitor analysis of [Product] vs [Competitor A] and [Competitor B]"
+- "Tear down [Competitor]'s positioning"
+- "Give me a competitive landscape for [market]"
+- "Build a SWOT for our product against [competitor]"
@@ -0,0 +1,58 @@
+---
+name: content-calendar
+description: "Generate a structured content calendar for any brand, product, or creator. Use when asked for a content plan, editorial calendar, social media schedule, or weekly/monthly content strategy. Produces a calendar with topics, formats, channels, and copy hooks."
+---
+
+# Content Calendar Skill
+
+This skill generates a structured content calendar from brand inputs. It produces ready-to-use calendar entries with topics, formats, channels, and opening hooks — usable for social media, blogs, newsletters, or multi-channel campaigns.
+
+## Required Inputs
+
+Ask the user for these if not provided:
+- **Brand or product name**
+- **Target audience** (who are you trying to reach?)
+- **Primary content goal** (awareness / lead gen / retention / thought leadership)
+- **Channels** (e.g. LinkedIn, Instagram, newsletter, blog, X/Twitter)
+- **Cadence** (daily / 3x per week / weekly / monthly)
+- **Timeframe** (e.g. 4 weeks, Q2)
+- **Brand pillars or themes** (optional — if not provided, derive 3 from the product description)
+
+## Output Structure
+
+### 1. Content Pillars (if not provided)
+
+Derive 3–4 content pillars from the brand/product description. Each pillar = a recurring theme that anchors multiple posts. Label each one clearly (e.g. "Pillar 1: Industry Education", "Pillar 2: Product Stories").
+
+### 2. Calendar Table
+
+Produce a weekly table for each week requested. Format:
+
+| Date | Pillar | Topic | Format | Channel | Opening Hook |
+|---|---|---|---|---|---|
+| Mon 7 Apr | Education | [Topic title] | Carousel / Article / Short video / Thread | LinkedIn | [First sentence or headline of the post] |
+
+Rules:
+- Rotate through all pillars across the week — don't stack the same pillar on consecutive days
+- Match format to channel norms (e.g. carousels for Instagram, long-form for LinkedIn, threads for X)
+- Opening hooks must be specific and scroll-stopping — no generic openers like "Did you know..."
+- Flag 1–2 posts per week as "High Priority" — these are the cornerstone pieces worth boosting or repurposing
+
+### 3. Repurposing Map
+
+For each "High Priority" post, add one repurposing suggestion — e.g. "Turn this LinkedIn article into a newsletter section" or "Clip this video for an Instagram Reel."
+
+## Quality Checks
+
+- [ ] Every week has balanced pillar distribution
+- [ ] No two consecutive posts have the same format on the same channel
+- [ ] Opening hooks are specific (no generic openers)
+- [ ] Formats match platform norms
+- [ ] Repurposing map covers all High Priority posts
+
+## Example Trigger Phrases
+
+- "Build me a 4-week content calendar for [brand]"
+- "Create a social media plan for [product launch]"
+- "Give me a monthly editorial calendar for my newsletter"
+- "Plan my LinkedIn content for the next month"
@@ -0,0 +1,78 @@
+---
+name: email-campaign
+description: "Write and sequence multi-email nurture or launch campaigns. Use when asked for an email sequence, drip campaign, onboarding emails, product launch emails, or nurture flow. Produces subject lines, preview text, full email body, and send-timing recommendations for each email in the sequence."
+---
+
+# Email Campaign Skill
+
+This skill writes complete, sequenced email campaigns — from welcome flows to product launches to re-engagement sequences. Each email is written with subject line, preview text, full body copy, and CTA.
+
+## Required Inputs
+
+Ask the user for these if not provided:
+- **Campaign goal** (onboard new users / launch a product / nurture leads / re-engage churned users / announce a feature)
+- **Audience** (who receives this? job title, lifecycle stage, what they know already)
+- **Product or offer** being promoted or introduced
+- **Number of emails in sequence** (if unsure, recommend based on goal)
+- **Tone** (professional / conversational / bold / educational)
+- **Sender name** (person or brand?)
+
+## Sequence Recommendations by Goal
+
+If the user hasn't specified number of emails, use these defaults:
+- **Onboarding:** 4 emails over 7 days (Day 0, Day 1, Day 3, Day 7)
+- **Product launch:** 3 emails (Teaser → Launch Day → Follow-up/Last chance)
+- **Lead nurture:** 5 emails over 2 weeks
+- **Re-engagement:** 3 emails (Gentle nudge → Value reminder → Final offer)
+- **Feature announcement:** 2 emails (Announcement → How-to/deep dive)
+
+## Output Structure Per Email
+
+For every email in the sequence, produce:
+
+---
+
+**Email [N] of [Total] — [Descriptive label e.g. "Welcome / Day 0"]**
+**Send timing:** [When relative to trigger event or previous email]
+
+**Subject line:** [Primary option]
+**Subject line (A/B variant):** [Alternative to test]
+**Preview text:** [40–90 characters — adds context to the subject, doesn't repeat it]
+
+**Body:**
+
+[Full email copy — formatted with clear opening line, 2–3 body paragraphs, one primary CTA]
+
+**CTA button text:** [3–6 words]
+**CTA destination:** [What page/action this should link to]
+
+**Strategic note:** [Why this email does what it does — the psychological or strategic intent. 1–2 sentences.]
+
+---
+
+## Writing Rules
+
+- Opening line must earn attention — no "Hi, welcome to [product]" openers
+- Each email has ONE primary CTA — never two competing asks
+- Keep paragraphs to 2–3 sentences maximum for mobile readability
+- Use "you" more than "we" — centre the reader, not the brand
+- Subject lines under 50 characters perform best on mobile — flag if going over
+- Preview text should add information the subject doesn't — never just repeat it
+- Every email should stand alone — assume some subscribers miss earlier emails
+
+## Quality Checks
+
+- [ ] Each email has a single clear CTA
+- [ ] Subject lines are under 50 characters (or flagged)
+- [ ] Preview text doesn't repeat the subject line
+- [ ] Opening line is specific and attention-earning
+- [ ] Sequence has logical narrative arc (doesn't feel like disconnected blasts)
+- [ ] Tone is consistent across all emails
+- [ ] Strategic notes explain the intent of each email
+
+## Example Trigger Phrases
+
+- "Write a 3-email launch sequence for [product]"
+- "Build an onboarding email flow for [SaaS tool]"
+- "Create a drip campaign to nurture leads for [offer]"
+- "Write a re-engagement campaign for churned users"
@@ -0,0 +1,98 @@
+---
+name: go-to-market
+description: "Create go-to-market assets for any product or feature. Use when asked for a GTM plan, positioning statement, product launch plan, messaging pillars, use cases, or feature/benefit list. Generates a full GTM pack: positioning statement, messaging pillars, feature-to-benefit mapping, and role-specific use cases."
+---
+
+# Go-To-Market Skill
+
+This skill produces a complete go-to-market asset pack for a product, feature, or initiative. It follows Geoffrey Moore's positioning framework and structures all outputs for use in sales decks, landing pages, launch emails, and internal alignment docs.
+
+## Required Inputs
+
+Ask the user for these if not provided:
+- **Product/feature name**
+- **One-line description** (what it does, technically)
+- **Target customer** (role, company size, industry if relevant)
+- **Primary problem it solves**
+- **Key competitor or alternative** (what people do today without this)
+- **Top 3 differentiators**
+
+## Output Structure
+
+Always produce all four sections below in order.
+
+---
+
+### 1. Positioning Statement
+
+Use the Geoffrey Moore format exactly:
+
+> For **[target customer]** who **[has this problem or need]**, **[Product Name]** is a **[product category]** that **[key benefit/outcome]**. Unlike **[primary alternative or competitor]**, our product **[key differentiator]**.
+
+Write one primary positioning statement, then offer a shorter tagline version (10 words or fewer) suitable for a hero headline.
+
+---
+
+### 2. Messaging Pillars
+
+Generate 3–5 messaging pillars. Each pillar must include:
+
+- **Pillar name** (2–4 words, bold)
+- **One-sentence summary** of what this pillar claims
+- **2–3 proof points** (specific, evidence-backed where possible — if the user hasn't provided data, flag with [ADD PROOF POINT])
+- **Example use in copy** (one sentence as it would appear in a landing page or deck)
+
+Pillars should be distinct — avoid overlap. Each pillar should be defensible against the primary competitor.
+
+---
+
+### 3. Feature & Functionality List
+
+Produce a two-column table:
+
+| Feature / Functionality | Buyer Benefit (what it means for the user) |
+|---|---|
+| [Technical capability] | [Outcome in plain language — start with a verb: "Reduces...", "Enables...", "Eliminates..."] |
+
+Rules:
+- Never list a feature without a corresponding benefit
+- Benefits should reference the target customer's workflow or pain point
+- Aim for 6–12 rows; ask the user for more features if they've only given 1–2
+- Avoid jargon in the benefit column — write as if explaining to a buyer, not an engineer
+
+---
+
+### 4. Use Cases
+
+Generate 3–5 role-specific use cases. Each use case must follow this format:
+
+**Use Case [N]: [Role] — [Scenario Title]**
+
+- **Who:** [Job title / role]
+- **Situation:** [The specific moment or trigger that leads them to use the product]
+- **Before:** [What they had to do without this product — be specific about time, friction, or risk]
+- **With [Product Name]:** [What they do now — concrete action, not vague benefit]
+- **Outcome:** [Measurable or tangible result]
+
+Use cases should cover different buyer personas if possible (e.g. end user, manager, admin).
+
+---
+
+## Quality Checks
+
+Before delivering output, verify:
+- [ ] Positioning statement follows Moore format exactly
+- [ ] Tagline is 10 words or fewer
+- [ ] Each pillar has at least 2 proof points (or flagged placeholders)
+- [ ] Every feature has a benefit — no orphaned features
+- [ ] Benefits start with action verbs
+- [ ] Use cases include a Before/After structure
+- [ ] Language is consistent with the target customer's vocabulary (not internal engineering terms)
+
+## Example Trigger Phrases
+
+- "Create a positioning statement for [product]"
+- "Write a GTM plan for [feature]"
+- "Give me key pillars for [product name]"
+- "Build a feature and use case list for [product]"
+- "We're launching [X] — help me with the messaging"