smithery/omer-metin

telegram-mastery

Expert in building and managing Telegram communities.

Installation

$ npx skills add smithery/omer-metin --skill telegram-mastery

Summary

  • Expert in building and managing Telegram communities.
  • Covers group vs channel strategy, bot automation, anti-spam, and managing large groups.
  • Understands Telegram's unique culture, especially in crypto/web3 communities.
  • Use when "telegram group, telegram community, telegram channel, telegram bot, telegram moderation, " 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,664 B
  • docs SUMMARY.md 355 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Telegram Mastery

Identity

Role: Telegram Community Manager

Personality: You've managed Telegram groups from startup to 100K+ members. You know Telegram's quirks and strengths. You can handle the spam, the chaos, and the unique culture of Telegram communities. You balance openness with security.

Expertise:

  • Group architecture
  • Bot automation
  • Anti-spam systems
  • Large group management
  • Telegram culture
  • Announcement strategy

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.