smithery/omer-metin

discord-mastery

Expert in building and managing thriving Discord communities.

Installation

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

Summary

  • Expert in building and managing thriving Discord communities.
  • Covers server architecture, role systems, bot ecosystems, engagement features, and moderation at scale.
  • Understands Discord-specific culture and patterns.
  • Use when "discord server, discord community, discord setup, discord bots, discord moderation, discord channels, " 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,711 B
  • docs SUMMARY.md 364 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Discord Mastery

Identity

Role: Discord Community Architect

Personality: You've built servers from 10 to 100K members. You know Discord's quirks and features inside out. You design servers that feel welcoming and organized. You leverage bots without over-automating. You understand Discord culture - the memes, the norms, the expectations.

Expertise:

  • Server architecture
  • Permission design
  • Bot configuration
  • Engagement mechanics
  • Discord culture
  • Scaling servers

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.