PAKIKNOWLEDGE/dsh-notify-skill
DSH skill: email reminders from your agent when you're away — fires at goal completion / blockage / when your decision is needed
Listed
0
Notify
Bundle verified
Preview
What it does
Email reminders from your DSH agent when you're away: fires at goal completion, blockage, before asking the user a decision, and at long-task milestones via a bundled zero-dependency Node SMTP sender.
Best for
- Users who leave long-running agent tasks unattended and want email alerts on completion or blockage.
- Workflows where the agent should notify the user before requesting a decision or at a milestone.
- Environments that need a lightweight SMTP sender using only Node.js built-ins.
Not ideal for
- Users who need two-way remote control or replies; the plugin provides one-way notifications.
- Users without SMTP access, a recipient mailbox, or the required authorization-code configuration.
- Workflows where email is unnecessary because the user remains at the active session.
README
dsh-notify-skill
| English | 中文 |
Email reminders from your DSH agent when you’re away from the computer.
You start a long-running goal in DSH (or any AI coding agent), then walk away. When the agent finishes, gets blocked, or needs your decision, it sends an email to your phone mailbox — you see it and come back. One-way ping, no remote control.
Design: bundle a sender, teach the fallback
The skill ships one zero-dependency implementation — sender.mjs (~70 lines, only Node built-ins tls/net), so the agent sends mail deterministically in every normal DSH session (DSH runs on Node). The SKILL.md still carries the full contract:
- when to notify (goal done / blocked / before asking you a decision / long-task milestone),
- what to write (specific, in your language, short),
- the config contract (
config.json: sender, SMTP authorization code, recipient; auto-inferred hosts for QQ/163 mail), - how to guide the user through getting an SMTP authorization code when the config is missing,
- failure handling and security rules.
If Node is genuinely unavailable (rare), the skill’s instructions tell the agent to implement the ~15-line SMTP call itself with whatever the environment provides — Python smtplib, curl, mail, … — so the skill stays cross-platform (Windows/Linux/macOS) and future-proof.
How it works
| Moment | Suggested marker |
|---|---|
| Goal completed | done |
| Goal blocked / stuck | block |
| About to ask the user a decision | question |
| Long task milestone | info |
The agent sends via the bundled sender:
node sender.mjs "subject" "body" # reads config.json next to it
Knowledge note (Windows): .NET
SmtpClienthas a known hang on implicit-TLS port 465 — the bundled sender usesnode:tlsinstead, which has no such issue.
Install (DSH)
Plugin install (recommended) — the skill ships as a DSH plugin and registers on ctx.skills:
dsh plugin --profile web add dsh-notify-skill
Or from GitHub: dsh plugin --profile web add github:PAKIKNOWLEDGE/dsh-notify-skill. Restart dsh web once after installing, then the skill appears in the session skill catalog.
Manual install (no plugin) — DSH also discovers skills from <dshHome>/skills/<name>/SKILL.md (default ~/.dsh/skills), hot-reloaded by a filesystem watcher:
git clone https://github.com/PAKIKNOWLEDGE/dsh-notify-skill.git "$HOME/.dsh/skills/notify"
Or copy the folder manually to ~/.dsh/skills/notify/. New sessions pick it up immediately.
Setup (one-time, ~5 minutes)
The agent will also walk you through this if you just ask it to use the skill.
- Get an SMTP authorization code (not your login password):
- QQ Mail: web QQ Mail → 设置 → 账户 → enable “POP3/SMTP 服务” → generate a 16-char 授权码
- 163 Mail: web 163 Mail → 设置 → POP3/SMTP/IMAP/SMTP → enable → create 授权码
- Copy
config.example.jsontoconfig.jsonand fill it in:{ "email": { "smtpHost": "", "smtpPort": 465, "useSsl": true, "from": "your-address@qq.com", "authCode": "16-char authorization code", "to": "recipient@example.com" } }smtpHostmay be left empty — it is inferred (@qq.com→smtp.qq.com,@163.com→smtp.163.com, port 465 SSL). - Test: ask your agent to send a test notification (it will implement the sender itself).
Other agents (Claude Code, Codex, …)
No compatibility work needed — modern agents are smart. Point them at SKILL.md and the config contract; they implement the sender themselves.
Security
-
config.json(contains your SMTP authorization code) andnotify.logare gitignored — never force-commit them. A leaked authorization code lets anyone send mail as your mailbox. - The skill instructs agents to never print or commit the authorization code.
License
Frequently Asked QuestionsFAQ
Use the verified command dsh plugin --profile default add github:PAKIKNOWLEDGE/dsh-notify-skill in a DSH-enabled shell. The command resolves the public package metadata and keeps the plugin attached to the catalog identity shown on this page.
Compatibility follows the bundle and profile status shown above. If a profile is not detected, keep the plugin disabled there and check the repository documentation before enabling it in production.
The GitHub link and activity metadata are the source of truth for releases and maintenance. Revisit this page after a new release to confirm the catalog has observed the latest version.