discord-hub-builder_skill

This skill builds a complete Discord AI command center via API, creating categories, channels, roles, and pinned workflow cards for agent management.
  • Python

2.6k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill discord-hub-builder

  • _meta.json295 B
  • SKILL.md2.7 KB

Overview

This skill builds a complete Discord AI command center server from scratch using the Discord REST API. It automates creation of categories, channels, roles, permissions hints, and pins workflow cards into agent channels. The process runs entirely via API calls so no manual UI steps are required once prerequisites are met.

How this skill works

The skill uses a Discord bot token and target guild ID to call the REST API and provision resources. It creates roles (skips by name if present), creates categories and channels, posts and pins workflow cards in each agent channel, and prints resulting channel IDs. A dry-run mode previews changes before any live modifications to the server.

When to use it

  • Setting up a professional server for AI agent management and coordination.
  • Rapidly provisioning standardized channels, roles, and pinned workflow templates for a new guild.
  • Migrating or restoring a command center layout to a new or backup server.
  • Onboarding a team that needs a consistent Discord structure for agents, reviewers, and ops.
  • When you want a repeatable, scriptable way to create agent channels with pinned runbooks.

Best practices

  • Always run the dry-run preview and confirm before executing live changes.
  • Ensure the bot has Manage Channels, Manage Roles, Send Messages, and Manage Messages permissions before running.
  • Keep a backup of role and channel naming conventions to avoid duplicates on re-runs.
  • After build, manually verify channel-specific permission overrides (e.g., task-queue owner-only send).
  • If you hit rate limits, add small delays between requests and retry failed calls.

Example use cases

  • Create a COMMAND CENTER with #daily-brief and #task-queue and standardized roles for agents and reviewers.
  • Provision multiple AGENT CHANNELS and pin workflow cards that describe TOOL / TRIGGER / INPUT / OUTPUT / FREQUENCY.
  • Stand up a RESEARCH & OUTPUTS area with channels for financial briefs, content drafts, and archives.
  • Recreate an archived command center layout on a new server for continuity or disaster recovery.
  • Add operations channels for logs and ops notes, then share channel IDs with team tooling for integrations.

FAQ

You need a bot token, the target guild ID, and the bot must have Manage Channels, Manage Roles, Send Messages, and Manage Messages permissions.

Can I preview changes before they are made?

Yes — always run the dry-run option first to get a preview of created resources and confirm before live execution.

Will re-running the script create duplicates?

Roles are skipped by name to avoid duplicates, but channels are not deduplicated; re-running will create duplicate channels unless you remove them first.

How do I handle rate limit errors?

Add small sleeps between API calls or wait and retry after receiving 429 responses; implement retry logic for robust runs.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational