Skool Member Activation Concierge

Design public-safe onboarding prompts and weekly concierge actions that help new Skool members make first comments, share first proof, surface blockers, and...

Use this skill when a Skool community needs early engagement, cleaner onboarding, or a repeatable path from new member to useful outcome.

Inputs

Collect or infer:

• community promise,
• new member types,
• first useful action,
• common blocker categories,
• available templates or lessons,
• founder/operator time available each week,
• no-paid-implementation boundary.

Workflow

1. Define the first member action in one sentence.
2. Write a welcome comment template.
3. Write a "where are you now" poll.
4. Write a blocker poll.
5. Write a first-win prompt.
6. Create a 7-day concierge checklist for the operator.
7. Define escalation rules for free proof reviews and future interest-list requests.

Output

Return:

• first action,
• welcome post or comment,
• poll copy,
• first-win prompt,
• 7-day concierge checklist,
• trust escalation rules,
• activation metrics.

Do not automate private DMs or scrape member data. Keep outreach consent-first and based on visible member posts or explicit replies.

Examples

Good public-safe inputs:

• "Write a welcome comment for members who want to audit one repeated task."
• "Create a blocker poll using only visible replies and aggregate counts."

Avoid inputs that require member lists, DMs, hidden posts, paid lessons, credentials, private exports, or screenshots with personal/account details. Use visible posts, explicit replies, synthetic samples, or aggregate counts.

Guardrails

• Do not scrape private communities, member lists, DMs, paid lessons, or hidden pages.
• Do not request, store, transform, or paste credentials, API keys, session cookies, payment data, private exports, or account recovery data.
• Do not promise income, growth, conversion, rank, time saved, health, financial, legal, or education outcomes.
• Do not automate private DMs or off-platform outreach.
• Keep proof reviews free, consent-first, and based on user-submitted or operator-owned artifacts.