Discord Channel Auditor

Audit and auto-update a Discord server guide channel. Compares a reference guide message against actual channels, detects new/renamed/deleted/moved channels,...

Security Scan

The skill's stated purpose (keeping a Discord guide channel in sync) matches its instructions, but the runtime instructions are ambiguous about which messages may be deleted/edited and lack safety constraints, creating a real risk of unintended message deletion or excessive privileges.

Purpose & Capability

Name/description (audit and update a Discord guide) align with the SKILL.md workflow: listing channels, reading the guide, comparing, and updating. Relying on OpenClaw's built-in message tool for Discord operations is coherent for this purpose.

Instruction Scope

Instructions tell the agent to 'Delete old guide messages and post fresh guide' but do not specify safe selection criteria (e.g., only delete messages authored by the bot or tagged as guides). This gives the agent broad discretion to delete/edit messages in the guide channel and may accidentally remove other users' content. The SKILL.md is otherwise narrowly scoped (channel-list, read, send, delete, edit) and does not reference unrelated files or env vars.

Install Mechanism

Instruction-only skill with no install spec or code files — minimal disk/system footprint. Lower installation risk.

Credentials

No environment variables or external credentials requested by the skill itself. However, it requires the bot to have 'Send Messages' and 'Manage Messages' permissions and 'View Channel' to list channels — these are elevated permissions and grant the platform-level message tool broad capabilities; ensure the bot's scope is limited to the intended guild/channel.

Persistence & Privilege

always:false (normal). disable-model-invocation:false (normal platform default). The skill does not request persistent installation or modify other skills' configs.

What to consider before installing

This skill appears to do what it claims, but its instructions are underspecified and could lead to accidental deletion or editing of non-guide messages. Before installing: - Confirm OpenClaw's message tool enforces per-bot and per-channel scoping (that the skill cannot delete messages it shouldn't). - Ensure the bot account has only the minimum permissions needed and is limited to the target guild/channel. - Require the guide messages to be identifiable (e.g., always authored by the bot or include a unique marker) so the skill only deletes messages it created. - Ask the author to add explicit safeguards to SKILL.md: a dry-run mode, only delete messages authored by the bot or containing a guide tag, confirm large changes with a human, and a tombstone marker for historical messages. - Test on a throwaway server/role-limited environment and run manually before enabling a daily cron. If the maintainer provides concrete deletion/edit selection rules (or code enforcing them), or shows that OpenClaw enforces scoped permissions, this evaluation could move to benign.

Keep a server guide channel automatically synced with actual Discord channels.

Requirements

• OpenClaw with Discord channel configured (no extra credentials needed)
• Uses OpenClaw's built-in message tool for all Discord operations (channel-list, read, send, delete, edit)
• Bot must have "View Channel" permission in the guild to list channels
• Bot must have "Send Messages" + "Manage Messages" in the guide channel to post/delete

When to Use

• Maintaining a #how-to or #server-guide channel
• After creating, renaming, deleting, or moving channels
• On a daily cron to catch drift

Workflow

1. Fetch channel list using message(action=channel-list) for the guild
2. Read current guide using message(action=read) on the guide channel
3. Compare -- check for:
   • New channels not in the guide
   • Channels in the guide that no longer exist
   • Renamed channels (ID exists, name changed)
   • Moved channels (different category)
   • Wrong descriptions
4. If changes found: Delete old guide messages and post fresh guide
5. If no changes: Do nothing (save tokens)

Guide Format

Organize by category in Discord display order (by position). Use this structure:

**📥 Category Name**
- **#channel-name** -- Brief description of purpose
- **#another-channel** -- What goes here

**💼 Another Category**
- **#work-channel** -- Description

Rules

• Keep descriptions to one line, max ~10 words
• Match category emoji to Discord category name
• List channels in position order within each category
• Include a "General tips" section at the bottom
• Post as 1-2 messages max (Discord 2000 char limit per message)
• Skip voice channels unless specifically relevant

Cron Setup

Schedule: daily at a quiet hour (e.g., 6 AM local)
Session: isolated
Timeout: 120 seconds
Delivery: none (don't notify, just update silently)

Edge Cases

• New category with no channels: include header, note "(empty)"
• Private channels: skip unless the bot has access
• Archived channels: skip