notify

Drafts and dispatches research-progress briefings through user-configured notification services.

75|7|Updated May 2, 2026
One-click install
npx skills add https://github.com/zjunlp/Mechanist --skill notify-zjunlp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: notify
Source: https://github.com/zjunlp/Mechanist/tree/main/skills/notify
Command: npx skills add https://github.com/zjunlp/Mechanist --skill notify-zjunlp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long-running autonomous research pipelines leave users in the dark about progress, failures, and blockers. This Skill turns workspace artifacts into human-readable progress briefings and delivers them through whatever notification channel the user has already configured, so researchers stay informed without polling logs. ## Core Features & Use Cases - Opt-in briefing generation: Reads task.md for a notification directive and silently does nothing unless the user opted in, guaranteeing zero side effects otherwise. - Channel-agnostic dispatch: Detects whatever notification service is configured (email account, webhook, chat integration) and sends through it without hard-coding any tool; always saves a timestamped copy to notification/ even when nothing is configured. - Delta-aware reporting: Compares against the previous briefing to report what changed — runs finished, verdicts flipped, GPU-hours consumed — and leads with blockers requiring human action. - Use Case: During a multi-hour mechanistic interpretability experiment, the pipeline calls this Skill hourly and on done/halted/approval-needed events, emailing the researcher a TL;DR update like "C1 verified PASS, 2 runs left" with a clear action item when blocked. ## Quick Start Ask the agent to send a progress notification for the current run, for example by invoking /notify with an event type such as progress or approval-needed.

Frequently Asked Questions about notify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get email notifications from an autonomous research pipeline?

Add a notification directive such as "notify: email" or natural-language intent like "email me when done" to task.md at the project root. The Skill then drafts briefings from workspace artifacts and dispatches them through whatever email service you have already configured.

How to send progress updates without hard-coding a notification tool?

Use a channel-agnostic approach: draft the briefing text first, then scan the environment for whatever service the user configured — an email account, webhook, or chat integration — and send through that service's own interface. If none exists, save the briefing to disk as the durable record.

Does the notify skill work if no notification service is configured?

Yes. It still drafts the briefing and saves it as a timestamped Markdown file in the notification/ directory, then logs that no dispatch channel was configured. The saved file serves as the durable record, and the pipeline continues unaffected.

What happens when a notification fails to send?

Dispatch errors such as non-zero exits, expired auth, or rate limits are logged and swallowed. The saved notification file is kept, and the pipeline proceeds without blocking or failing loudly.

When does the notify skill do nothing at all?

It is a silent no-op unless task.md contains an explicit opt-in marker like "notify:" or natural-language intent to be notified. Without that signal it returns immediately without drafting or writing any files.