Docs

Read the syntax

<value> is required; [value] is optional and may show a default. Don’t type the brackets. Replace example mentions and IDs with real targets. Quote multiword positional arguments; trailing text can contain spaces.

The default prefix is .; administrators can change it. Slash commands use the exact path on each card, with Discord’s named option fields. Aliases apply to prefix commands. A group’s bare prefix command usually becomes its slash overview action—for example .ticket → /ticket overview. For durations, a bare number means minutes; use s, m, h or d for an explicit unit.

Set up your server

1. Skye only remains in owner-authorized servers. Request authorization through support, then invite Skye and review individual permissions and ensure it can view/send in the channels you use. Administrator is not requested.
2. Put Skye’s role above the roles/members it must manage. You also need the required permissions and role position; Skye does not lend you its privileges.
3. Use .features to inspect optional modules. Economy, leveling, giveaways, server options, games, bump reminders, counting, confessions, anti-nuke, anti-raid, logging and VoiceMaster start disabled. Some need setup before .features enable <name>.
4. Open /setup overview for private guided setup, or .serversetup in a staff-only text channel. Reopen it to resume saved progress. Use .help, .commandinfo <name> or the cards below for the command you need. Buttons, confirmations and modals are part of the feature, not separate text commands.

Step-by-step server setup

Open /setup overview for a private wizard. Each page asks about one feature: choose Set up / enable to answer relevant questions, select channels or roles, and enter settings. Keep settings / next preserves existing configuration; Disable feature explicitly switches a supported feature off. Disabled features skip dependent questions. Previous revisits a page; Finish shows saved settings. Reopen the command to resume your saved step; unfinished answers are not saved.

Each operation retains the original command permissions, validation and cooldowns. Anti-nuke owner restrictions still apply. Use .serversetup only in a private staff channel. Ticket setup opens its dedicated customization menu. Advanced options remain available through each feature’s commands and .help.

Common setup sequences

• Tickets: .ticket setup main → select category/support role → .ticket panel main #support.
• Voice rooms: .voicemaster setup → use the generated join-to-create lobby and control panel.
• Economy / XP: .economy enable; .features enable leveling → .levelconfig.
• Role automation: .features enable server_options → configure .serverconfig, .buttonrole or .reactionrole. Cosmetic roles cannot grant private access or moderation authority.
• Security: the server owner runs .antinuke setup #staff-log, reviews .antinuke rules and chooses responses. .antiraid setup #staff-log has separate thresholds. Review actions before enabling them.
• Filtering: .filter add blocked phrase or .filter spam enable → .filter enable. Filtering is configured separately from the optional-module list.
• Community: .confessions setup #confessions, .counting setup #counting, or .bumpreminder setup #bump.
• Logging: .logs setup #staff-log → .logs event messages on if needed. Message events record metadata, not bodies.

Before destructive or private actions

Read confirmation prompts. Cleanup is bounded and rechecks permissions, but deletions can be irreversible. Anti-nuke is reactive and is not a backup. Old ticket channels without ownership records need manual administrator closure.

Sensitive moderation responses use private delivery; use slash commands for private interaction menus. Confessions are anonymous to readers, not the operator. Use slash commands for ephemeral confession/bug-report acknowledgements, and a support ticket for sensitive requests. Never submit credentials. Message lookup and pins must run in the source channel.

If a command does not work

Check the server’s prefix, module setup, your permissions, Skye’s permissions and role order, then the cooldown. Timed-out members and members who cannot send in the channel cannot use Skye to bypass that restriction. Slash visibility can also be restricted in Discord’s Integrations settings. Missing presence data, unsupported server image/colour features and downtime may limit results.

Use .bugreport for reproducible non-sensitive bugs. For privacy, deletion or security concerns, join support and open a ticket. Skye has no public nuke/reset-channel command.

Guided setup

Use /setup overview or .serversetup in a staff-only channel. Choose a section and setting, optionally pick channels or roles, then Configure. Each change saves independently. Finish shows saved settings; reopening resumes your last section. Administrator permission is required, and anti-nuke owner restrictions still apply.

Welcome, goodbye and boosts

Use .serverconfig welcome #welcome Welcome {mention}!, .serverconfig leave #goodbye {user} has left {server}. and .serverconfig boost #boosts Thank you {mention}!. Inspect the shared placeholders with .serverconfig placeholders. Each message type has its own destination and disable command.

Invite tracking

Tracking starts off. An authorized manager can use .invitetrack enable and configure the fake-invite threshold. Members can view .invites @user. Attribution can be unknown when Discord does not provide enough evidence; vanity URLs cannot always identify an inviter.

Logging and tickets

Use .logs setup #staff-log, then configure individual categories with .logs channel and .logs event. Use .ticket setup main to select a category, support role and destination, then .ticket panel main #support to publish the panel.

Targets, reasons and cases

User, role and channel arguments accept IDs alongside supported mentions and names. IDs never bypass permissions or role hierarchy. Reasons must be 1–400 characters without control characters. Durations accept minutes or s/m/h/d combinations; timeouts are limited to 28 days. Recent completed moderation cases are available privately through .memberhistory.

Customize tickets

Run .ticket setup main, select the category, support role and panel destination, then choose Customize everything. The same complete editor is available through .ticket edit main. Publish with .ticket panel main #support. All configuration requires Administrator; settings persist per server.

• Panel text and appearance: title, description, outside message, author, footer, color, image, thumbnail, fields and timestamp.
• Opening text and appearance: the same controls for each new ticket's first message, with an optional inherited color.
• Links and icons: separate title/author URLs and author/footer icons for the panel and opening embed.
• Menu and behavior: buttons or dropdown, dropdown placeholder, channel-name template and separate creator/support-role ping controls.
• Ticket reasons/options: up to 25 reasons with labels, emojis, button colors, dropdown descriptions and optional opening-message overrides. Route each reason to a category/support role by ID, or leave routing blank to inherit panel defaults.

Preview panel and Preview opening are private, suppress pings and create no channels. Custom fields use one Name | Value per line (up to 10); complete embeds must fit 6,000 characters. Media and link URLs must use HTTP/HTTPS without credentials. Panel text is static; opening templates share member/server placeholders with welcome, goodbye and boost, plus {reason}, {number}, {panel}, {support}, {channel} and {channel_id}. Channel placeholders are only available after creation. See .serverconfig placeholders ticket.

Existing buttons retain their identifiers. The one-open-ticket limit, creation cooldown, private channel overwrites and server ticket cap remain enforced. A failed posted-panel refresh is reported separately from saving settings. Discord Administrators can still access private ticket channels.

Preview member announcements

Administrators can use .serverconfig preview welcome, .serverconfig preview leave or .serverconfig preview boost to privately preview saved messages. Append draft text to preview it without saving. The slash equivalent is /automation preview. Your account is the sample member; previews do not ping anyone, post in announcement channels or enable disabled features.

Message cleanup

.purge 50 starts immediately. Recent messages use bulk batches of up to 100; older messages require individual deletion. There is no added per-message delay, but Discord rate limits still apply. The running status message is removed after success; partial-failure notices remain visible. Permissions and abuse limits are still enforced.

Anti-nuke and anti-raid

Both protections start disabled. Review .antinuke rules and .antiraid before enabling enforcement. Anti-nuke supports owner-approved escalation and fallback responses; anti-raid offers optional repeated joins, young-account bursts, newcomer spam detection, punishment budgets and temporary verification. Audit logs arrive after actions, and the bot cannot cross Discord role hierarchy or guarantee prevention.

AutoMod

Add blocked terms with .filter add, configure the spam threshold with .filter spam set, choose the response, then enable the relevant filters. Exemptions and punishment cooldowns remain separate from deleting matching messages.