Discord Mastery

Name: Discord Mastery
Author: omer-metin

omer-metin/skills-for-antigravity

27 installs
122 repo stars
Updated January 22, 2026
omer-metin/skills-for-antigravity

Helps with ai & agent building tasks during AI-assisted development.

About

discord-mastery is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted coding.

discord-mastery
AI & Agent Building
AI-coding skill

Discord Mastery by the numbers

27 all-time installs (skills.sh)
Ranked #9,601 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
Data as of Aug 5, 2026 (Skillselion catalog sync)

npx skills add https://github.com/omer-metin/skills-for-antigravity --skill discord-mastery

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

[![Listed on Skillselion](https://skillselion.com/badge/skills/omer-metin/skills-for-antigravity/discord-mastery.svg)](https://skillselion.com/skills/omer-metin/skills-for-antigravity/discord-mastery)

Installs	27
repo stars	★ 122
Last updated	January 22, 2026
Repository	omer-metin/skills-for-antigravity ↗

What it does

Helps with ai & agent building tasks during AI-assisted development.

Files

SKILL.mdMarkdownGitHub ↗

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.

Discord Mastery

Patterns

---

Name

Server Architecture

Description

Designing organized, scalable server structure

When To Use

When setting up or restructuring a Discord server

Implementation

Discord Server Architecture

Category Structure

    WELCOME
    ├── #rules
    ├── #introductions
    ├── #start-here
    └── #announcements
    
    COMMUNITY
    ├── #general
    ├── #off-topic
    ├── #wins
    └── #help
    
    TOPIC SPECIFIC (varies)
    ├── #topic-1
    ├── #topic-2
    └── #topic-3
    
    RESOURCES
    ├── #resources
    ├── #links
    └── #faq
    
    VOICE
    ├── General VC
    ├── Focus Room
    └── Events Stage
    
    MOD ONLY
    ├── #mod-chat
    ├── #mod-logs
    └── #escalations

Channel Count Guidelines

Server Size	Max Channels	Categories
< 500	10-15	3-4
500-2K	15-25	4-6
2K-10K	25-40	6-8
10K+	40-60	8-12

Common Mistakes

Too many channels (cognitive overload)
No clear purpose per channel
Buried important channels
Inconsistent naming

---

Name

Role System Design

Description

Permission-based role hierarchy

When To Use

When designing access control

Implementation

Role Hierarchy

Standard Roles (Top to Bottom)

    ADMIN (Full perms)
    ├── Lead Moderator
    ├── Senior Moderator
    ├── Moderator
    ├── Trial Moderator
    ├── VIP/OG
    ├── Active Member
    ├── Verified
    └── New Member

Role Assignment

Role	How Earned	Perks
Verified	Complete onboarding	Basic access
Active	Time + activity	More channels
VIP	Contribution	Special access
Mod	Application/invite	Mod tools

Permission Best Practices

Start restrictive, grant permissions up
Use role hierarchy properly
Avoid @everyone permissions
Regular permission audits

---

Name

Bot Ecosystem

Description

Strategic bot deployment

When To Use

When setting up or optimizing bots

Implementation

Bot Strategy

Essential Bots

Purpose	Options	Notes
Moderation	Carl-bot, Wick, Dyno	Pick one main
Welcome/Roles	Carl-bot, MEE6	Reaction roles
Leveling	MEE6, Tatsu, Arcane	Optional
Tickets	Ticket Tool, Carl-bot	For support
Custom	Custom bot	For unique needs

Configuration Principles

One primary moderation bot
Avoid duplicate functionality
Test before deploying
Document all bot settings
Regular bot audits

Automod Setup

Rule	Action	Notes
Spam	Delete + warn	Link cooldown
Slurs	Delete + timeout	Use blocklist
Raids	Lockdown	Mention spam
Scams	Delete + ban	Crypto scams

Anti-Patterns

---

Name

Channel Sprawl

Description

Too many channels killing activity

Why Bad

Activity diluted across channels. Members don't know where to post. Dead channels look bad.

What To Do Instead

Start minimal, add only when needed. Archive unused channels. Use threads for sub-topics. Quality over quantity.

---

Name

Bot Overload

Description

Too many bots cluttering server

Why Bad

Confusing for members. Overlapping functionality. Bot spam in channels. Maintenance nightmare.

What To Do Instead

Audit bots quarterly. One bot per function. Remove unused bots. Document configurations.

---

Name

Over-Gamification

Description

Excessive XP/leveling focus

Why Bad

Members game the system. Quantity over quality. XP farming behavior. Loses meaning.

What To Do Instead

Subtle gamification. Meaningful levels (access, not just status). Quality-based, not just activity.

Discord Mastery - Sharp Edges

Server Raids

Id

server-raids

Summary

Coordinated attack on server

Severity

high

Situation

Multiple accounts joining and spamming/causing chaos

Why

Server linked publicly. No verification gate. Slow mod response.

Solution

Raid Prevention & Response

Prevention

Enable verification level (Medium+)
Use verification bot/captcha
Limit new member permissions
Hide sensitive channels from new members

Detection

Unusual join spike
New accounts posting immediately
Same/similar messages
Mention spam

Response Protocol

1. IMMEDIATE: Enable slowmode (all channels) 2. IF SEVERE: Lock server (disable join) 3. Ban raid accounts 4. Review logs for patterns 5. Report to Discord Trust & Safety

Automod Settings for Raids

  - Block mass mentions (5+ in message)
  - Block new account spam (< 1 day old)
  - Enable anti-raid mode in modbot

Symptoms

Spam flood
Mass joins
Chaos in channels
Members panicking

Detection Pattern

raid|spam|mass join|attack|flooded

Permission Creep

Id

permission-creep

Summary

Permissions granted carelessly over time

Severity

medium

Situation

Too many people with too many permissions

Why

Giving perms to fix quick issues. Not revoking when roles change. No regular audits.

Solution

Permission Hygiene

Audit Checklist

[ ] Who has admin? (Should be 2-3 max)
[ ] Who can ban? (Mods only)
[ ] Who can manage channels? (Leads only)
[ ] Who can @everyone? (Admins only)

Cleanup Process

1. Export current role/perm list 2. Review each elevated role 3. Remove unnecessary permissions 4. Document who has what and why

Prevention

Grant minimum necessary
Document permission grants
Quarterly permission audits
Revoke on role change

Symptoms

Who gave them perms?
Accidental @everyone
Unauthorized changes
Security concerns

Detection Pattern

who has|too many|permission|security

Dead Channel Syndrome

Id

dead-channel-syndrome

Summary

Many channels with no activity

Severity

medium

Situation

Server looks abandoned with empty channels

Why

Created too many channels upfront. Topics that didn't pan out. No archive strategy.

Solution

Channel Health

Activity Audit

Last Message	Action
< 7 days	Healthy
7-30 days	Monitor
30-90 days	Consider archiving
> 90 days	Archive or delete

Archive Process

1. Create "Archive" category (hidden from most) 2. Move dead channels there 3. Or export and delete 4. Announce consolidation

Prevention

Start with fewer channels
Earn channels through demand
Use threads for temp topics
Regular channel reviews

Symptoms

Empty channels
Where is everyone?
Activity in 2-3 channels only
New members confused

Detection Pattern

dead|empty|no one uses|too many channels

Verification Bypass

Id

verification-bypass

Summary

Scammers getting through verification

Severity

high

Situation

Bad actors passing verification and scamming members

Why

Verification too simple. No ongoing monitoring. Scam patterns evolve.

Solution

Anti-Scam Measures

Verification Layers

1. Discord's built-in level (phone/email) 2. Bot captcha (Wick, Captcha.bot) 3. Manual review for suspicious 4. Probation period for new members

Scam Detection

Pattern	Action
DM about crypto	Warn members, ban scammer
"Admin" impersonation	Immediate ban
Fake giveaway links	Delete, ban, report
NFT mint links from new accounts	Delete, ban