Docs

Moderation

Jail, mute variants, bans, and cases. Do basic setup before punishing members. Pair with Antinuke so staff action rates stay limited.

Overview

Moderation needs roles and channels Skill can manage. Hierarchy matters: Skill’s role must sit above jail/mute roles and the members you moderate.

Setup

;setup — moderation setup wizard (jail / mute roles and related channels)
;setup sync — re-apply jail/mute permissions on current channels

You can also use Quick setup on a server in the dashboard.

Jail

Jail restricts a member to the jail channel (similar to a hard mute across the server).

;jail @user reason
;unjail @user
;jaillist — currently jailed members

Mute

;mute @user 10m reason — role-based mute (separate from Discord timeout)
;unmute @user
;imute @user / ;iunmute — block attachments/embeds
;rmute @user / ;runmute — block reactions
;hardmute @user — persistent mute (re-applies if the role is removed)

Ban & kick

;ban @user reason · ;unban userId
;tempban @user 7d reason
;hardban @user — re-ban if someone unbans them
;kick @user reason

Staff roles

Mark staff so exemptions and punishments like stripstaff know who is staff. Use the dashboard or staff-role settings in the bot.

Dashboard

  • Cases — search recorded actions
  • Audit log — who changed settings on the website
  • Quick setup — jail, mute, logging in one flow

Common issues

  • Can’t jail/mute — Skill’s role is below the jail/mute role or the target.
  • Mute does nothing — mute role missing channel permission overwrites.
  • Run ;setup sync after adding many new channels.

Commands: Moderation.