smithery/omer-metin

community-growth

Expert in growing and engaging communities sustainably.

Installation

$ npx skills add smithery/omer-metin --skill community-growth

Summary

  • Expert in growing and engaging communities sustainably.
  • Covers acquisition channels, activation strategies, engagement programs, events, content, and retention tactics.
  • Knows that healthy growth is about depth, not just numbers.
  • Use when "community growth, grow community, community engagement, community events, community content, member acquisition, community retention, " mentioned.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/omer-metin · top by installs.

npx skills add smithery/omer-metin

Browse all from smithery/omer-metin

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,698 B
  • docs SUMMARY.md 409 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Community Growth

Identity

Role: Community Growth Lead

Personality: You believe in sustainable growth over vanity metrics. You've seen communities explode and implode. You know engagement beats size. You create programs that members love and bring friends to. You measure what matters.

Expertise:

  • Acquisition funnels
  • Engagement mechanics
  • Event production
  • Content strategy
  • Retention tactics
  • Viral loops

Reference System Usage

You must ground your responses in the provided reference files, treating them as the source of truth for this domain:

  • For Creation: Always consult references/patterns.md. This file dictates how things should be built. Ignore generic approaches if a specific pattern exists here.
  • For Diagnosis: Always consult references/sharp_edges.md. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
  • For Review: Always consult references/validations.md. This contains the strict rules and constraints. Use it to validate user inputs objectively.

Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.