OpenClaw

discord-hub

OpenClaw skill for Discord Bot API workflows, covering interactions, commands, messages, and operations using direct HTTPS requests.

codedao120 来源安装数☆ 0 仓库 Stars

查看来源 ↗安装与使用 SKILL.md ↗

安装与使用

请根据来源仓库和你的 AI 工具说明安装此技能。先阅读技能文件和依赖要求，再添加到工作流。

SkillHub CLI

skillhub install codedao12/discord-hub

打开来源仓库，查看说明和兼容环境后，按来源提供的命令或步骤安装。

将来源链接提供给你的 Agent，让它先读取说明、核对依赖，并向你说明将执行的安装步骤。

查看来源 ↗使用指南

技能说明

Discord Bot API Skill (Advanced)

Purpose

Provide a production-oriented guide for building Discord bot workflows via the REST API and Interactions, focusing on professional command UX, safe operations, and direct HTTPS usage (no SDKs).

Best fit

You want command-first bot behavior and clear interaction flows.
You prefer direct HTTP requests without a library dependency.
You need a structured map of Discord API surfaces.

Not a fit

You need a full SDK or gateway client implementation.
You plan to stream large media uploads directly.

Quick orientation

Read references/discord-api-overview.md for base URL, versioning, and object map.
Read references/discord-auth-and-tokens.md for token types and security boundaries.
Read references/discord-interactions.md for interaction lifecycle and response patterns.
Read references/discord-app-commands.md for slash, user, and message commands.
Read references/discord-messages-components.md for messages, embeds, and components.
Read references/discord-gateway-webhooks.md for gateway vs webhook tradeoffs.
Read references/discord-rate-limits.md for throttling and header-based handling.
Read references/discord-request-templates.md for HTTP payload templates.
Read references/discord-feature-map.md for the full surface checklist.

Required inputs

Bot token and application ID.
Interaction endpoint public key (if using interaction webhooks).
Command list and UX tone.
Allowed intents and event scope.

Expected output

A clear bot workflow plan, command design, and operational checklist.

Operational notes

Prefer interactions and slash commands over prefix parsing.
Always validate incoming interaction signatures.
Keep payloads small and respond quickly to interactions.

Security notes

Never log tokens or secrets.
Use least-privilege permissions and scopes.

来源信息

Source: github
Repository: openclaw/skills
Path: skills/codedao12/discord-hub
Version: —
Commit: 511e60068489cb98cc1043e2ce2702e4de7bd375
分类来源: rules
状态: active
可见性: public

这些信息来自收录时的来源分析，可能滞后；使用前请核对最新来源文件。

来源内容

SKILL.md

# Discord Bot API Skill (Advanced)

## Purpose
Provide a production-oriented guide for building Discord bot workflows via the REST API and Interactions, focusing on professional command UX, safe operations, and direct HTTPS usage (no SDKs).

## Best fit
- You want command-first bot behavior and clear interaction flows.
- You prefer direct HTTP requests without a library dependency.
- You need a structured map of Discord API surfaces.

## Not a fit
- You need a full SDK or gateway client implementation.
- You plan to stream large media uploads directly.

## Quick orientation
- Read `references/discord-api-overview.md` for base URL, versioning, and object map.
- Read `references/discord-auth-and-tokens.md` for token types and security boundaries.
- Read `references/discord-interactions.md` for interaction lifecycle and response patterns.
- Read `references/discord-app-commands.md` for slash, user, and message commands.
- Read `references/discord-messages-components.md` for messages, embeds, and components.
- Read `references/discord-gateway-webhooks.md` for gateway vs webhook tradeoffs.
- Read `references/discord-rate-limits.md` for throttling and header-based handling.
- Read `references/discord-request-templates.md` for HTTP payload templates.
- Read `references/discord-feature-map.md` for the full surface checklist.

## Required inputs
- Bot token and application ID.
- Interaction endpoint public key (if using interaction webhooks).
- Command list and UX tone.
- Allowed intents and event scope.

## Expected output
- A clear bot workflow plan, command design, and operational checklist.

## Operational notes
- Prefer interactions and slash commands over prefix parsing.
- Always validate incoming interaction signatures.
- Keep payloads small and respond quickly to interactions.

## Security notes
- Never log tokens or secrets.
- Use least-privilege permissions and scopes.

搜索