agent-job-dm
Send a direct message to a user OR broadcast to all subscribed admins via their default channel (currently Telegram). Also looks up users when a specific person is named. Trigger when the user says "let me know when…", "DM me", "send X to <name>", "tell <name> that…", "notify the admins", "alert everyone", "broadcast this", "let the team know", "tell all admins", or asks "who are the users?", "list users".
pinned to #33f032dupdated last week
Ask your AI client: “install skills/agent-job-dm”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/agent-job-dmmetahub onboarded this repo on the author's behalf.
If you own github.com/stephengpope/thepopebot on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
1,845
Last commit
last week
Latest release
published
Evaluation report
WarningsAutomated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.33f032d· last week
Documentation
41Description quality
69 words · 409 chars — "Send a direct message to a user OR broadcast to all subscribed admins via their …"
README is present and substantial
13,517 chars · 9 sections · 8 code blocks
Tags / topics declaredwarn
No manifest tags and no GitHub repo topics
Add tags to the manifest (or GitHub topics on the repo) so the registry's search and category filters surface this artifact.
README has usage / example sections
no labeled section but 8 code blocks document usage
Homepage / docs URL declared
https://skool.com/ai-architects
Release history
1- releasecurrent33f032dwarnlast week
Contents
The three modes — pick one
Read the request and route to exactly one of these. Do NOT mix them.
Mode 1 — Broadcast to admins
Trigger phrases: "notify the admins", "alert everyone", "broadcast this", "let the team know", "tell all admins", "send to admins".
node skills/agent-job-dm/agent-job-dm.js send "<message>" --broadcast
DO NOT run list first. DO NOT look up any user ids. The --broadcast flag handles fan-out internally — it sends to every admin where subscribed_to_system_messages=true automatically. Calling list and then sending one-at-a-time is wrong and skips the subscription filter.
Mode 2 — DM the originator (the user who started this job)
Trigger phrases: "DM me", "let me know when…", "tell me when…", "ping me", "send me".
node skills/agent-job-dm/agent-job-dm.js send "<message>"
No flags. The skill reads USER_ID from the environment (the originator) and sends to them. Don't look them up — USER_ID is already correct.
Mode 3 — DM a specific named user
Trigger phrases: "tell Alice…", "send this to bob@…", "DM <name>", "message <person>".
node skills/agent-job-dm/agent-job-dm.js list
node skills/agent-job-dm/agent-job-dm.js send --user-id <id> "<message>"
- Run
listto get the directory. - Match the requested name against
nickname,first_name,last_name, oremail. If multiple match, ask which one. - Send with
--user-id <id>.
Other commands
# List users (id, email, first/last name, nickname, role, available DM channels)
node skills/agent-job-dm/agent-job-dm.js list
Rules
- The
<message>arg is sent verbatim. Don't rewrite it unless the requester asked you to. AGENT_JOB_TOKEN,APP_URL, andUSER_IDare injected automatically — no setup required.- Every DM is stored in the recipient's inbox in the event handler, regardless of delivery channel.
- Users link their DM channel themselves in
/profile/telegram. If a target user has no verified channel, the message still lands in their inbox.
Reviews
No reviews yet. Be the first.
Related
Verification Before Completion
Evidence before assertions, always
Writing Plans
Turn specs into phased implementation plans
Test-Driven Development
Red → green → refactor discipline for any feature or bugfix
mh install skills/agent-job-dm