Discord
Purpose
Use when you need to control Discord from CoWork-OSS via the discord tool: send messages, react, post or upload stickers, upload emojis, run polls, manage threads/pins/search, create/edit/delete channels and categories, fetch permissions or member/role/channel info, or handle moderation actions in Discord DMs or channels.
Routing
-
Use when: Use when the user asks to use when you need to control Discord from CoWork-OSS via the discord tool: send messages, react, post or upload stickers, upload emojis, run polls, manage threads/pins/search, create/edit/delete channels and categories, fetch permissions or member/role/channel info, or handle moderation actions in Discord DMs or channels.
-
Do not use when: Do not use when the request is asking for planning documents, high-level strategy, or non-executable discussion; use the relevant planning or design workflow instead.
-
Outputs: Outcome from Discord: task-specific result plus concrete action notes.
-
Success criteria: Returns concrete actions and decisions matching the requested task, with no fabricated tool-side behavior.
Trigger Examples
Positive
-
Use the discord skill for this request.
-
Help me with discord.
-
Use when the user asks to use when you need to control Discord from CoWork-OSS via the discord tool: send messages, react, post or upload stickers, upload emojis, run polls, manage threads/pins/search, create/edit/delete channels and categories, fetch permissions or member/role/channel info, or handle moderation actions in Discord DMs or channels.
-
Discord: provide an actionable result.
Negative
-
Do not use when the request is asking for planning documents, high-level strategy, or non-executable discussion; use the relevant planning or design workflow instead.
-
Do not use discord for unrelated requests.
-
This request is outside discord scope.
-
This is conceptual discussion only; no tool workflow is needed.
Runtime Prompt
-
Current runtime prompt length: 1101 characters.
-
Runtime prompt is defined directly in ../discord.json .