Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Design, secure, and optimize Discord servers with audits, prioritized fixes, role management, onboarding, moderation, engagement systems, and data-driven gro...
Design, secure, and optimize Discord servers with audits, prioritized fixes, role management, onboarding, moderation, engagement systems, and data-driven gro...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Use this skill to turn a Discord server into a high-signal, well-moderated, growth-ready community.
Use when the user asks to: Set up a new Discord server properly Improve moderation/safety Build cleaner channel + role structure Increase engagement/retention Audit a messy server and create a fix plan
Donβt use this for: One-off Discord message sends/reactions only (use discord skill) Non-Discord community platforms Bot-specific coding/hosting implementation (use coding workflow)
Always produce these 3 deliverables: Server Audit Scorecard (0-100 with category scores) Priority Fix Plan (Now / Next / Later) Execution Checklist (step-by-step settings/actions)
Safety first, growth second Lock down abuse vectors before growth pushes. Least privilege always Give members/mods only what they need, no more. Onboarding is product design First 5 minutes determines retention. Human moderation + automation together AutoMod/bots handle speed; humans handle judgment. Measure, then iterate Use Insights and behavior data to decide changes.
Enable Community features. Enable AutoMod (keyword/spam/mention abuse filters). Use higher verification level for public servers. Require 2FA for moderation roles. Remove @everyone ability to mass mention. Create a private #mod-logs and #incident-room.
Keep a clean hierarchy: Owner > Admin > Mod > Helper > Member > New/Unverified. Avoid permission overlap chaos (few roles, clear job boundaries). Never hand out Administrator unless absolutely necessary. Keep bot roles scoped to needed permissions only.
Configure welcome + rules + clear first action (βStart hereβ, βIntroduce yourselfβ). Keep visible channels minimal for new users. Use concise channel names and category grouping. Make verification instructions obvious and one-path.
Build 3 core activity loops: Daily discussion prompt Weekly event (AMA, demo, challenge) Recognition loop (wins, shoutouts, roles) Maintain announcement/value channels users check repeatedly. Use Insights to evaluate activation + retention changes.
Use this exact sequence.
Score each 0-20: Security Permission hygiene Onboarding clarity Moderation operations Engagement loops Output: total /100 + top 5 risks.
Apply anti-raid + AutoMod + verification + 2FA baseline. Lock risky perms (@everyone, unmanaged bot perms, excessive admin).
Rebuild role map around least privilege. Document each role: purpose, grants, owner.
Redesign onboarding path for first-message success. Add one clear CTA channel for newcomers.
Launch weekly cadence (events + content beats). Create community rituals and recognition.
Track metrics for 2 weeks and adjust: Join β first message conversion D7 retention Moderation incidents/week Message quality in target channels
Security: X/20 Permissions: X/20 Onboarding: X/20 Moderation Ops: X/20 Engagement: X/20 Total: X/100 Top Risks: ... ... ...
...
...
...
Enable Community + safety features Configure AutoMod rules Set verification level + 2FA for mods Refactor roles and permissions Simplify onboarding channels Create mod logging + incident channels Launch weekly engagement cadence Review Insights after 14 days
#start-here #rules #announcements #roles
#introductions #general #wins #resources
#events #event-chat
#mod-chat #mod-logs #incident-room #staff-notes
Too many channels too early (overwhelm) Too many roles with random perms No verification gate on public invites No incident playbook for raids No recurring events/rituals Measuring vanity metrics only (member count) vs behavior metrics
Discord Safety: Auto moderation in Discord https://discord.com/safety/auto-moderation-in-discord Discord Community: Using Insights to Improve Community Growth and Engagement https://discord.com/community/using-insights-to-improve-community-growth-engagement Discord Support (raid prevention / roles docs surfaced in research): https://support.discord.com/hc/en-us/articles/10989121220631-How-to-Protect-Your-Server-from-Raids-101 https://support.discord.com/hc/en-us/articles/214836687-Discord-Roles-and-Permissions Note: Some Discord support pages are Cloudflare-protected for automated fetchers; validate in browser when needed.
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Largest current source with strong distribution and engagement signals.