Coding

Skool Growth Teardown Poster

Try it

Create public-safe Skool growth teardown posts from validated public community snapshots. Use when generating posts, copy-paste reply packs, consultation CTA...

What it does

Create public-safe Skool growth teardown posts from validated public community snapshots. Use when generating posts, copy-paste reply packs, consultation CTA...

The skill document

Skool Growth Teardown Poster

Use this skill to turn public Skool community growth data into a useful post and opt-in reply pack for a Skool audience.

Inputs

Collect or infer:

  • baseline public snapshot,
  • current public snapshot or official About-page checks,
  • target community URL,
  • desired member goal,
  • desired consultation or lead goal,
  • strongest winner by absolute growth,
  • strongest winner by percent growth,
  • data caveats.

If the source includes private posts, member lists, DMs, emails, paid lessons, cookies, screenshots with names, or hidden community content, stop and replace it with public metadata or aggregate placeholders.

Workflow

  1. Validate the data boundary:
    • allowed: public Discovery cards, public About pages, creator-owned notes, aggregate metrics,
    • blocked: private members, DMs, emails, paid lessons, hidden posts, cookies, session tokens.
  2. Compare baseline and current member counts by slug.
  3. Pick one main winner by absolute member growth.
  4. Mention percent-growth leaders only as a secondary lens.
  5. Explain the mechanism:
    • clear promise,
    • free quick win,
    • outside content engine,
    • visible proof or resources,
    • paid implementation path.
  6. Convert the mechanism into a member action.
  7. Add a comment CTA that asks for opt-in words such as growth map, audit, or paid map.
  8. Add reply scripts for opt-ins.
  9. Add a consultation offer only as a specific diagnostic, not a generic income or growth guarantee.
  10. Add the next post prompt so the community can keep the series moving.
  11. Prepare a final post draft and approval checklist for the community owner. Do not post, comment, or message as part of this skill.

Output

Return:

  • title,
  • main Skool post,
  • pinned comment,
  • 4 to 6 reply templates,
  • inbound-DM script for opted-in people only,
  • paid consultation scope,
  • next 3 to 7 posts,
  • validation caveat.

Guardrails

  • Do not claim "fastest on Skool" without complete platform-wide time series.
  • Prefer "fastest in this measured public candidate set" or "clearest winner by measured absolute growth."
  • Do not promise joins, income, rank, conversion, retention, or revenue.
  • Do not cold-DM people or automate cross-community comment blasting.
  • Do not store private member data, DMs, emails, paid content, credentials, cookies, screenshots with names, or hidden posts.
  • Keep every CTA consent-first and tied to a useful free action.

Related skills

Improve a Skool community's public discovery page for search clarity, trust signals, and free-course activation. Use when the user wants a better Skool name,...

13 installs

Build a free-course trust ladder for Skool communities. Use when the user wants to earn trust in a free or early community through proof, public templates, p...

12 installs

Help a new Skool or online-community creator choose a community topic, name, audience, proof promise, and first 7-day validation challenge using the creator'...

13 installs

Design a public-safe 7-day Skool challenge. Use when the user wants to invite member action, collect comments, produce visible proof, test demand, or turn re...

12 installs

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

14 installs

Build and leverage online communities to drive product growth and brand loyalty. Use when the user wants to create a community strategy, grow a Discord or Slack community, manage a forum or subreddit, build brand advocates, increase word-of-mouth, drive community-led growth, engage users post-signup, or turn customers into evangelists. Trigger phrases: "build a community," "community strategy," "Discord community," "Slack community," "community-led growth," "brand advocates," "user community," "forum strategy," "community engagement," "grow our community," "ambassador program," "community flywheel."

3 installs