Discord API Skill

Use this skill to run Discord REST operations through uxc + OpenAPI.

Reuse the uxc skill for shared execution, auth, and error-handling guidance.

Prerequisites

• - uxc is installed and available in PATH.
• Network access to https://discord.com/api/v10.
• Access to Discord OpenAPI spec URL:

• - Discord bot token (recommended) or OAuth2 user authentication (limited functionality).

Authentication

Option 1: Bot Token (Recommended)

Bot token provides full access to Discord API including reading messages, managing servers, sending messages, and all administrative operations. This is the recommended method for most use cases.

1. 1. Create a bot application at https://discord.com/developers/applications
2. Generate a bot token from the Bot section
3. Configure bot credential:

CODEBLOCK0

1. 4. Bind credential to Discord API endpoint:

CODEBLOCK1

Option 2: OAuth2 User Authentication (Limited Use Cases)

Important: User OAuth2 has significant limitations and is not recommended for most operations:

• - ❌ Cannot read channel messages via HTTP API (local RPC only)
• ❌ Cannot send messages or manage servers
• ✅ Can read user profile, email, connections
• ✅ Can list user's servers

Only use OAuth2 if you specifically need to access user profile information as the user. For all other operations, use Bot Token.

If you still need OAuth2 for user profile operations:

Configuration:

• - Client ID: INLINECODE6
• Redirect URI: INLINECODE7

OAuth2 Scopes:

Discord user OAuth2 supports read-only operations. It cannot send messages or manage servers as a user (use Bot Token for those operations).

Recommended Scopes (Full Functionality):
CODEBLOCK2

Minimal Read-Only Scopes:
CODEBLOCK3

Scope Reference:

Note: User OAuth2 cannot send messages or manage servers as the user. Use Bot Token for write operations. guilds.join is a special user OAuth write capability that depends on the same application's bot already being in the target guild, so it is not part of the default read-only flow. See Discord OAuth2 documentation for complete scope list.

Two-Stage OAuth Flow (Agent-Friendly):

1. 1. Start OAuth flow with desired scopes:

1. 2. Open the displayed authorization URL in browser, complete authorization, then copy the callback URL from browser address bar.

1. 3. Complete OAuth flow:

1. 4. Bind credential:

Interactive Alternative (Local Terminal Only):

CODEBLOCK7

Then paste the callback URL when prompted.

Core Workflow

1. 1. Use fixed link command by default:

1. 2. Discover operations with schema mapping:

1. 3. Inspect operation schema first:

1. 4. Execute operation:

Authentication Methods Comparison

Key Recommendation: Use Bot Token for almost all operations. User OAuth2 is only useful if you need to read user profile information as that specific user. For reading channel messages, managing servers, or sending messages, Bot Token is required.

Subscribe / Gateway Status

Discord inbound events flow through the Gateway WebSocket, not through this REST/OpenAPI surface.

Current uxc subscribe status:

• - the built-in discord-gateway transport now bootstraps through INLINECODE29
• live Gateway sessions reached READY and delivered INLINECODE31
• a real posted channel message produced a MESSAGE_CREATE event in the subscribe sink
• heartbeat scheduling, IDENTIFY, sequence tracking, and reconnect handling are implemented

Recommended invocation:

CODEBLOCK8

Intent notes:

• - 4609 = INLINECODE35
• add 32768 (MESSAGE_CONTENT) only when the bot has that privileged intent enabled in the Discord developer portal

Use discord-openapi-cli for REST calls and uxc subscribe start ... --transport discord-gateway ... for inbound Gateway events.

Guardrails

• - OAuth2 Scope Limitation: User OAuth2 tokens cannot read channel messages via HTTP API, send messages, or manage servers. These operations require Bot Token authentication.
• Discord OpenAPI spec is persisted in the generated link via uxc link --schema-url ...; pass --schema-url <other-url> only when you need to override it temporarily.
• Keep automation on JSON output envelope; do not use --text.
• Parse stable fields first: ok, kind, protocol, data, error.
• Prefer positional JSON for non-string objects instead of --input-json.
• INLINECODE49 is equivalent to uxc https://discord.com/api/v10 --schema-url <discord_openapi_spec> <operation> ....
• Treat post:/channels/{channel_id}/messages, delete/update endpoints, and moderation endpoints as write/high-risk operations; require explicit user confirmation before execution.

References

• - Usage patterns: INLINECODE52
• Discord API docs: https://discord.com/developers/docs
• Discord API OpenAPI spec: https://github.com/discord/discord-api-spec