Send notifications to Feishu/Lark. Internal utility used by other skills, or manually via /feishu-notify. Use when user says "发飞书", "notify feishu", or other skills need to send status updates.

Feishu/Lark Notification Send a notification: $ARGUMENTS Overview This skill provides Feishu/Lark integration for ARIS. It is designed as an internal utility — other skills call it at key events (experiment done, review scored, checkpoint waiting). It can also be invoked manually. Zero impact guarantee : If no feishu.json config exists, this skill does nothing and returns silently. All existing workflows are completely unaffected. Configuration The skill reads ~/.claude/feishu.json . If this file does not exist, all Feishu functionality is disabled — skills behave exactly as before. Config Format Modes Mode "mode" value What it does Requires Off "off" or file absent Nothing. Pure CLI as is Nothing Push only "push" Send webhook notifications at key events. Mobile push, no reply Feishu bot webhook URL Interactive "interactive" Full bidirectional. Approve/reject from Feishu, reply to checkpoints [feishu claude code](https://github.com/joewongjc/feishu claude code) running Workflow Step 1: Read Config File not found → return silently, do nothing "mode": "off" → return silently, do nothing "mode": "push" → proceed to Step 2 (push) "mode": "interactive" → proceed to Step 3 (interactive) Step 2: Push Notification (webhook) Send a rich card to the Feishu webhook: Card templates by event type: Event Title Color Body experiment done Experiment Complete green Results table, delta vs baseline review scored Review Round N: X/10 blue (≥6) / orange (<6) Score, verdict, top 3 weaknesses checkpoint Checkpoint: Waiting for Input yellow Question, options, context error Error: [type] red Error message, what failed pipeline done Pipeline Complete purple Final summary, deliverables custom Custom blue Free form message from $ARGUMENTS Return immediately after curl — push mode never waits for a response. Step 3: Interactive Notification (bidirectional) Interactive mode uses [feishu claude code](https://github.com/joewongjc/feishu claude code) as a bridge: 1. Send message to the bridge: 2. Wait for reply (with timeout): Returns: {"reply": "approve"} or {"reply": "reject"} or {"reply": "user typed message"} or {"timeout": true} 3. On timeout : Fall back to AUTO PROCEED behavior (proceed with default option). 4. Return the user's reply to the calling skill so it can act on it. Step 4: Verify Delivery Push mode : Check curl exit code. If non zero, log warning but do NOT block the workflow. Interactive mode : If bridge is unreachable, fall back to push mode (if webhook configured) or skip silently. Helper Function (for other skills) Other skills should use this pattern to send notifications: This check is always guarded. If the config file doesn't exist, the skill skips the notification block entirely — zero overhead, zero side effects. Event Catalog Skills send these events at these moments: Skill Event When /auto review loop review scored After each round's review score /auto review loop pipeline done Loop complete (positive or max rounds) /auto paper improvement loop review scored After each round's review score /auto paper improvement loop pipeline done All rounds complete /run experiment experiment done Screen session finishes /idea discovery checkpoint Between phases (if interactive) /idea discovery pipeline done Final report ready /monitor experiment experiment done Results collected /research pipeline checkpoint Between workflow stages /research pipeline pipeline done Full pipeline complete Key Rules NEVER block a workflow because Feishu is unreachable. Always fail open. NEVER require Feishu config — all skills must work without it. Config file absent = mode off. No error, no warning, no log. Push mode is fire and forget. Send curl, check exit code, move on. Interactive timeout = auto proceed. Don't hang forever waiting for a reply. Respect AUTO PROCEED : In interactive mode, if the user doesn't reply within timeout, use the same auto proceed logic as the calling skill. No secrets in notifications. Never include API keys, tokens, or passwords in Feishu messages.