Run any Skill in Manus with one click

discord-messaging

Stars69

Forks31

UpdatedJuly 9, 2026 at 16:36

Explains how to send Discord messages from cron jobs that don't have a NypsiClient/gateway connection, covering WebhookClient vs the shared getRest() REST client. Use when writing or editing a scheduled job in src/scheduled/jobs/ that needs to post a message to a channel.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

mxz7

mxz7/nypsi

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	discord-messaging
description	Explains how to send Discord messages from cron jobs that don't have a NypsiClient/gateway connection, covering WebhookClient vs the shared getRest() REST client. Use when writing or editing a scheduled job in src/scheduled/jobs/ that needs to post a message to a channel.

Sending Messages Outside the Main Client

Two patterns exist in src/scheduled/jobs/ for posting messages from cron jobs (no NypsiClient/gateway connection available):

WebhookClient (discord.js) - used when a dedicated webhook URL exists in env (e.g. LOTTERY_HOOK, TOPCOMMANDS_HOOK, per-guild birthdayHook). Simple, but requires a webhook to be created/stored per destination.
Shared REST client (src/utils/rest.ts, getRest()) - wraps @discordjs/rest, authed with BOT_TOKEN. Post directly to a channel with rest.post(Routes.channelMessages(channelId), { body: { embeds: [...] } }). Embeds must be plain JSON (.toJSON() on CustomEmbed/EmbedBuilder instances, not the builder objects themselves). Preferred when you already know a channel ID and don't want to manage a separate webhook URL/secret (e.g. topbalance.ts posts to channel 833052442069434429 this way).

getRest(client?) returns client.rest if a NypsiClient is passed (has an active gateway connection), otherwise a standalone REST instance - use the standalone version in jobs since they don't have a client instance.

More from this repository

same repository

codebase-structure

mxz7/nypsi

Explains command/interaction handler patterns, slash command option builders, Sharp image processing usage, and the sudoku-gen package status. Use when adding or modifying commands, interaction handlers (buttons/autocomplete), slash command options/subcommands, or any image generation code.

2026-07-1969

economy-items

mxz7/nypsi

How to look up economy items by user-provided text (name/id/alias/plural) and compute their worth in this codebase, centered on selectItem() and calcItemValue() in src/utils/functions/economy/inventory.ts and getItems() in economy/utils.ts. Use whenever a command, tool, or feature needs to resolve a search string to an Item or needs an item's current value.

2026-07-0969

openai-tool-calling

mxz7/nypsi

How to add OpenAI Responses API function/tool calling (with structured `text.format` output) in this repo, based on the implementation in src/utils/functions/ai/help-chat.ts. Use when adding or modifying tool calls for any AI chat flow (openai.responses.parse).

2026-07-0969

conventions

mxz7/nypsi

Describes how to structure commands, scheduled jobs, interaction handlers, and user-facing messages/embeds in nypsi. Use when creating or modifying a command, a cron job in src/scheduled/jobs, an interaction/autocomplete handler, or when sending any message to a user.

2026-07-0969

leaderboards

mxz7/nypsi

Notes the leaderboard export/import conventions in src/utils/functions/economy/top.ts, including how global vs guild scope is selected. Use when adding a new leaderboard or modifying existing top/leaderboard functions.

2026-07-0969

prisma-schema

mxz7/nypsi

Safe workflow for editing prisma/schema.prisma without corrupting model blocks, and for regenerating the Prisma client. Use whenever you need to add, remove, or modify a field or model in the Prisma schema.

2026-07-0969

name	discord-messaging
description	Explains how to send Discord messages from cron jobs that don't have a NypsiClient/gateway connection, covering WebhookClient vs the shared getRest() REST client. Use when writing or editing a scheduled job in src/scheduled/jobs/ that needs to post a message to a channel.

Sending Messages Outside the Main Client

Two patterns exist in src/scheduled/jobs/ for posting messages from cron jobs (no NypsiClient/gateway connection available):

WebhookClient (discord.js) - used when a dedicated webhook URL exists in env (e.g. LOTTERY_HOOK, TOPCOMMANDS_HOOK, per-guild birthdayHook). Simple, but requires a webhook to be created/stored per destination.
Shared REST client (src/utils/rest.ts, getRest()) - wraps @discordjs/rest, authed with BOT_TOKEN. Post directly to a channel with rest.post(Routes.channelMessages(channelId), { body: { embeds: [...] } }). Embeds must be plain JSON (.toJSON() on CustomEmbed/EmbedBuilder instances, not the builder objects themselves). Preferred when you already know a channel ID and don't want to manage a separate webhook URL/secret (e.g. topbalance.ts posts to channel 833052442069434429 this way).