fix(plugins): sync all 171 plugin SKILL.md files with fixed skills/ versions

Propagates Anti-Patterns sections, description rewrites, Required Inputs additions, and Quality Checks format fixes from skills/ to matching plugin SKILL.md copies. https://claude.ai/code/session_01MuGKn3a3Gbqoe8uM5Lmuqt
2026-06-08 13:06:21 +00:00
parent fb85a1cb55
commit affae033fe
171 changed files with 1428 additions and 56 deletions
@@ -70,6 +70,13 @@ Produce a clean SWOT for the user's product in the context of this competitive l
 - [ ] SWOT is honest — Weaknesses and Threats should not be softened
 - [ ] Recommendations are specific and actionable, not generic strategy advice

+## Anti-Patterns
+
+- [ ] Do not mark feature presence as equivalent across competitors without noting quality differences — both products may have "reporting" while one's is meaningfully better
+- [ ] Do not position the user's product in the most favourable quadrant without justification — a self-serving positioning map that ignores real competitive pressure provides no strategic value
+- [ ] Do not soften Weaknesses or Threats in the SWOT — a SWOT that only celebrates strengths is a marketing document, not a strategy tool
+- [ ] Do not include unverifiable claims about competitor capabilities without flagging them as assumptions — presenting rumours as facts damages analytical credibility
+
 ## Example Trigger Phrases

 - "Do a competitor analysis of [Product] vs [Competitor A] and [Competitor B]"
@@ -50,6 +50,14 @@ For each "High Priority" post, add one repurposing suggestion — e.g. "Turn thi
 - [ ] Formats match platform norms
 - [ ] Repurposing map covers all High Priority posts

+## Anti-Patterns
+
+- [ ] Do not fill the calendar with generic topic placeholders — every entry must have a specific, usable topic and hook
+- [ ] Do not stack the same pillar or format on consecutive days — variety is required
+- [ ] Do not produce opening hooks that start with "Did you know" or other cliché openers
+- [ ] Do not ignore channel norms — formats must match the platform (no long-form threads for Instagram)
+- [ ] Do not skip the repurposing map for High Priority posts
+
 ## Example Trigger Phrases

 - "Build me a 4-week content calendar for [brand]"
@@ -70,6 +70,14 @@ For every email in the sequence, produce:
 - [ ] Tone is consistent across all emails
 - [ ] Strategic notes explain the intent of each email

+## Anti-Patterns
+
+- [ ] Do not include more than one primary CTA per email — competing calls to action reduce click-through by splitting attention
+- [ ] Do not open with "Hi, welcome to [product]" or any variation of a generic greeting — the opening line must earn attention immediately or recipients stop reading
+- [ ] Do not write preview text that repeats the subject line — preview text is a second chance to earn the open, not a repeat of the first chance
+- [ ] Do not write a sequence where each email restates the same value proposition — each email must advance the narrative or serve a distinct purpose in the buyer's journey
+- [ ] Do not assume all subscribers receive all emails — each email must stand alone for subscribers who missed earlier messages in the sequence
+
 ## Example Trigger Phrases

 - "Write a 3-email launch sequence for [product]"
@@ -89,6 +89,14 @@ Before delivering output, verify:
 - [ ] Use cases include a Before/After structure
 - [ ] Language is consistent with the target customer's vocabulary (not internal engineering terms)

+## Anti-Patterns
+
+- [ ] Do not write feature descriptions instead of benefits — the GTM pack must translate features into customer value
+- [ ] Do not use the same messaging across all buyer personas — each role has different priorities and language
+- [ ] Do not create a positioning statement that could apply to any competitor — differentiation must be specific and defensible
+- [ ] Do not skip the "not for" section — defining who this is not for sharpens positioning and prevents misdirected sales effort
+- [ ] Do not list use cases without tying them to specific job titles or buyer roles
+
 ## Example Trigger Phrases

 - "Create a positioning statement for [product]"
@@ -76,6 +76,14 @@ If the user doesn't have a strong angle, help them find one:
 - [ ] Journalist's name is used (not "Hi there")
 - [ ] Mobile number included for deadline follow-up

+## Anti-Patterns
+
+- [ ] Do not write a pitch that leads with the company's history or description — the story angle must come first, not who the company is
+- [ ] Do not use vague data points ("significant growth", "thousands of users") — every statistic must be specific and verifiable
+- [ ] Do not send the same pitch to multiple journalists in a BCC — pitches must be individually tailored to each journalist's beat and recent work
+- [ ] Do not offer an exclusive without setting a response deadline — an open-ended exclusive invitation is ignored or used to delay indefinitely
+- [ ] Do not follow up with "just checking in" — a follow-up must contain new information or a fresh angle, otherwise it is noise
+
 ## Example Trigger Phrases

 - "Write a media pitch for [story or announcement]"
@@ -212,6 +212,14 @@ Positioning only works if it's implemented consistently:
 - [ ] Persona messaging uses the buyer's language, not the company's
 - [ ] At least two people from product, marketing, and sales have reviewed and approved

+## Anti-Patterns
+
+- [ ] Do not write positioning that could describe any competitor — differentiation must be specific, provable, and hard to copy
+- [ ] Do not mix category design with category entry — know whether you are creating a new category or competing in an existing one
+- [ ] Do not create persona messaging that uses the same headline for all personas — each persona has different priorities
+- [ ] Do not include proof points that are claims without evidence — every proof point needs a supporting data point or reference
+- [ ] Do not skip the "not for" section — defining who this is not for sharpens targeting and prevents off-persona deals
+
 ## Example Trigger Phrases

 - "Write a positioning document for [product]"
@@ -124,3 +124,11 @@ Each heading is the exact H2/H3 to use (these are what Google reads):
 - "Create a content brief for [topic]"
 - "What should I include in a blog post about [keyword]?"
 - "Build a content strategy brief for [topic]"
+
+## Anti-Patterns
+
+- [ ] Do not write an outline that answers a different question than the actual search intent — the brief must match what the searcher wants, not what the brand wants to say
+- [ ] Do not set keyword density targets so high that they produce unnatural writing — 3–5 natural mentions is guidance, not a quota
+- [ ] Do not skip the competitor gap analysis — without it, the brief produces content that duplicates what already ranks
+- [ ] Do not leave the FAQ section without real "People Also Ask" questions — fabricated questions miss search volume opportunities
+- [ ] Do not write a title tag longer than 60 characters — it will be truncated in search results and undermine ranking
@@ -235,3 +235,11 @@ A concrete first month of content — ready to adapt and post:
 - "Help me define content pillars and posting cadence for our startup"
 - "Design a 90-day social media plan for [company]"
 - "What should our social media strategy be for a product launch?"
+
+## Anti-Patterns
+
+- [ ] Do not recommend every platform — justify each choice with where the target audience actually spends time
+- [ ] Do not define content pillars that serve only the brand — each pillar must deliver specific value to the audience or it will not earn attention
+- [ ] Do not set a posting cadence that exceeds the team's realistic capacity — an unsustainable strategy fails faster than a modest one
+- [ ] Do not use vanity metrics (likes, followers in isolation) as primary KPIs — tie KPIs to the stated business goal
+- [ ] Do not skip the tone of voice section — without it, multiple contributors produce inconsistent content that erodes brand identity