Viralz content-creation skill — Claude.ai pack

Bug note: Claude.ai chat/Projects reject .md and .zip uploads.
Upload this .txt (or the individual .txt files) under Project → Files,
or attach it in a chat. Keep connecting Viral MCP in Claude Connectors.

For Cursor / Claude Code / Hermes, prefer the .md skill folder or the .zip.
===== SKILL.md =====

---
name: viralz-content-creation
description: >-
  Creates LinkedIn content the Viralz way: load gold/bronze bracket patterns, ICP and
  company context, writing style, choose user idea vs Viralz ideas, generate visual
  (infographic or slider) first, then write the post, then QA against best practices.
  Use when drafting LinkedIn posts, content ideas, carousels, infographics, or when
  the user mentions Viralz, Viral MCP, brackets, ICP, or LinkedIn content. When the
  user says "use the Viral MCP", run MCP onboarding first (content design, meetings,
  podcasts).
metadata:
  author: viralz
  version: "1.1.0"
  organization: Viralz
---

# Viralz content creation

Ship LinkedIn posts that steal **gold** patterns, avoid **bronze** habits, sound like the user, and hit their ICP — using the Viral MCP whenever it is available.

**Claude.ai note:** Upload the `.txt` pack from `/skills` (`viralz-content-creation-for-claude.txt`). Claude.ai rejects `.md` and `.zip` file uploads.

## MCP onboarding (when the user says “use the Viral MCP”)

Ask once per session before pulling specialty skills:

### 1. Content design

> Do you want to use the **content design skill and templates from Viral MCP**, or your **own** ones?

- **Viral** → `import_content_design_skill` / templates + this skill’s visual pipeline.
- **Own** → follow their skill/templates; still load ICP / voice / gold / bronze from Viral MCP.

### 2. Meetings

> Do you use **Fireflies**, **Fathom** meeting transcriber, or **other**?

- **Fireflies / Fathom / other external** → **skip** Meeting ↔ Content (`import_meeting_content_skill`). Do not push that skill.
- Only offer meeting↔content if they are not on an external transcriber (or they explicitly ask).

### 3. Podcasts

> Do you make podcasts? **Yes / No**

- **No** → do not push Podcast → Content.
- **Yes** → ask if they want the **podcast → content skill**. If yes → `import_podcast_content_skill` and follow `podcast-2-content.md` (transcript → interesting moments → ICP filter → Viral context → content skills).

Also call `get_mcp_agent_readme` — it contains the same onboarding rules.

## Non-negotiable: Viral MCP for LinkedIn

If you are making LinkedIn content and the Viral (`viral`) MCP server is connected, **use it**. Do not invent ICP, vocabulary, brackets, or metrics.

Call `get_mcp_agent_readme` or `get_app_overview` first (after onboarding if they asked to use Viral MCP).

## Workflow checklist

Copy and track:

```
Viralz content run:
- [ ] 1. Bracket best practices (gold) + negative patterns (bronze)
- [ ] 2. ICP + company / business context
- [ ] 3. Writing style (Your voice + style guide)
- [ ] 4. Idea source: user idea OR Viralz ideal ideas
- [ ] 5. Visual FIRST (infographic OR slider/carousel)
- [ ] 6. Write the post
- [ ] 7. QA against all best practices (+ simulate_draft)
```

---

### Step 1 — Bracket analysis: steal gold, avoid bronze

**MCP tools:** `get_bracket_synthesis`, `get_bracket_analyses`, `get_user_comparison`, optionally `get_bracket_insights`

Load and keep in working memory:

| Source | Steal / use | Never repeat |
|--------|-------------|--------------|
| **Gold** | hookPattern, rehookPattern, viralPatterns, format/angle patterns | — |
| **Silver** | adequate patterns only (do not copy wholesale) | — |
| **Bronze** | — | self-sabotage habits |
| **User comparison** | `goodPractices`, `goldGaps` | `badPractices`, `bronzeOverlap` |

Patterns UI labels map to: **Start doing** = good practices · **Stop doing** = bad practices · **Fix next** = gaps/overlap.

Details: [references/bracket-patterns.md](references/bracket-patterns.md)

If no research run exists: tell the user to run Bracket research in Viral, or call `start_creator_research` (subscription), then poll `get_creator_research_run`.

---

### Step 2 — ICP and company context

**MCP tools:** `get_icp`, `get_business_context` (preferred full pack)

Must capture:

- Buyer: title, industry, company size, core problem, niche/themes
- Business: service/product, industry, model
- Uploaded markdown: `businessContextMarkdown` when present
- Brand style from website: colors/fonts in `styleContext` (for visuals)

Do not draft for a generic “LinkedIn audience.” One ICP per post.

---

### Step 3 — Writing style

**MCP tools:** `get_user_vocabulary` (use `promptReady`), `get_business_context` for `styleGuideMarkdown`

Rules:

- Reuse their frequent words and signature phrases naturally — do not keyword-stuff
- Match typical post length (`avg words/post`)
- Structure like them: opening length, mid-post pacing, closing ask
- Never invent a generic influencer voice

---

### Step 4 — Idea source (branch)

Ask (or infer) which path:

**A. User’s own idea**  
User supplies topic/angle. Still ground it in gold hooks, ICP, voice, and bronze avoidance. Optionally compare to `get_generated_content_ideas` / `list_saved_content_ideas` for fit.

**B. Ideal Viralz idea**  
Use Viralz research:

```
get_icp + get_user_vocabulary
→ generate_content_ideas   # or get_generated_content_ideas / list_saved_content_ideas
→ pick one idea (format, hook, rehook, visual, postStructure, cta, goldPatternStolen)
```

Prefer ideas that cite a concrete `goldPatternStolen` and a clear 3-P pillar (Personality / Problem / Proof).

---

### Step 5 — Visual FIRST (infographic or slider)

**Always produce the visual before the post body.**

Choose:

| Format | When |
|--------|------|
| **Infographic** (IMAGE) | One insight readable in ~3 seconds: single-stat, 2×2, funnel, before/after, timeline, annotated screenshot |
| **Slider / carousel** (DOCUMENT) | Multi-beat story: hook card → 3–7 teaching cards → CTA card |

From `get_business_context` / website style: use **their brand colors and fonts**. Nick Broekma lens: complex idea → clear visual in three seconds.

Output a concrete visual brief (and generate the asset if the agent can create images/PDF). See [references/visual-formats.md](references/visual-formats.md).

Viral MCP does not render pixels — describe the visual precisely, then use the agent’s image/design tools (or hand the brief to the user).

---

### Step 6 — Write the post

Draft in this order:

1. **Hook** — steal a concrete gold hook mechanism (tension, stake, specificity, proof-first)
2. **Rehook** (line 2) — open loop; never throat-clearing
3. **Body** — 4–7 beats from `postStructure`, in their voice, for one ICP
4. **CTA** — ICP-specific conversation starter (not “Thoughts?” / “Follow me”)

Creator lenses (one per idea when using Viralz ideas): Hormozi, Herubel, Chris James (3-P), Lara Acosta, Jasmin Ali (rehook), Nick Broekma (visual), Chris Do, Louis Grenier.

Banned phrases: [references/anti-slop.md](references/anti-slop.md)

---

### Step 7 — QA (must pass before delivery)

Run [references/post-checklist.md](references/post-checklist.md). Then:

```
simulate_draft   # Skeptical Prospect / Skimmer / Ideal Client
```

Iterate until readiness is solid. Only then present final visual + post.

---

## Quick MCP sequence

```
get_app_overview
→ get_bracket_synthesis + get_user_comparison
→ get_icp + get_business_context
→ get_user_vocabulary
→ (B) generate_content_ideas / get_generated_content_ideas  OR  (A) use user idea
→ VISUAL brief/asset (infographic | slider)
→ draft post
→ simulate_draft + checklist QA
```

## What you must not do

- Skip Viral MCP when it is connected and the task is LinkedIn content
- Fabricate brackets, ICP, vocabulary, or metrics when tools return empty
- Write the post before the visual
- Use bronze / badPractices patterns
- End with generic engagement-bait CTAs
- Sound like generic LinkedIn AI (see anti-slop list)

===== references/anti-slop.md =====

# Anti-AI-slop — never use in LinkedIn copy

Do not use these words/phrases (or close variants) in hooks, rehooks, body, CTAs, or titles.

## High-frequency bans

game-changer, revolutionary, disrupt/disruptive, unlock/unleash, harness, leverage, synergy, paradigm (shift), ecosystem, landscape, in today's world, at the end of the day, it's no secret, let's dive in, deep dive, without further ado, buckle up, here's the thing, spoiler alert, plot twist, mind-blowing, groundbreaking, cutting-edge, state-of-the-art, best-in-class, world-class, next-level, level up, supercharge, skyrocket, 10x, holistic, robust, seamless, streamline, optimize, empower, transformative, thought leader/leadership, move the needle, circle back, touch base, bandwidth, think outside the box, win-win, delve, tapestry, plethora, myriad, multifaceted, nuanced, pivotal, paramount, resonate, navigate, journey, embark, foster, cultivate, spearhead, elevate, amplify, actionable insights, key takeaways, pro tip, hack/hacks, secret sauce, blueprint, playbook, framework, roadmap, masterclass, cheat sheet, ultimate/definitive/comprehensive guide, in conclusion, bottom line, the reality/truth is, cut through the noise, silver bullet, hot take, unpopular opinion, brutal/hard truth, food for thought, picture this, what if I told you, did you know, fun fact

## Engagement-bait bans

follow me / follow for more, subscribe, like and share, comment below, thoughts?, agree?, what do you think?, does this resonate?, tag someone, share if you agree, save this post, DM me, link in bio, stay tuned, excited/thrilled/proud to announce, humbled/honored/grateful (as filler)

## Structure bans

- Em dashes as filler
- Exactly five generic numbered lessons
- “In today's fast-paced world…”
- Symmetrical blog-outline paragraphs that do not sound like the user

## Allowed CTA shape

One short, ICP-specific invitation to a real conversation, e.g. reply with a metric, situation, or constraint — never broadcast engagement bait.

===== references/bracket-patterns.md =====

# Bracket patterns — steal gold, avoid bronze

## Gold (best practices)

Steal mechanisms, not copy-paste posts:

- **Hooks** — tension, stake, specificity, proof-first, number contrast
- **Rehooks** — line two keeps the open loop
- **Formats** — text vs document/carousel vs image that actually travel in the niche
- **Angles** — how gold creators frame the same topic for one clear buyer
- **Why it travels** — use `whyItWorks` / viralPatterns from gold analysis

MCP: `get_bracket_analyses` (gold), `get_bracket_synthesis`, gold fields on ideas (`goldPatternStolen`).

## Silver

Adequate patterns. Borrow lightly. Do not treat silver as the ceiling.

## Bronze (negative patterns)

Never reproduce:

- Vague claims without receipts
- Generic engagement bait
- Throat-clearing openers / wasted line two
- Self-promo without teaching
- Habits listed in `badPractices` and `bronzeOverlap` from `get_user_comparison`

## User comparison mapping

From `get_user_comparison`:

| Field | Meaning | Action |
|-------|---------|--------|
| `goodPractices` | Gold structures they are not using yet | **Start doing** |
| `badPractices` | Habits shared with bronze | **Stop doing** |
| `goldGaps` | Missing gold moves | **Fix next** |
| `bronzeOverlap` | Where they still look bronze | Remove from drafts |

## How to apply in a draft

1. Name the gold hook mechanism you are stealing (one sentence).
2. Name the bronze habit you are deliberately avoiding (one sentence).
3. Confirm the post is for one ICP only.
4. If the draft drifts toward a `badPractices` item — rewrite before delivery.

===== references/post-checklist.md =====

# Post QA checklist

Run after the visual and draft exist. Fix failures before delivery.

## Bracket & strategy

- [ ] Steals a named **gold** hook/mechanism (not a vague topic paraphrase)
- [ ] Line 2 is a real **rehook** (open loop), not context-setting
- [ ] Avoids every relevant **bronze** / `badPractices` / `bronzeOverlap` habit
- [ ] Fits one 3-P pillar job: Personality, Problem, or Proof
- [ ] Angle is specific enough that Louis Grenier–style originality would approve (not recycled platitudes)

## ICP & business

- [ ] Clearly for **one** ICP (title/problem recognizable)
- [ ] Product/company context is accurate when mentioned (from `get_business_context`)
- [ ] CTA is an ICP-specific conversation starter

## Voice & style

- [ ] Sounds like **this user** (vocabulary + cadence + length)
- [ ] No keyword-stuffed word cloud
- [ ] Style guide markdown respected when present

## Visual

- [ ] Visual (infographic **or** slider) was defined/generated **before** the post
- [ ] Visual readable in ~3 seconds; uses brand colors when known
- [ ] Post and visual tell the same story (hook aligns with card 1 / infographic headline)

## Anti-slop & craft

- [ ] No banned AI-slop phrases ([anti-slop.md](anti-slop.md))
- [ ] No generic CTAs (follow me, thoughts?, like and share, …)
- [ ] Hook would stop a skimmer; body earns the CTA

## Viral MCP stress-test

- [ ] `simulate_draft` run (Skeptical Prospect / Skimmer / Ideal Client)
- [ ] Revisions applied until readiness is solid

## Delivery package

Present to the user:

1. Visual asset or brief  
2. Final post text (hook → rehook → body → CTA)  
3. One-line note: gold pattern stolen + bronze habit avoided

===== references/visual-formats.md =====

# Visual formats — infographic or slider

Produce the visual **before** the LinkedIn post text.

Pull brand colors/fonts from `get_business_context` → website `styleContext` (or style guide markdown).

## Infographic (IMAGE)

Use when one idea can be understood in ~3 seconds.

Archetypes:

- Single-stat card
- Before / after
- 2×2 matrix
- Funnel or steps (max 4)
- Timeline
- Annotated screenshot
- Checklist (short)

Brief must include:

1. Format archetype  
2. Exact headline on the visual (≤ ~8 words)  
3. 1–5 data/label blocks  
4. Brand colors (hex if known) + font mood  
5. What the skimmer understands in 3 seconds  

## Slider / carousel (DOCUMENT)

Use when the story needs multiple beats.

Suggested card stack:

1. Hook card (same tension as post hook)  
2. Context / problem card  
3. 2–5 teaching or proof cards (one idea each)  
4. CTA card (ICP-specific ask — not “follow me”)  

Brief must include per-card: headline, 1–2 lines body, layout note.

## Nick Broekma rule

Complex idea → redraw as a Pinterest-clear infographic or carousel in **their** colors. No cluttered dashboards. No tiny text walls.

## Agent capabilities

- If you can generate images/PDF: build the asset from the brief, then write the post that references it.
- If you cannot: deliver the brief as the visual deliverable, then write the post.
