Merge remote-tracking branch 'origin/main' into development

.claude-plugin/marketplace.json

@@ -12,12 +12,13 @@
   "plugins": [
     {
       "name": "marketing-skills",
-      "description": "25 marketing skills for technical marketers and founders: CRO, copywriting, SEO, paid ads, pricing strategy, referral programs, and more",
+      "description": "26 marketing skills for technical marketers and founders: CRO, copywriting, cold email, SEO, paid ads, pricing strategy, referral programs, and more",
       "source": "./",
       "strict": false,
       "skills": [
         "./skills/ab-test-setup",
         "./skills/analytics-tracking",
+        "./skills/cold-email",
         "./skills/competitor-alternatives",
         "./skills/content-strategy",
         "./skills/copy-editing",

README.md

@@ -19,6 +19,7 @@ Skills are markdown files that give AI agents specialized knowledge and workflow
 |-------|-------------|
 | [ab-test-setup](skills/ab-test-setup/) | When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B... |
 | [analytics-tracking](skills/analytics-tracking/) | When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions... |
+| [cold-email](skills/cold-email/) | Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails,... |
 | [competitor-alternatives](skills/competitor-alternatives/) | When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when... |
 | [content-strategy](skills/content-strategy/) | When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also... |
 | [copy-editing](skills/copy-editing/) | When the user wants to edit, review, or improve existing marketing copy. Also use when the user mentions 'edit this... |
@@ -154,6 +155,7 @@ You can also invoke skills directly:
 ### Content & Copy
 - `copywriting` - Marketing page copy
 - `copy-editing` - Edit and polish existing copy
+- `cold-email` - B2B cold outreach emails and sequences
 - `email-sequence` - Automated email flows
 - `social-content` - Social media content
 

VERSIONS.md

@@ -6,6 +6,7 @@ Current versions of all skills. Agents can compare against local versions to che
 |-------|---------|--------------|
 | ab-test-setup | 1.0.0 | 2026-01-27 |
 | analytics-tracking | 1.0.0 | 2026-01-27 |
+| cold-email | 1.0.0 | 2026-02-14 |
 | competitor-alternatives | 1.0.0 | 2026-01-27 |
 | content-strategy | 1.0.0 | 2026-01-27 |
 | copy-editing | 1.0.0 | 2026-01-27 |

skills/ab-test-setup/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: ab-test-setup
-version: 1.0.0
 description: When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," or "hypothesis." For tracking implementation, see analytics-tracking.
+metadata:
+  version: 1.0.0
 ---
 
 # A/B Test Setup

skills/ab-test-setup/references/sample-size-guide.md

@@ -2,6 +2,17 @@
 
 Reference for calculating sample sizes and test duration.
 
+## Contents
+- Sample Size Fundamentals (required inputs, what these mean)
+- Sample Size Quick Reference Tables
+- Duration Calculator (formula, examples, minimum duration rules, maximum duration guidelines)
+- Online Calculators
+- Adjusting for Multiple Variants
+- Common Sample Size Mistakes
+- When Sample Size Requirements Are Too High
+- Sequential Testing
+- Quick Decision Framework
+
 ## Sample Size Fundamentals
 
 ### Required Inputs

skills/ab-test-setup/references/test-templates.md

@@ -2,6 +2,15 @@
 
 Templates for planning, documenting, and analyzing experiments.
 
+## Contents
+- Test Plan Template
+- Results Documentation Template
+- Test Repository Entry Template
+- Quick Test Brief Template
+- Stakeholder Update Template
+- Experiment Prioritization Scorecard
+- Hypothesis Bank Template
+
 ## Test Plan Template
 
 ```markdown

skills/analytics-tracking/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: analytics-tracking
-version: 1.0.0
 description: When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," or "tracking plan." For A/B test measurement, see ab-test-setup.
+metadata:
+  version: 1.0.0
 ---
 
 # Analytics Tracking

skills/analytics-tracking/references/event-library.md

@@ -2,6 +2,15 @@
 
 Comprehensive list of events to track by business type and context.
 
+## Contents
+- Marketing Site Events (navigation & engagement, CTA & form interactions, conversion events)
+- Product/App Events (onboarding, core usage, errors & support)
+- Monetization Events (pricing & checkout, subscription management)
+- E-commerce Events (browsing, cart, checkout, post-purchase)
+- B2B / SaaS Specific Events (team & collaboration, integration events, account events)
+- Event Properties (Parameters)
+- Funnel Event Sequences
+
 ## Marketing Site Events
 
 ### Navigation & Engagement

skills/analytics-tracking/references/ga4-implementation.md

@@ -2,6 +2,16 @@
 
 Detailed implementation guide for Google Analytics 4.
 
+## Contents
+- Configuration (data streams, enhanced measurement events, recommended events)
+- Custom Events (gtag.js implementation, Google Tag Manager)
+- Conversions Setup (creating conversions, conversion values)
+- Custom Dimensions and Metrics (when to use, setup steps, examples)
+- Audiences (creating audiences, audience examples)
+- Debugging (DebugView, real-time reports, common issues)
+- Data Quality (filters, cross-domain tracking, session settings)
+- Integration with Google Ads (linking, audience export)
+
 ## Configuration
 
 ### Data Streams

skills/analytics-tracking/references/gtm-implementation.md

@@ -2,6 +2,16 @@
 
 Detailed guide for implementing tracking via Google Tag Manager.
 
+## Contents
+- Container Structure (tags, triggers, variables)
+- Naming Conventions
+- Data Layer Patterns
+- Common Tag Configurations (GA4 configuration tag, GA4 event tag, Facebook pixel)
+- Preview and Debug
+- Workspaces and Versioning
+- Consent Management
+- Advanced Patterns (tag sequencing, exception handling, custom JavaScript variables)
+
 ## Container Structure
 
 ### Tags

skills/cold-email/SKILL.md

@@ -0,0 +1,155 @@
+---
+name: cold-email
+description: Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Covers subject lines, opening lines, body copy, CTAs, personalization, and multi-touch follow-up sequences.
+---
+
+# Cold Email Writing
+
+You are an expert cold email writer. Your goal is to write emails that sound like they came from a sharp, thoughtful human — not a sales machine following a template.
+
+## Before Writing
+
+**Check for product marketing context first:**
+If `.claude/product-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
+
+Understand the situation (ask if not provided):
+
+1. **Who are you writing to?** — Role, company, why them specifically
+2. **What do you want?** — The outcome (meeting, reply, intro, demo)
+3. **What's the value?** — The specific problem you solve for people like them
+4. **What's your proof?** — A result, case study, or credibility signal
+5. **Any research signals?** — Funding, hiring, LinkedIn posts, company news, tech stack changes
+
+Work with whatever the user gives you. If they have a strong signal and a clear value prop, that's enough to write. Don't block on missing inputs — use what you have and note what would make it stronger.
+
+---
+
+## Writing Principles
+
+### Write like a peer, not a vendor
+
+The email should read like it came from someone who understands their world — not someone trying to sell them something. Use contractions. Read it aloud. If it sounds like marketing copy, rewrite it.
+
+### Every sentence must earn its place
+
+Cold email is ruthlessly short. If a sentence doesn't move the reader toward replying, cut it. The best cold emails feel like they could have been shorter, not longer.
+
+### Personalization must connect to the problem
+
+If you remove the personalized opening and the email still makes sense, the personalization isn't working. The observation should naturally lead into why you're reaching out.
+
+See [personalization.md](references/personalization.md) for the 4-level system and research signals.
+
+### Lead with their world, not yours
+
+The reader should see their own situation reflected back. "You/your" should dominate over "I/we." Don't open with who you are or what your company does.
+
+### One ask, low friction
+
+Interest-based CTAs ("Worth exploring?" / "Would this be useful?") beat meeting requests. One CTA per email. Make it easy to say yes with a one-line reply.
+
+---
+
+## Voice & Tone
+
+**The target voice:** A smart colleague who noticed something relevant and is sharing it. Conversational but not sloppy. Confident but not pushy.
+
+**Calibrate to the audience:**
+
+- C-suite: ultra-brief, peer-level, understated
+- Mid-level: more specific value, slightly more detail
+- Technical: precise, no fluff, respect their intelligence
+
+**What it should NOT sound like:**
+
+- A template with fields swapped in
+- A pitch deck compressed into paragraph form
+- A LinkedIn DM from someone you've never met
+- An AI-generated email (avoid the telltale patterns: "I hope this email finds you well," "I came across your profile," "leverage," "synergy," "best-in-class")
+
+---
+
+## Structure
+
+There's no single right structure. Choose a framework that fits the situation, or write freeform if the email flows naturally without one.
+
+**Common shapes that work:**
+
+- **Observation → Problem → Proof → Ask** — You noticed X, which usually means Y challenge. We helped Z with that. Interested?
+- **Question → Value → Ask** — Struggling with X? We do Y. Company Z saw [result]. Worth a look?
+- **Trigger → Insight → Ask** — Congrats on X. That usually creates Y challenge. We've helped similar companies with that. Curious?
+- **Story → Bridge → Ask** — [Similar company] had [problem]. They [solved it this way]. Relevant to you?
+
+For the full catalog of frameworks with examples, see [frameworks.md](references/frameworks.md).
+
+---
+
+## Subject Lines
+
+Short, boring, internal-looking. The subject line's only job is to get the email opened — not to sell.
+
+- 2-4 words, lowercase, no punctuation tricks
+- Should look like it came from a colleague ("reply rates," "hiring ops," "Q2 forecast")
+- No product pitches, no urgency, no emojis, no prospect's first name
+
+See [subject-lines.md](references/subject-lines.md) for the full data.
+
+---
+
+## Follow-Up Sequences
+
+Each follow-up must add something new — a different angle, fresh proof, a useful resource. Never "just checking in."
+
+- 3-5 total emails, increasing gaps between them
+- Each email should stand alone (they may not have read the previous ones)
+- The breakup email is your last touch — honor it
+
+See [follow-up-sequences.md](references/follow-up-sequences.md) for cadence, angle rotation, and breakup email templates.
+
+---
+
+## Quality Check
+
+Before presenting, gut-check:
+
+- Does it sound like a human wrote it? (Read it aloud)
+- Would YOU reply to this if you received it?
+- Does every sentence serve the reader, not the sender?
+- Is the personalization connected to the problem?
+- Is there one clear, low-friction ask?
+
+---
+
+## What to Avoid
+
+- Opening with "I hope this email finds you well" or "My name is X and I work at Y"
+- Jargon: "synergy," "leverage," "circle back," "best-in-class," "leading provider"
+- Feature dumps — one proof point beats ten features
+- HTML, images, or multiple links
+- Fake "Re:" or "Fwd:" subject lines
+- Identical templates with only {{FirstName}} swapped
+- Asking for 30-minute calls in first touch
+- "Just checking in" follow-ups
+
+---
+
+## Data & Benchmarks
+
+The references contain performance data if you need to make informed choices:
+
+- [benchmarks.md](references/benchmarks.md) — Reply rates, conversion funnels, expert methods, common mistakes
+- [personalization.md](references/personalization.md) — 4-level personalization system, research signals
+- [subject-lines.md](references/subject-lines.md) — Subject line data and optimization
+- [follow-up-sequences.md](references/follow-up-sequences.md) — Cadence, angles, breakup emails
+- [frameworks.md](references/frameworks.md) — All copywriting frameworks with examples
+
+Use this data to inform your writing — not as a checklist to satisfy.
+
+---
+
+## Related Skills
+
+- **copywriting**: For landing pages and web copy
+- **email-sequence**: For lifecycle/nurture email sequences (not cold outreach)
+- **social-content**: For LinkedIn and social posts
+- **product-marketing-context**: For establishing foundational positioning

skills/cold-email/references/benchmarks.md

@@ -0,0 +1,83 @@
+# Benchmarks, Data & Expert Methods
+
+## Core Performance Metrics (2024–2025)
+
+| Metric                     | Average | Good   | Excellent | Source                   |
+| -------------------------- | ------- | ------ | --------- | ------------------------ |
+| Open rate                  | 27.7%   | 40–45% | 50%+      | Belkins, Snov.io         |
+| Reply rate                 | 4–5.8%  | 5–10%  | 10–15%    | Belkins, Reachoutly      |
+| Reply rate (best-in-class) | —       | —      | 15–25%+   | Digital Bloom, Instantly |
+| Positive reply %           | ~48%    | 55–60% | 62–65%    | Digital Bloom            |
+| Meeting booking rate       | 0.5–1%  | 1–2%   | 2.3%+     | Reachoutly               |
+| Bounce rate                | 7.5%    | <4%    | <2%       | Belkins                  |
+
+## Realistic Funnel Model
+
+500 emails → 100 opens (20%) → 25 replies (5%) → 8 positive replies (30%) → 4 meetings (50%) → 1 client (25% close). ~**0.2% end-to-end conversion** for average performers.
+
+## Performance Levers (ranked by impact)
+
+1. **Hook type** — Timeline hooks outperform problem hooks by 3.4x in meetings
+2. **Personalization depth** — Up to 250% more replies
+3. **Brevity** — 25–75 words optimal, 83% more replies under 75 words
+4. **Targeting precision** — ≤50 contacts per campaign = 2.76x higher reply rates
+5. **Follow-up strategy** — First follow-up adds 49% more replies
+6. **Reading level** — 3rd–5th grade = 67% more replies
+7. **Send timing** — Thursday peaks at 6.87% reply rate
+
+## Declining Effectiveness Trend
+
+Reply rates dropped from 7–8% (2020–2022) to 4–5.8% (2024–2025), ~15% YoY decline. Drivers: inbox saturation (10+ cold emails/week, 20% say none relevant), stricter anti-spam (Google's threshold: 0.1% complaints), AI email flood (more volume, less quality signal). Writing craft matters more, not less — gap between average and excellent is widening.
+
+## Response Rates by Seniority
+
+- **Entry-level:** Highest engagement at 8% reply, 50% open
+- **C-level:** 23% more likely to respond than non-C-suite when they engage (6.4% vs 5.2%)
+- **CTOs/VP Tech:** 7.68% reply
+- **CEOs/Founders:** 7.63% reply
+- **Heads of Sales:** 6.60% (most targeted role, highest saturation)
+
+## Industry Variation
+
+**Highest responding:** Nonprofits (16.5%+), legal (10%), EdTech (7.8%), chemical (7.3%), manufacturing (6.1%).
+**Lowest responding:** SaaS (3.5%), financial services (3.4%), IT services (3.5%).
+
+## Top 15 Mistakes (ranked by impact)
+
+1. **Too long** — 70% of emails above 10th-grade level. Under 75 words = 83% more replies
+2. **Too self-focused** — "We are a leading..." signals sales pitch. Count I/We sentences
+3. **No clear value prop** — 71% of decision-makers ignore irrelevant emails
+4. **Generic templates** — {{FirstName}} isn't personalization. Recipients detect instantly
+5. **Feature dumping** — "Great reps lead with problems" (Lavender). One proof point beats ten features
+6. **False personalization** — "Loved your post!" without specifics is transparent
+7. **Asking too much too soon** — 30-min call in first email = "proposing on first date"
+8. **Pushy language** — "Act Now" stacking increases spam flagging by 67%
+9. **No CTA** — Without a clear next step, momentum dies
+10. **"Just checking in" follow-ups** — "I never heard back" = 12% drop in bookings
+11. **Wrong tone for audience** — Founder ≠ RevOps lead ≠ sales leader
+12. **Jargon/buzzwords** — "Leverage synergistic platform" → "We help you book more meetings"
+13. **Unsubstantiated claims** — "300% more leads" without proof triggers skepticism
+14. **Too many contacts per company** — 1–2 people = 7.8% reply; 10+ = 3.8%
+15. **Fake urgency** — Fake "Re:" / "Fwd:" / countdown timers destroy trust
+
+## Cultural Calibration
+
+| Factor       | US              | UK                       | Germany/DACH         | Scandinavia             |
+| ------------ | --------------- | ------------------------ | -------------------- | ----------------------- |
+| Tone         | Direct, casual  | Polite, professional     | Precise, data-driven | Fact-based, egalitarian |
+| Length       | Shorter, blunt  | Longer, insight-led      | Detail-oriented      | Concise but substantive |
+| Social proof | Outcome numbers | Research-led credibility | Technical precision  | Shared values           |
+
+North America: 4.1% response. Europe: 3.1%. Asia-Pacific: 2.8%. Shorter, more direct sequences work better in US. UK needs more insight/personality. GDPR affects European tone.
+
+## Expert Quick Reference
+
+| Expert         | Core Method                                                     | Best For                                        |
+| -------------- | --------------------------------------------------------------- | ----------------------------------------------- |
+| Alex Berman    | 3C's: Compliment → Case Study → CTA                             | High-ticket B2B services, agencies              |
+| Josh Braun     | "Poke the Bear" — neutral questions exposing invisible problems | Empathy-driven consultative selling             |
+| Kyle Coleman   | Systematic research + AI personalization at scale               | Bridging mass outreach and deep personalization |
+| Becc Holland   | Psychographic personalization, Premise Buckets                  | Combining personalization with relevance        |
+| Will Allred    | Data-driven coaching, Mouse Trap, Vanilla Ice Cream             | Any context; universal frameworks               |
+| Justin Michael | 1–3 sentence hyper-brevity, quote their own words               | High-velocity SDR teams at scale                |
+| Sam Nelson     | Agoge Sequence — Triple on Day 1 (email + LinkedIn + call)      | Multi-channel, tiered personalization           |

skills/cold-email/references/follow-up-sequences.md

@@ -0,0 +1,81 @@
+# Follow-Up Sequences
+
+55% of replies come from follow-ups, not the initial email. Yet 48% of salespeople never follow up even once.
+
+## How Many: 3–5 Total Emails
+
+- Highest single-email reply rate: **8.4%** (Belkins).
+- 4–7 email campaigns achieve **27% reply rates** vs 9% for 1–3 emails (Woodpecker, 20M emails).
+- By 4th follow-up, response rates drop **55%** and spam complaints **triple**.
+- Resolution: longer sequences catch different timing windows. Cap at 4 follow-ups (5 total emails). Each must add genuinely new value.
+
+## Optimal Cadence
+
+Increase the gap between each touch:
+
+| Touch         | Day   | Notes                                          |
+| ------------- | ----- | ---------------------------------------------- |
+| Initial email | 0     | Maximum personalization investment             |
+| Follow-up 1   | 3     | Waiting 3 days increases response by up to 31% |
+| Follow-up 2   | 7–8   | Different angle                                |
+| Follow-up 3   | 14    | New value piece                                |
+| Follow-up 4   | 21–28 | Breakup email                                  |
+
+**Best days:** Tuesday–Thursday (Thursday peaks at 6.87% reply rate).
+**Best times:** 9–11 AM or 1–3 PM in prospect's local time.
+**Avoid:** Monday mornings (inbox overload), Friday afternoons (checked out).
+
+## Angle Rotation
+
+Each follow-up must stand alone while building toward the goal. Never just "bump this up."
+
+| Email       | Angle                                                      | Purpose                    |
+| ----------- | ---------------------------------------------------------- | -------------------------- |
+| Initial     | Personalized hook + core value prop + soft CTA             | Introduce problem/solution |
+| Follow-up 1 | Different angle, new value piece (stat, insight, resource) | Show additional benefit    |
+| Follow-up 2 | Social proof / case study from similar company             | Build credibility          |
+| Follow-up 3 | New insight, industry trend, or relevant resource          | Demonstrate expertise      |
+| Follow-up 4 | Breakup — acknowledge silence, leave door open             | Trigger loss aversion      |
+
+Add only **one new value proposition per email** (SalesBread). This naturally forces different angles.
+
+## The Breakup Email
+
+Leverages loss aversion — removing pressure while creating scarcity through withdrawal. Close.com reports **10–15% response rates** from breakup emails with cold prospects.
+
+**Structure:**
+
+1. Acknowledge you've reached out multiple times
+2. Validate their potential lack of interest
+3. State this is your final email for now
+4. Leave the door open
+
+**Example:**
+
+> I haven't heard back, so I'll assume now isn't the right time. Before I close the loop: [1-sentence insight or resource]. If that changes things, feel free to reply. Otherwise, no hard feelings — good luck with [their goal].
+
+**1-2-3 Format** (reduces friction to near zero):
+
+> Since I haven't heard back, I'll keep it simple. Reply with a number:
+>
+> 1 — Interested, let's talk
+> 2 — Not now, check back in 3 months
+> 3 — Not interested, please stop
+
+**Critical rule:** If you send a breakup email, honor it. Do not contact the prospect again.
+
+## Phrases That Kill Response Rates
+
+- "I never heard back" → **12% drop** in meeting booking rate (Gong)
+- "Just checking in" → Zero value, signals laziness
+- "Bumping this to the top of your inbox" → Presumptuous
+- "Did you see my last email?" → Guilt-tripping
+- "Following up on my previous message" → Generic, adds nothing
+
+## CTA Adjustment by Seniority
+
+**Executives/founders:** Ultra-low-effort, curiosity-driven. "Curious?" or "Worth 2 min?"
+
+**Mid-level managers:** More specific value. "Want me to walk through how [Company] saved 15 hours/week?"
+
+Higher in the org chart = less friction you can ask for.

skills/cold-email/references/frameworks.md

@@ -0,0 +1,90 @@
+# Cold Email Copywriting Frameworks
+
+Frameworks beat templates — they teach thinking patterns, not copy-paste shortcuts.
+
+## PAS — Problem, Agitate, Solution (default)
+
+**Structure:** Identify pain → Amplify consequences → Present solution + soft CTA.
+**Best for:** Problem-aware but not solution-aware prospects. The workhorse framework.
+
+> Most VP Sales at companies your size spend 5+ hours/week on manual CRM reporting. That's 250+ hours/year not spent coaching reps — and often means inaccurate forecasts reaching leadership. We built a tool that auto-generates CRM reports in real time. Teams like Datadog reduced reporting time by 80%. Would it make sense to see how?
+
+## BAB — Before, After, Bridge
+
+**Structure:** Current painful situation → Ideal future → Your product as the bridge.
+**Best for:** Transformation-driven offers with clear before/after. Emotional decision-makers.
+
+> Right now, your team is likely spending hours manually sourcing leads — feast or famine each quarter. Imagine qualified leads arriving daily on autopilot, reps spending 100% of their time selling. That's what our platform does. Companies like HubSpot saw a 40% pipeline increase within 90 days. Can I show you how?
+
+## QVC — Question, Value, CTA
+
+**Structure:** Targeted pain question → Brief value → Direct next step.
+**Best for:** C-suite prospects who prefer brevity. Qualify interest immediately.
+
+> Are your SDRs spending more time researching than selling? We help sales teams automate prospect research so reps focus on conversations. Clients see 3x more meetings per rep per week. Worth a 10-minute demo?
+
+## AIDA — Attention, Interest, Desire, Action
+
+**Structure:** Hook/stat → Address specific challenge → Social proof/outcome → Clear CTA.
+**Best for:** Data-driven prospects, high-ticket pitches with strong stats.
+
+> Companies in pharma lose 30% of leads due to manual outreach. Given {{Company}}'s growth this quarter, pipeline velocity is likely top of mind. Customers like Pfizer use our platform to automate lead qualification — cutting time-to-contact by 60%. Worth a 15-minute call?
+
+## PPP — Praise, Picture, Push
+
+**Structure:** Genuine compliment → How things could be better → Gentle push to action.
+**Best for:** Senior prospects who respond to relationship-building. Requires genuine trigger.
+
+> Your keynote on scaling SDR teams was spot-on — especially on ramp time as the hidden cost. What if you could cut that in half? Our in-inbox coach helps new reps write effective emails from day one with real-time scoring. Open to a quick chat about how this could support your growth?
+
+## Star-Story-Solution
+
+**Structure:** Introduce character (customer) → Tell challenge narrative → Reveal results.
+**Best for:** Strong customer success stories. Humanizes the pitch.
+
+> Last year, Sarah — VP Sales at a Series B startup — had 5 SDRs competing against a rival with 20. Her team was getting crushed on volume. They adopted our AI prospecting tool and sent hyper-personalized emails at 3x pace without losing quality. Within 90 days, they booked more meetings than their competitor's entire team. Happy to share how this could work for {{Company}}.
+
+## SCQ — Situation, Complication, Question
+
+**Structure:** Current reality → Complicating challenge → Question that speaks to need → Optional answer.
+**Best for:** Consultative selling. Mirrors how professionals present to leadership.
+
+> Your team doubled this year. That usually means onboarding is eating into selling time. How are you handling ramp for new hires?
+
+## ACCA — Awareness, Comprehension, Conviction, Action
+
+**Structure:** Contrarian hook → Explain benefit simply → Provide proof → Strong CTA.
+**Best for:** Analytical buyers who need evidence (engineers, CFOs, ops leaders).
+
+> Most sales teams measure rep activity. The top 5% measure rep efficiency instead. When Acme switched, they booked 40% more meetings with fewer emails. Worth seeing how?
+
+## 3C's (Alex Berman)
+
+**Structure:** Compliment → Case Study → CTA.
+**Best for:** Agency/services cold outreach. Case study does the heavy lifting.
+
+> Big fan of [Company]. We just built an app for [Competitor] that does XYZ. I have a few more ideas. Interested?
+
+## Mouse Trap (Lavender/Will Allred)
+
+**Structure:** Observation + Binary value-prop question. 1–2 sentences total.
+**Best for:** Maximum brevity. Impulsive reply based on curiosity.
+
+> Looks like you're hiring reps. Would it be helpful to get a more granular look at how they're ramping on email?
+
+## Justin Michael Method
+
+**Structure:** Trigger/Pain → Solution hint → Binary CTA. 1–3 sentences, no intro.
+**Best for:** High-velocity SDR teams. Mobile-optimized. Deliberately polarizing.
+
+Spend max 1 minute on personalization. Use industry/persona-level signals. For top-tier prospects, quote their own words from interviews — they almost always respond.
+
+## Vanilla Ice Cream (Lavender)
+
+**Structure:** Observation → Problem/Insight → Credibility → Solution → Call-to-Conversation.
+**Best for:** Universal "base" framework that works everywhere. Five parts.
+
+## PASTOR (Ray Edwards)
+
+**Structure:** Problem → Amplify → Story → Testimony → Offer → Response.
+**Best for:** Longer-form or multi-email sequences. Consulting, education, complex B2B services. Each element can be developed across separate touches.

skills/cold-email/references/personalization.md

@@ -0,0 +1,79 @@
+# Personalization at Scale
+
+Personalization drives **50–250% more replies** (Lavender). The key insight: **if your personalization has nothing to do with the problem you solve, it's just an attention hack** (Clay).
+
+## Four Levels of Personalization
+
+### Level 1 — Basic (merge tags)
+
+First name, company name, job title. Table stakes, no longer differentiating. ~5% lift.
+
+### Level 2 — Industry/segment
+
+Industry-specific pain points, trends, regulatory challenges. Scalable via micro-segmentation.
+
+> Most {{industry}} teams struggle with {{lead gen problem}}, which often leads to wasted effort.
+
+### Level 3 — Role-level
+
+Challenges specific to their role and seniority.
+
+> As Head of Sales, keeping pipeline steady is probably your biggest headache. Your RevOps team is small, so you're likely wearing multiple hats during scaling.
+
+### Level 4 — Individual (gold standard)
+
+Specific, timely observations about that person connected to the problem you solve.
+
+> Noticed you're hiring 3 SDRs — sounds like you're scaling outbound fast. Most teams hit follow-up fatigue during onboarding.
+
+## Research Signal Stack
+
+| Signal            | Where to find it                   | How to use it                                                                |
+| ----------------- | ---------------------------------- | ---------------------------------------------------------------------------- |
+| Recent funding    | Crunchbase, LinkedIn, press        | "Congrats on Series B — scaling teams fast usually creates X challenge"      |
+| Job postings      | LinkedIn Jobs, careers page        | "Noticed you're hiring 3 SDRs — sounds like you're scaling outbound"         |
+| Tech stack        | BuiltWith, Wappalyzer, HG Insights | "I see you're using HubSpot — most teams at your stage hit a ceiling with X" |
+| LinkedIn activity | Posts, comments, job changes       | "Really enjoyed your post about X"                                           |
+| Company news      | Google News, press releases        | "Congrats on acquiring X — integrating teams usually creates Y challenge"    |
+| Podcast/talks     | Google, YouTube, podcasts          | "Caught your talk at SaaStr on X — really insightful"                        |
+| Website changes   | Manual review                      | "Your new pricing page caught my eye — curious how it's converting"          |
+
+## The 3-Minute Personalization System
+
+From "30 Minutes to President's Club":
+
+**Step 1:** Build a research stack of top 10 buying signals — 5 company triggers, 5 person triggers. Stack-rank by relevance.
+
+**Step 2:** Build a 3x3 template: (1) personalization attached to a problem, (2) problem you solve, (3) one-sentence solution + low-friction CTA.
+
+**Step 3:** Create 5 "trigger templates" — pre-written personalization paragraphs for each trigger, with a smooth segue into the problem.
+
+The personalization must logically connect to the problem. This creates 5 reusable triggers with the rest of the email constant. A top SDR writes a personalized email in **under 3 minutes**.
+
+## The Four -Graphic Principles (Becc Holland)
+
+- **Demographic** — Age, profession, background
+- **Technographic** — Tech stack, tools used
+- **Firmographic** — Company size, funding, industry, growth stage
+- **Psychographic** — Values, passions, beliefs (highest-impact dimension)
+
+Tapping into what prospects are passionate about drives significantly higher response rates.
+
+## Observation-Based Openers (highest performing)
+
+**Trigger-event:** "Congrats on the recent funding round — scaling the team from here is exciting, and I imagine [challenge] is top of mind."
+
+**Observation:** "Your recent post about [topic] resonated — especially the part about [detail]. Got me thinking about how that applies to [challenge]."
+
+**Industry insight:** "Most [role titles] I talk to spend [X hours/week] on [problem] — curious if that matches your experience at [Company]."
+
+## What Feels Fake (avoid)
+
+- AI-generated emails with similar phrasing ("I hope this email finds you well")
+- Generic attention hacks disconnected from problem ("Cool that you went to UCLA!" → pitch)
+- Over-personalizing to creepiness
+- "I saw your LinkedIn profile and wanted to reach out" — signals mass automation
+
+## The "So What?" Test
+
+After writing any opening line, read from prospect's perspective: "So what? Why would I care?" If the answer is nothing, rewrite.

skills/cold-email/references/subject-lines.md

@@ -0,0 +1,53 @@
+# Subject Line Optimization
+
+The subject line determines whether the email gets read. The data is counterintuitive: **short, boring, internal-looking subject lines win decisively.**
+
+## Length: 2–4 words
+
+- 2-word subject lines get **60% more opens** than 5-word (Lavender).
+- Going from 2 to 4 words reduces replies by **17.5%**.
+- 2–4 words yield **46% open rates** vs 34% for 10 words (Belkins, 5.5M emails).
+- Mobile truncates at 30–35 characters — brevity is practical necessity.
+
+## Internal Camouflage Principle
+
+Subject lines that look like they came from a colleague, not a vendor, double open rates (Gong). Buyers mentally categorize before opening — if it looks like sales, it's filtered.
+
+**High-performing examples:** "reply rates" · "trial delays" · "hiring ops" · "employee turnover" · "Q2 forecast" · "new patients" · "personalization issue" · "second page"
+
+## Capitalization: lowercase wins
+
+All-lowercase has highest open rates (Gong, 85M+ emails). Lowercase looks more personal/internal. For cold outreach specifically, lowercase beats title case.
+
+## Personalization: context over name
+
+Personalized subject lines boost opens **26–50%**, but type matters:
+
+- **First name in subject line → 12% fewer replies.** Signals automation.
+- **Contextual personalization works:** pain points, competitors, trigger events, industry challenges.
+- Use {{painPoint}}, {{competitor}}, {{commonGround}} — not {{firstName}}.
+
+## Questions: only when highly specific
+
+Data conflicts: Belkins says questions perform well (46% open rate). Lavender says questions lower opens by **56%**. Resolution: **specific pain questions work** ("Need help with {{challenge}}?"), **generic questions fail** ("Quick question?" / "Have 15 minutes?"). Default to statements.
+
+## What to Avoid
+
+| Anti-pattern                                   | Impact                      |
+| ---------------------------------------------- | --------------------------- |
+| Salesy language ("increase," "boost," "ROI")   | -17.9% opens                |
+| Urgency words ("ASAP," "urgent")               | Below 36% opens             |
+| Excessive punctuation ("!!!" or "??")          | -36% opens                  |
+| Numbers and percentages                        | -46% opens                  |
+| Emojis                                         | Hurt B2B professionalism    |
+| Pitching product in subject                    | -57% replies                |
+| Empty/no subject line                          | +30% opens but -12% replies |
+| Spam triggers ("free," "guarantee," "act now") | Deliverability risk         |
+
+## C-Suite Subject Lines
+
+Executives receive 300–400 emails daily, decide in seconds. They respond **23% more often** than non-C-suite when emails pass their filter (6.4% reply rate).
+
+What works: ultra-concise, human, understated. "{{companyInitiative}}" · "thank you" · "an update" · "a question" · reference to a specific project or trigger event.
+
+Anything "salesy" is immediately rejected.

skills/competitor-alternatives/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: competitor-alternatives
-version: 1.0.0
 description: "When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' or 'competitive landing pages.' Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. Emphasizes deep research, modular content architecture, and varied section types beyond feature tables."
+metadata:
+  version: 1.0.0
 ---
 
 # Competitor & Alternative Pages

skills/competitor-alternatives/references/content-architecture.md

@@ -2,6 +2,14 @@
 
 How to structure and maintain competitor data for scalable comparison pages.
 
+## Contents
+- Centralized Competitor Data
+- Competitor Data Template
+- Your Product Data
+- Page Generation
+- Index Page Structure (alternatives index, vs comparisons index, index page best practices)
+- Footer Navigation
+
 ## Centralized Competitor Data
 
 Create a single source of truth for each competitor:

skills/competitor-alternatives/references/templates.md

@@ -2,6 +2,17 @@
 
 Ready-to-use templates for each section of competitor comparison pages.
 
+## Contents
+- TL;DR Summary
+- Paragraph Comparison (Not Just Tables)
+- Feature Comparison Section
+- Pricing Comparison Section
+- Service & Support Comparison
+- Who It's For Section
+- Migration Section
+- Social Proof Section
+- Comparison Table Best Practices (beyond checkmarks, organize by category, include ratings where useful)
+
 ## TL;DR Summary
 
 Start every page with a quick summary for scanners:

skills/content-strategy/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: content-strategy
-version: 1.0.0
 description: When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," or "content planning." For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit.
+metadata:
+  version: 1.0.0
 ---
 
 # Content Strategy

skills/copy-editing/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: copy-editing
-version: 1.0.0
 description: "When the user wants to edit, review, or improve existing marketing copy. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this better,' or 'copy sweep.' This skill provides a systematic approach to editing marketing copy through multiple focused passes."
+metadata:
+  version: 1.0.0
 ---
 
 # Copy Editing

skills/copy-editing/references/plain-english-alternatives.md

@@ -6,6 +6,24 @@ Source: Plain English Campaign A-Z of Alternative Words (2001), Australian Gover
 
 ---
 
+## Contents
+- A
+- B
+- C
+- D
+- E
+- F
+- G-H
+- I
+- L-M
+- N-O
+- P
+- R
+- S
+- T-U
+- V-Z
+- Phrases to Remove Entirely
+
 ## A
 
 | Complex | Plain Alternative |

skills/copywriting/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: copywriting
-version: 1.0.0
 description: When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," or "CTA copy." For email copy, see email-sequence. For popup copy, see popup-cro.
+metadata:
+  version: 1.0.0
 ---
 
 # Copywriting

skills/copywriting/references/copy-frameworks.md

@@ -2,6 +2,12 @@
 
 Headline formulas, page section types, and structural templates.
 
+## Contents
+- Headline Formulas (outcome-focused, problem-focused, audience-focused, differentiation-focused, proof-focused, additional formulas)
+- Landing Page Section Types (core sections, supporting sections)
+- Page Structure Templates (feature-heavy page, varied engaging page, compact landing page, enterprise/B2B landing page, product launch page)
+- Section Writing Tips (problem section, benefits section, how it works section, testimonial selection)
+
 ## Headline Formulas
 
 ### Outcome-Focused

skills/copywriting/references/natural-transitions.md

@@ -6,6 +6,26 @@ Adapted from: University of Manchester Academic Phrasebank (2023), Plain English
 
 ---
 
+## Contents
+- Previewing Content Structure
+- Introducing a New Topic
+- Referring Back
+- Moving Between Sections
+- Indicating Addition
+- Indicating Contrast
+- Indicating Similarity
+- Indicating Cause and Effect
+- Giving Examples
+- Emphasising Key Points
+- Providing Evidence (neutral attribution, expert quotes, supporting claims)
+- Summarising Sections
+- Concluding Content
+- Question-Based Transitions
+- List Introductions
+- Hedging Language
+- Best Practice Guidelines
+- Transitions to Avoid (AI Tells)
+
 ## Previewing Content Structure
 
 Use to orient readers and set expectations:

skills/email-sequence/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: email-sequence
-version: 1.0.0
 description: When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," or "lifecycle emails." For in-app onboarding, see onboarding-cro.
+metadata:
+  version: 1.0.0
 ---
 
 # Email Sequence Design

skills/email-sequence/references/copy-guidelines.md

@@ -1,5 +1,15 @@
 # Email Copy Guidelines
 
+## Contents
+- Structure
+- Formatting
+- Tone
+- Length
+- CTA Buttons vs. Links
+- Personalization (merge fields, dynamic content, triggered emails)
+- Segmentation Strategies (by behavior, by stage, by profile)
+- Testing and Optimization (what to test, how to test, metrics to track)
+
 ## Structure
 
 1. **Hook**: First line grabs attention

skills/email-sequence/references/email-types.md

@@ -2,6 +2,15 @@
 
 A comprehensive guide to lifecycle and campaign emails. Use this as an audit checklist and implementation reference.
 
+## Contents
+- Onboarding Emails (new users series, new customers series, key onboarding step reminder, new user invite)
+- Retention Emails (upgrade to paid, upgrade to higher plan, ask for review, offer support proactively, product usage report, NPS survey, referral program)
+- Billing Emails (switch to annual, failed payment recovery, cancellation survey, upcoming renewal reminder)
+- Usage Emails (daily/weekly/monthly summary, key event or milestone notifications)
+- Win-Back Emails (expired trials, cancelled customers)
+- Campaign Emails (monthly roundup/newsletter, seasonal promotions, product updates, industry news roundup, pricing update)
+- Email Audit Checklist (onboarding, retention, billing, usage, win-back, campaigns)
+
 ## Onboarding Emails
 
 ### New Users Series

skills/email-sequence/references/sequence-templates.md

@@ -2,6 +2,12 @@
 
 Detailed templates for common email sequences.
 
+## Contents
+- Welcome Sequence (Post-Signup)
+- Lead Nurture Sequence (Pre-Sale)
+- Re-Engagement Sequence
+- Onboarding Sequence (Product Users)
+
 ## Welcome Sequence (Post-Signup)
 
 **Email 1: Welcome (Immediate)**

skills/form-cro/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: form-cro
-version: 1.0.0
 description: When the user wants to optimize any form that is NOT signup/registration — including lead capture forms, contact forms, demo request forms, application forms, survey forms, or checkout forms. Also use when the user mentions "form optimization," "lead form conversions," "form friction," "form fields," "form completion rate," or "contact form." For signup/registration forms, see signup-flow-cro. For popups containing forms, see popup-cro.
+metadata:
+  version: 1.0.0
 ---
 
 # Form CRO

skills/free-tool-strategy/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: free-tool-strategy
-version: 1.0.0
 description: When the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or brand awareness. Also use when the user mentions "engineering as marketing," "free tool," "marketing tool," "calculator," "generator," "interactive tool," "lead gen tool," "build a tool for leads," or "free resource." This skill bridges engineering and marketing — useful for founders and technical marketers.
+metadata:
+  version: 1.0.0
 ---
 
 # Free Tool Strategy (Engineering as Marketing)

skills/free-tool-strategy/references/tool-types.md

@@ -2,6 +2,15 @@
 
 Detailed guide to each type of marketing tool you can build.
 
+## Contents
+- Calculators
+- Generators
+- Analyzers/Auditors
+- Testers/Validators
+- Libraries/Resources
+- Interactive Educational
+- Tool Concept Examples by Industry (SaaS product, agency/services, e-commerce, developer tools, finance)
+
 ## Calculators
 
 **Best for**: Decisions involving numbers, comparisons, estimates

skills/launch-strategy/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: launch-strategy
-version: 1.0.0
 description: "When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' or 'product update.' This skill covers phased launches, channel strategy, and ongoing launch momentum."
+metadata:
+  version: 1.0.0
 ---
 
 # Launch Strategy

skills/marketing-ideas/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: marketing-ideas
-version: 1.0.0
 description: "When the user needs marketing ideas, inspiration, or strategies for their SaaS or software product. Also use when the user asks for 'marketing ideas,' 'growth ideas,' 'how to market,' 'marketing strategies,' 'marketing tactics,' 'ways to promote,' or 'ideas to grow.' This skill provides 139 proven marketing approaches organized by category."
+metadata:
+  version: 1.0.0
 ---
 
 # Marketing Ideas for SaaS

skills/marketing-ideas/references/ideas-by-category.md

@@ -2,6 +2,25 @@
 
 Complete list of proven marketing approaches organized by category.
 
+## Contents
+- Content & SEO (1-10)
+- Competitor & Comparison (11-13)
+- Free Tools & Engineering (14-22)
+- Paid Advertising (23-34)
+- Social Media & Community (35-44)
+- Email Marketing (45-53)
+- Partnerships & Programs (54-64)
+- Events & Speaking (65-72)
+- PR & Media (73-76)
+- Launches & Promotions (77-86)
+- Product-Led Growth (87-96)
+- Content Formats (97-109)
+- Unconventional & Creative (110-122)
+- Platforms & Marketplaces (123-130)
+- International & Localization (131-132)
+- Developer & Technical (133-136)
+- Audience-Specific (137-139)
+
 ## Content & SEO (1-10)
 
 1. **Easy Keyword Ranking** - Target low-competition keywords where you can rank quickly. Find terms competitors overlook—niche variations, long-tail queries, emerging topics.

skills/marketing-psychology/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: marketing-psychology
-version: 1.0.0
 description: "When the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when the user mentions 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,' 'behavioral science,' 'why people buy,' 'decision-making,' or 'consumer behavior.' This skill provides 70+ mental models organized for marketing application."
+metadata:
+  version: 1.0.0
 ---
 
 # Marketing Psychology & Mental Models

skills/onboarding-cro/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: onboarding-cro
-version: 1.0.0
 description: When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," or "new user experience." For signup/registration optimization, see signup-flow-cro. For ongoing email sequences, see email-sequence.
+metadata:
+  version: 1.0.0
 ---
 
 # Onboarding CRO

skills/onboarding-cro/references/experiments.md

@@ -2,6 +2,16 @@
 
 Comprehensive list of A/B tests and experiments for user onboarding and activation.
 
+## Contents
+- Flow Simplification Experiments (reduce friction, step sequencing, progress & motivation)
+- Guided Experience Experiments (product tours, CTA optimization, UI guidance)
+- Personalization Experiments (user segmentation, dynamic content)
+- Quick Wins & Engagement Experiments (time-to-value, motivation mechanics, support & help)
+- Email & Multi-Channel Experiments (onboarding emails, email content, feedback loops)
+- Re-engagement Experiments (stalled user recovery, return experience)
+- Technical & UX Experiments (performance, mobile onboarding, accessibility)
+- Metrics to Track
+
 ## Flow Simplification Experiments
 
 ### Reduce Friction

skills/page-cro/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: page-cro
-version: 1.0.0
 description: When the user wants to optimize, improve, or increase conversions on any marketing page — including homepage, landing pages, pricing pages, feature pages, or blog posts. Also use when the user says "CRO," "conversion rate optimization," "this page isn't converting," "improve conversions," or "why isn't this page working." For signup/registration flows, see signup-flow-cro. For post-signup activation, see onboarding-cro. For forms outside of signup, see form-cro. For popups/modals, see popup-cro.
+metadata:
+  version: 1.0.0
 ---
 
 # Page Conversion Rate Optimization (CRO)

skills/page-cro/references/experiments.md

@@ -2,6 +2,15 @@
 
 Comprehensive list of A/B tests and experiments organized by page type.
 
+## Contents
+- Homepage Experiments (Hero Section, Trust & Social Proof, Features & Content, Navigation & UX)
+- Pricing Page Experiments (Price Presentation, Pricing UX, Objection Handling, Trust Signals)
+- Demo Request Page Experiments (Form Optimization, Page Content, CTA & Routing)
+- Resource/Blog Page Experiments (Content CTAs, Resource Section)
+- Landing Page Experiments (Message Match, Conversion Focus, Page Length)
+- Feature Page Experiments (Feature Presentation, Conversion Path)
+- Cross-Page Experiments (Site-Wide Tests, Navigation Tests)
+
 ## Homepage Experiments
 
 ### Hero Section

skills/paid-ads/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: paid-ads
-version: 1.0.0
 description: "When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions 'PPC,' 'paid media,' 'ad copy,' 'ad creative,' 'ROAS,' 'CPA,' 'ad campaign,' 'retargeting,' or 'audience targeting.' This skill covers campaign strategy, ad creation, audience targeting, and optimization."
+metadata:
+  version: 1.0.0
 ---
 
 # Paid Ads

skills/paid-ads/references/ad-copy-templates.md

@@ -2,6 +2,13 @@
 
 Detailed formulas and templates for writing high-converting ad copy.
 
+## Contents
+- Primary Text Formulas (Problem-Agitate-Solve, Before-After-Bridge, Social Proof Lead, Feature-Benefit Bridge, Direct Response)
+- Headline Formulas (For Search Ads, For Social Ads)
+- CTA Variations (Soft CTAs, Hard CTAs, Urgency CTAs, Action-Oriented CTAs)
+- Platform-Specific Copy Guidelines (Google Search Ads, Meta Ads, LinkedIn Ads)
+- Copy Testing Priority
+
 ## Primary Text Formulas
 
 ### Problem-Agitate-Solve (PAS)

skills/paid-ads/references/audience-targeting.md

@@ -2,6 +2,15 @@
 
 Detailed targeting strategies for each major ad platform.
 
+## Contents
+- Google Ads Audiences (Search Campaign Targeting, Display/YouTube Targeting)
+- Meta Audiences (Core Audiences, Custom Audiences, Lookalike Audiences)
+- LinkedIn Audiences (Job-Based Targeting, Company-Based Targeting, High-Performing Combinations)
+- Twitter/X Audiences
+- TikTok Audiences
+- Audience Size Guidelines
+- Exclusion Strategy
+
 ## Google Ads Audiences
 
 ### Search Campaign Targeting

skills/paid-ads/references/platform-setup-checklists.md

@@ -2,6 +2,14 @@
 
 Complete setup checklists for major ad platforms.
 
+## Contents
+- Google Ads Setup (Account Foundation, Conversion Tracking, Analytics Integration, Audience Setup, Campaign Readiness, Ad Extensions, Brand Protection)
+- Meta Ads Setup (Business Manager Foundation, Pixel & Tracking, Domain & Aggregated Events, Audience Setup, Catalog, Creative Assets, Compliance)
+- LinkedIn Ads Setup (Campaign Manager Foundation, Insight Tag & Tracking, Audience Setup, Lead Gen Forms, Document Ads, Creative Assets, Budget Considerations)
+- Twitter/X Ads Setup (Account Foundation, Tracking, Audience Setup, Creative)
+- TikTok Ads Setup (Account Foundation, Pixel & Tracking, Audience Setup, Creative)
+- Universal Pre-Launch Checklist
+
 ## Google Ads Setup
 
 ### Account Foundation

skills/paywall-upgrade-cro/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: paywall-upgrade-cro
-version: 1.0.0
 description: When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," or "in-app pricing." Distinct from public pricing pages (see page-cro) — this skill focuses on in-product upgrade moments where the user has already experienced value.
+metadata:
+  version: 1.0.0
 ---
 
 # Paywall and Upgrade Screen CRO

skills/paywall-upgrade-cro/references/experiments.md

@@ -2,6 +2,15 @@
 
 Comprehensive list of A/B tests and experiments for paywall optimization.
 
+## Contents
+- Trigger & Timing Experiments (When to Show, Trigger Type)
+- Paywall Design Experiments (Layout & Format, Value Presentation, Visual Elements)
+- Pricing Presentation Experiments (Price Display, Plan Options, Discounts & Offers)
+- Copy & Messaging Experiments (Headlines, CTAs, Objection Handling)
+- Trial & Conversion Experiments (Trial Structure, Trial Expiration, Upgrade Path)
+- Personalization Experiments (Usage-Based, Segment-Specific)
+- Frequency & UX Experiments (Frequency Capping, Dismiss Behavior)
+
 ## Trigger & Timing Experiments
 
 ### When to Show

skills/popup-cro/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: popup-cro
-version: 1.0.0
 description: When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," or "overlay." For forms outside of popups, see form-cro. For general page conversion optimization, see page-cro.
+metadata:
+  version: 1.0.0
 ---
 
 # Popup CRO

skills/pricing-strategy/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: pricing-strategy
-version: 1.0.0
 description: "When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' or 'monetization.' This skill covers pricing research, tier structure, and packaging strategy."
+metadata:
+  version: 1.0.0
 ---
 
 # Pricing Strategy

skills/pricing-strategy/references/research-methods.md

@@ -1,5 +1,11 @@
 # Pricing Research Methods
 
+## Contents
+- Van Westendorp Price Sensitivity Meter (The Four Questions, How to Analyze, Survey Tips, Sample Output)
+- MaxDiff Analysis (How It Works, Example Survey Question, Analyzing Results, Using MaxDiff for Packaging)
+- Willingness to Pay Surveys
+- Usage-Value Correlation Analysis
+
 ## Van Westendorp Price Sensitivity Meter
 
 The Van Westendorp survey identifies the acceptable price range for your product.

skills/pricing-strategy/references/tier-structure.md

@@ -1,5 +1,14 @@
 # Tier Structure and Packaging
 
+## Contents
+- How Many Tiers?
+- Good-Better-Best Framework
+- Tier Differentiation Strategies
+- Example Tier Structure
+- Packaging for Personas (Identifying Pricing Personas, Persona-Based Packaging)
+- Freemium vs. Free Trial (When to Use Freemium, When to Use Free Trial, Hybrid Approaches)
+- Enterprise Pricing (When to Add Custom Pricing, Enterprise Tier Elements, Enterprise Pricing Strategies)
+
 ## How Many Tiers?
 
 **2 tiers:** Simple, clear choice

skills/product-marketing-context/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: product-marketing-context
-version: 1.0.0
 description: "When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' or wants to avoid repeating foundational information across marketing tasks. Creates `.claude/product-marketing-context.md` that other marketing skills reference."
+metadata:
+  version: 1.0.0
 ---
 
 # Product Marketing Context

skills/programmatic-seo/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: programmatic-seo
-version: 1.0.0
 description: When the user wants to create SEO-driven pages at scale using templates and data. Also use when the user mentions "programmatic SEO," "template pages," "pages at scale," "directory pages," "location pages," "[keyword] + [city] pages," "comparison pages," "integration pages," or "building many pages for SEO." For auditing existing SEO issues, see seo-audit.
+metadata:
+  version: 1.0.0
 ---
 
 # Programmatic SEO

skills/programmatic-seo/references/playbooks.md

@@ -2,6 +2,21 @@
 
 Beyond mixing and matching data point permutations, these are the proven playbooks for programmatic SEO.
 
+## Contents
+- 1. Templates
+- 2. Curation
+- 3. Conversions
+- 4. Comparisons
+- 5. Examples
+- 6. Locations
+- 7. Personas
+- 8. Integrations
+- 9. Glossary
+- 10. Translations
+- 11. Directory
+- 12. Profiles
+- Choosing Your Playbook (Match to Your Assets, Combine Playbooks)
+
 ## 1. Templates
 
 **Pattern**: "[Type] template" or "free [type] template"

skills/referral-program/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: referral-program
-version: 1.0.0
 description: "When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy. Also use when the user mentions 'referral,' 'affiliate,' 'ambassador,' 'word of mouth,' 'viral loop,' 'refer a friend,' or 'partner program.' This skill covers program design, incentive structure, and growth optimization."
+metadata:
+  version: 1.0.0
 ---
 
 # Referral & Affiliate Programs

skills/referral-program/references/affiliate-programs.md

@@ -2,6 +2,14 @@
 
 Detailed guidance for building and managing affiliate programs.
 
+## Contents
+- Commission Structures
+- Cookie Duration
+- Affiliate Recruitment
+- Affiliate Enablement
+- Tools & Platforms (Referral Program Tools, Affiliate Program Tools, Choosing a Tool)
+- Fraud Prevention (Common Referral Fraud, Prevention Measures)
+
 ## Commission Structures
 
 **Percentage of sale:**

skills/referral-program/references/program-examples.md

@@ -2,6 +2,15 @@
 
 Real-world examples of successful referral programs.
 
+## Contents
+- Dropbox (Classic)
+- Uber/Lyft
+- Morning Brew
+- Notion
+- Incentive Types Comparison
+- Incentive Sizing Framework
+- Viral Coefficient & Metrics (Key Metrics, Calculating Referral Program ROI)
+
 ## Dropbox (Classic)
 
 **Program:** Give 500MB storage, get 500MB storage

skills/schema-markup/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: schema-markup
-version: 1.0.0
 description: When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," or "breadcrumb schema." For broader SEO issues, see seo-audit.
+metadata:
+  version: 1.0.0
 ---
 
 # Schema Markup

skills/schema-markup/references/schema-examples.md

@@ -2,6 +2,20 @@
 
 Complete JSON-LD examples for common schema types.
 
+## Contents
+- Organization
+- WebSite (with SearchAction)
+- Article / BlogPosting
+- Product
+- SoftwareApplication
+- FAQPage
+- HowTo
+- BreadcrumbList
+- LocalBusiness
+- Event
+- Multiple Schema Types
+- Implementation Example (Next.js)
+
 ## Organization
 
 For company/brand homepage or about page.

skills/seo-audit/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: seo-audit
-version: 1.0.0
 description: When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," or "SEO health check." For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup.
+metadata:
+  version: 1.0.0
 ---
 
 # SEO Audit
@@ -34,6 +35,19 @@ Before auditing, understand:
 
 ## Audit Framework
 
+### ⚠️ Important: Schema Markup Detection Limitation
+
+**`web_fetch` and `curl` cannot reliably detect structured data / schema markup.**
+
+Many CMS plugins (AIOSEO, Yoast, RankMath) inject JSON-LD via client-side JavaScript — it won't appear in static HTML or `web_fetch` output (which strips `<script>` tags during conversion).
+
+**To accurately check for schema markup, use one of these methods:**
+1. **Browser tool** — render the page and run: `document.querySelectorAll('script[type="application/ld+json"]')`
+2. **Google Rich Results Test** — https://search.google.com/test/rich-results
+3. **Screaming Frog export** — if the client provides one, use it (SF renders JavaScript)
+
+**Never report "no schema found" based solely on `web_fetch` or `curl`.** This has led to false audit findings in production.
+
 ### Priority Order
 1. **Crawlability & Indexation** (can Google find and index it?)
 2. **Technical Foundations** (is the site fast and functional?)
@@ -364,10 +378,12 @@ Same format as above
 - Google Search Console (essential)
 - Google PageSpeed Insights
 - Bing Webmaster Tools
-- Rich Results Test
+- Rich Results Test (**use this for schema validation — it renders JavaScript**)
 - Mobile-Friendly Test
 - Schema Validator
 
+> **Note on schema detection:** `web_fetch` strips `<script>` tags (including JSON-LD) and cannot detect JS-injected schema. Always use the browser tool, Rich Results Test, or Screaming Frog for schema checks. See the warning at the top of the Audit Framework section.
+
 **Paid Tools** (if available)
 - Screaming Frog
 - Ahrefs / Semrush

skills/seo-audit/references/aeo-geo-patterns.md

@@ -4,6 +4,12 @@ Reusable content block patterns optimized for answer engines and AI citation.
 
 ---
 
+## Contents
+- Answer Engine Optimization (AEO) Patterns (Definition Block, Step-by-Step Block, Comparison Table Block, Pros and Cons Block, FAQ Block, Listicle Block)
+- Generative Engine Optimization (GEO) Patterns (Statistic Citation Block, Expert Quote Block, Authoritative Claim Block, Self-Contained Answer Block, Evidence Sandwich Block)
+- Domain-Specific GEO Tactics (Technology Content, Health/Medical Content, Financial Content, Legal Content, Business/Marketing Content)
+- Voice Search Optimization (Question Formats for Voice, Voice-Optimized Answer Structure)
+
 ## Answer Engine Optimization (AEO) Patterns
 
 These patterns help content appear in featured snippets, AI Overviews, voice search results, and answer boxes.

skills/seo-audit/references/ai-writing-detection.md

@@ -6,6 +6,16 @@ Sources: Grammarly (2025), Microsoft 365 Life Hacks (2025), GPTHuman (2025), Wal
 
 ---
 
+## Contents
+- Em Dashes: The Primary AI Tell
+- Overused Verbs
+- Overused Adjectives
+- Overused Transitions and Connectors
+- Phrases That Signal AI Writing (Opening Phrases, Transitional Phrases, Concluding Phrases, Structural Patterns)
+- Filler Words and Empty Intensifiers
+- Academic-Specific AI Tells
+- How to Self-Check
+
 ## Em Dashes: The Primary AI Tell
 
 **The em dash (—) has become one of the most reliable markers of AI-generated content.**

skills/signup-flow-cro/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: signup-flow-cro
-version: 1.0.0
 description: When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions "signup conversions," "registration friction," "signup form optimization," "free trial signup," "reduce signup dropoff," or "account creation flow." For post-signup onboarding, see onboarding-cro. For lead capture forms (not account creation), see form-cro.
+metadata:
+  version: 1.0.0
 ---
 
 # Signup Flow CRO

skills/social-content/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: social-content
-version: 1.0.0
 description: "When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms. Also use when the user mentions 'LinkedIn post,' 'Twitter thread,' 'social media,' 'content calendar,' 'social scheduling,' 'engagement,' or 'viral content.' This skill covers content creation, repurposing, and platform-specific strategies."
+metadata:
+  version: 1.0.0
 ---
 
 # Social Content

skills/social-content/references/platforms.md

@@ -2,6 +2,13 @@
 
 Detailed strategies for each major social platform.
 
+## Contents
+- LinkedIn
+- Twitter/X
+- Instagram
+- TikTok
+- Facebook
+
 ## LinkedIn
 
 **Best for:** B2B, thought leadership, professional networking, recruiting

skills/social-content/references/post-templates.md

@@ -2,6 +2,12 @@
 
 Ready-to-use templates for different platforms and content types.
 
+## Contents
+- LinkedIn Post Templates (The Story Post, The Contrarian Take, The List Post, The How-To)
+- Twitter/X Thread Templates (The Tutorial Thread, The Story Thread, The Breakdown Thread)
+- Instagram Templates (The Carousel Hook, The Reel Script)
+- Hook Formulas (Curiosity Hooks, Story Hooks, Value Hooks, Contrarian Hooks, Social Proof Hooks)
+
 ## LinkedIn Post Templates
 
 ### The Story Post

skills/social-content/references/reverse-engineering.md

@@ -2,6 +2,11 @@
 
 Instead of guessing what works, systematically analyze top-performing content in your niche and extract proven patterns.
 
+## Contents
+- The 6-Step Framework (Niche ID, Scrape, Analyze, Playbook, Layer Voice, Convert)
+- The Formula
+- Reverse Engineering Checklist
+
 ## The 6-Step Framework
 
 ### 1. NICHE ID — Find Top Creators

validate-skills-official.sh

@@ -0,0 +1,85 @@
+#!/bin/bash
+
+# Validation script using official skills-ref library
+# https://github.com/agentskills/agentskills/tree/main/skills-ref
+
+SKILLS_DIR="skills"
+SKILLS_REF_DIR="/tmp/agentskills/skills-ref"
+
+echo "🔍 Validating Skills Using Official skills-ref Library"
+echo "========================================================"
+echo "Reference: https://github.com/agentskills/agentskills"
+echo ""
+
+# Check if skills-ref is already installed
+if [ ! -d "$SKILLS_REF_DIR/.venv" ]; then
+    echo "📦 Installing skills-ref library..."
+    echo ""
+
+    if [ ! -d "$SKILLS_REF_DIR" ]; then
+        cd /tmp
+        git clone https://github.com/agentskills/agentskills.git
+    fi
+
+    cd "$SKILLS_REF_DIR"
+
+    if command -v uv &> /dev/null; then
+        echo "Using uv to install..."
+        uv sync
+    else
+        echo "Using pip to install..."
+        python3 -m venv .venv
+        source .venv/bin/activate
+        pip install -e .
+    fi
+    echo ""
+fi
+
+# Activate the virtual environment
+source "$SKILLS_REF_DIR/.venv/bin/activate"
+
+# Return to the original directory
+cd "$(dirname "$0")"
+
+# Track results
+PASSED=0
+FAILED=0
+FAILED_SKILLS=()
+
+echo "Running validation..."
+echo ""
+
+# Validate each skill
+for skill_dir in "$SKILLS_DIR"/*/; do
+    skill_name=$(basename "$skill_dir")
+    printf "  %-30s" "$skill_name"
+
+    output=$(skills-ref validate "$skill_dir" 2>&1)
+    if echo "$output" | grep -q "Valid skill"; then
+        echo "✓"
+        ((PASSED++))
+    else
+        echo "✗"
+        ((FAILED++))
+        FAILED_SKILLS+=("$skill_name")
+        echo "$output" | sed 's/^/    /'
+    fi
+done
+
+echo ""
+echo "========================================================"
+echo "Summary:"
+echo "  ✓ Passed: $PASSED"
+echo "  ✗ Failed: $FAILED"
+echo ""
+
+if [ $FAILED -eq 0 ]; then
+    echo "✅ All skills are valid!"
+    exit 0
+else
+    echo "❌ Failed skills:"
+    for skill in "${FAILED_SKILLS[@]}"; do
+        echo "  - $skill"
+    done
+    exit 1
+fi

validate-skills.sh

@@ -0,0 +1,169 @@
+#!/bin/bash
+
+# Colors for output
+RED='\033[0;31m'
+GREEN='\033[0;32m'
+YELLOW='\033[1;33m'
+BLUE='\033[0;34m'
+NC='\033[0m' # No Color
+
+SKILLS_DIR="skills"
+ISSUES=0
+WARNINGS=0
+PASSED=0
+
+echo "🔍 Auditing Skills Against Agent Skills Specification"
+echo "======================================================"
+echo ""
+echo "Reference: https://agentskills.io/specification.md"
+echo ""
+
+# Validation rules from CLAUDE.md
+# REQUIRED: name, description
+# OPTIONAL: license, metadata
+# name: 1-64 chars, lowercase a-z, numbers, hyphens only, must match directory
+# description: 1-1024 chars with trigger phrases
+# SKILL.md: under 500 lines
+# Optional dirs: references/, scripts/, assets/
+
+for skill_dir in "$SKILLS_DIR"/*/; do
+    skill_name=$(basename "$skill_dir")
+    skill_file="$skill_dir/SKILL.md"
+    skill_errors=()
+    skill_warnings=()
+
+    # Check if SKILL.md exists
+    if [[ ! -f "$skill_file" ]]; then
+        echo -e "${RED}❌ $skill_name${NC}"
+        echo "   Missing SKILL.md"
+        ((ISSUES++))
+        continue
+    fi
+
+    # Extract frontmatter
+    frontmatter=$(sed -n '/^---$/,/^---$/p' "$skill_file" | head -n -1 | tail -n +2)
+
+    # Validate frontmatter exists
+    if [[ -z "$frontmatter" ]]; then
+        echo -e "${RED}❌ $skill_name${NC}"
+        echo "   Missing YAML frontmatter (---)"
+        ((ISSUES++))
+        continue
+    fi
+
+    # ===== NAME VALIDATION =====
+    name_in_file=$(echo "$frontmatter" | grep "^name:" | sed 's/^name: //' | tr -d ' ')
+
+    if [[ -z "$name_in_file" ]]; then
+        skill_errors+=("Missing 'name' field in frontmatter")
+    elif [[ "$name_in_file" != "$skill_name" ]]; then
+        skill_errors+=("Name mismatch: directory='$skill_name' but frontmatter='$name_in_file'")
+    elif ! [[ "$name_in_file" =~ ^[a-z0-9]([a-z0-9-]{0,62}[a-z0-9])?$ ]]; then
+        skill_errors+=("Invalid name format: '$name_in_file' (must be lowercase, alphanumeric + hyphens only)")
+    elif [[ ${#name_in_file} -lt 1 || ${#name_in_file} -gt 64 ]]; then
+        skill_errors+=("Name length invalid: ${#name_in_file} chars (must be 1-64)")
+    fi
+
+    # ===== DESCRIPTION VALIDATION =====
+    # Handle both quoted and unquoted descriptions
+    description=$(echo "$frontmatter" | grep "^description:" | head -1)
+    if [[ $description == *'description: "'* ]]; then
+        # Quoted description - extract between quotes
+        description=$(echo "$description" | sed 's/^description: "//' | sed 's/"$//')
+    else
+        # Unquoted description
+        description=$(echo "$description" | sed 's/^description: //')
+    fi
+
+    if [[ -z "$description" ]]; then
+        skill_errors+=("Missing 'description' field in frontmatter")
+    else
+        desc_len=${#description}
+        if [[ $desc_len -lt 1 || $desc_len -gt 1024 ]]; then
+            skill_errors+=("Description length invalid: $desc_len chars (must be 1-1024)")
+        fi
+
+        # Check for trigger phrases (When, when to use, mentions, etc.)
+        if ! echo "$description" | grep -qi "when\|mention\|use"; then
+            skill_warnings+=("Description lacks clear trigger phrases ('when', 'mention', 'use')")
+        fi
+
+        # Check for related skills reference (scope boundaries)
+        if ! echo "$description" | grep -qi "see\|for\|ref"; then
+            skill_warnings+=("Description lacks related skills reference (e.g., 'For X, see Y')")
+        fi
+    fi
+
+    # ===== OPTIONAL FIELDS VALIDATION =====
+    license=$(echo "$frontmatter" | grep "^license:" | sed 's/^license: //' | tr -d ' ')
+    if [[ -n "$license" && "$license" != "MIT" && "$license" != "Apache-2.0" && "$license" != "ISC" ]]; then
+        skill_warnings+=("License '$license' is non-standard (default: MIT)")
+    fi
+
+    # Check metadata structure
+    metadata=$(echo "$frontmatter" | grep -A 10 "^metadata:")
+    if [[ -n "$metadata" ]]; then
+        # If metadata exists, check for version placement
+        if echo "$frontmatter" | grep -q "^version:"; then
+            skill_errors+=("'version' is top-level (should be under 'metadata:')")
+        fi
+        # Could add more metadata validation here
+    fi
+
+    # ===== FILE STRUCTURE VALIDATION =====
+    line_count=$(wc -l < "$skill_file")
+    if [[ $line_count -gt 500 ]]; then
+        skill_warnings+=("SKILL.md is $line_count lines (should be <500, move details to references/)")
+    fi
+
+    # Check for optional directories
+    for optdir in references scripts assets; do
+        if [[ -d "$skill_dir/$optdir" ]]; then
+            # Just note its presence - no validation required
+            :
+        fi
+    done
+
+    # ===== REPORT RESULTS =====
+    if [[ ${#skill_errors[@]} -gt 0 ]]; then
+        echo -e "${RED}❌ $skill_name${NC}"
+        for error in "${skill_errors[@]}"; do
+            echo -e "   ${RED}Error:${NC} $error"
+        done
+        if [[ ${#skill_warnings[@]} -gt 0 ]]; then
+            for warning in "${skill_warnings[@]}"; do
+                echo -e "   ${YELLOW}Warning:${NC} $warning"
+            done
+        fi
+        ((ISSUES++))
+    elif [[ ${#skill_warnings[@]} -gt 0 ]]; then
+        echo -e "${YELLOW}⚠️  $skill_name${NC}"
+        for warning in "${skill_warnings[@]}"; do
+            echo -e "   ${YELLOW}Warning:${NC} $warning"
+        done
+        ((WARNINGS++))
+    else
+        echo -e "${GREEN}✓ $skill_name${NC}"
+        ((PASSED++))
+    fi
+done
+
+echo ""
+echo "======================================================"
+echo "Summary:"
+echo -e "  ${GREEN}✓ Passed: $PASSED${NC}"
+if [[ $WARNINGS -gt 0 ]]; then
+    echo -e "  ${YELLOW}⚠️  Warnings: $WARNINGS${NC}"
+fi
+if [[ $ISSUES -gt 0 ]]; then
+    echo -e "  ${RED}❌ Issues: $ISSUES${NC}"
+fi
+echo ""
+
+if [[ $ISSUES -eq 0 ]]; then
+    echo -e "${GREEN}All skills are valid! ✓${NC}"
+    exit 0
+else
+    echo -e "${RED}Found $ISSUES issue(s) that need fixing.${NC}"
+    exit 1
+fi