ClawHub

Discord Interactive

v1.1.1

Send Discord Components v2 interactive messages (buttons, selects, modals, rich layouts) via the message tool.

⭐ 1· 302·2 current·2 all-time
byLinn@muselinn
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description (Discord interactive components) match the SKILL.md and reference files. There are no unrelated environment variables, binaries, or install steps requested that would be disproportionate to sending interactive Discord messages.
✓
Instruction Scope
The instructions are scoped to constructing component payloads, sending/editing messages via the message tool, and handling the resulting inbound interaction text. There are no instructions to read arbitrary system files, environment variables, or to transmit data to unexpected endpoints. Note: examples show using components to confirm destructive actions (e.g., deleting files) — that is a valid usage pattern but requires cautious agent policies.
✓
Install Mechanism
No install spec and no code files — instruction-only skill. This minimizes write-to-disk and supply-chain risk.
✓
Credentials
Skill declares no required environment variables, credentials, or config paths. The examples reference Discord IDs, URLs, and attachment:// filenames only, which are appropriate for the stated functionality.
✓
Persistence & Privilege
Skill does not request always:true or other elevated persistence. It is user-invocable and allows normal autonomous invocation (platform default); nothing here indicates it would modify other skills or system-wide settings.
Assessment
This skill is coherent and focuses only on building and handling Discord interactive messages. Before installing: (1) confirm you trust agents that will use this skill because examples show workflows where a button click leads the agent to perform actions (including destructive ones); enforce safeguards/confirmation for destructive operations, (2) restrict interactive buttons using allowedUsers where appropriate, (3) treat modal-submitted form data as potentially sensitive and validate/sanitize it before using, and (4) test these components in a non-production channel to verify behavior and avoid accidental actions.

Like a lobster shell, security has layers — review code before you run it.

latestvk979scwr324sp9y9ng1djdhm85835bva

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Runtime requirements

🔘 Clawdis

Comments