Skool Post

---
name: skool-post
description: "Generate a Skool community post and publish via Playwright. Use when: creating Skool content. Triggers on: skool, skool post, community post, write a skool post."
---

# Skool Community Post

Generate a peer-to-peer community post for Skool — more casual than LinkedIn, bullet/list heavy, ends with a specific discussion prompt.

## Prerequisites

**Publishing uses Playwright MCP (`mcp__playwright__*`) — this is the ONLY method.**
Do NOT use Chrome extension tools (`mcp__claude-in-chrome__*`).

1. Verify Playwright MCP is connected (`mcp__playwright__browser_navigate` available)
2. User must be logged into Skool in the Playwright-controlled browser
3. If Playwright MCP unavailable, fall back to saving as markdown

---

## Workflow

### Step 1: Source Content

Ask the user:
- **Option A: From existing content** → ask which folder in `{{CONTENT_DIR}}/`, then read relevant files
- **Option B: From scratch** → ask for topic, key points, any relevant experience
- **Which Skool community?** → get the community URL (e.g., `https://www.skool.com/community-name`)

### Step 2: Load Context

- Read `{{PROFILE_PATH}}` — identity, voice, experience

### Step 3: Draft Post

**Title:** Clear, specific. Not clickbait. What would make YOU click in a community feed?
- GOOD: "3 things I changed about my cold email stack this month"
- BAD: "Game-changing insights about email"

**Body (300-800 words):**
- Peer-to-peer tone — you're posting in a group of smart operators, not broadcasting
- Bullet/list heavy — easy to scan
- Practical and specific — what did you do, what happened, what would you recommend
- Can be: lesson learned, framework share, tool comparison, experiment results, question to the group
- More casual than LinkedIn — contractions, shorter sentences, less polished

**Discussion prompt (NON-NEGOTIABLE — must be specific, not generic):**
- GOOD: "What's one tool you've replaced with AI in the last 90 days? I'll start — I replaced my entire enrichment workflow with Clay + Claude."
- GOOD: "Anyone else notice reply rates dropping on LinkedIn InMails? Seeing 3% vs 8% six months ago. What's working for you instead?"
- BAD: "What do you think?"
- BAD: "Let me know your thoughts!"
- BAD: "Agree or disagree?"

**NON-NEGOTIABLE rules:**
- Humanizer pass - scan for and fix AI writing patterns (see `humanizer` skill): AI vocabulary, significance inflation, filler phrases, hedging, copula avoidance, promotional language, generic conclusions.
- No false-contrast filler
- No revenue flex
- No em dashes (—) anywhere in content. Use regular dashes (-), commas, periods, or restructure. Em dashes are an obvious AI writing tell.
- Not promotional - this is a community, not your blog
- Discussion prompt must be specific enough that someone could answer in one sentence
- Match {{YOUR_NAME}}'s voice: direct, helpful, no fluff

### Step 4: User Review

Display the full post:

```
TITLE: [title]

[Full post body]

---
Discussion prompt quality check:
- Specific? [Yes/No]
- Answerable in one sentence? [Yes/No]
- Invites experience-sharing? [Yes/No]

Word count: [X]
```

Ask: **"Approve / Edit / Regenerate?"**

### Step 5: Publish via Playwright

1. `browser_navigate` → user's Skool community URL
2. `browser_snapshot` → confirm logged in and community page loaded
3. `browser_click` → "Create a post" or new post button
4. `browser_snapshot` → confirm post editor
5. `browser_click` → title field → `browser_type` → post title
6. `browser_click` → body field → `browser_type` → post body
7. `browser_snapshot` → verify content
8. `browser_click` → "Post" or publish button
9. `browser_snapshot` → verify posted successfully

**Fallback:** Save to file, display copy-ready output.

### Step 6: Save Output

Save as `skool-post.md` in the source content folder or ask user where to save.

```markdown
# Skool Post — [Topic]

**Community:** [community name/URL]
**Status:** [Posted / Ready for manual posting]
**Date:** [YYYY-MM-DD]

---

## [Title]

[Full post body including discussion prompt]
```