feishu-notify

Q: How do I install feishu-notify?

Run npx skills add https://github.com/wanshuiyin/auto-claude-code-research-in-sleep --skill feishu-notify in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/feishu-notify/ (personal) or .claude/skills/feishu-notify/ (project).

Q: Which AI agents can use feishu-notify?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Q: Is feishu-notify safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Q: Who maintains feishu-notify?

It is published by wanshuiyin in wanshuiyin/auto-claude-code-research-in-sleep. It has 493 recorded installs.

by wanshuiyinProductivity & Automation

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.

Installs: 493
Last 24h: —
Trending rank: —
Security: Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/wanshuiyin/auto-claude-code-research-in-sleep --skill feishu-notify

01
Install
Run the command in your project. The CLI asks which agents to install for.
02
Describe the task
Ask your agent for something this skill covers. It loads feishu-notify automatically when relevant.
03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

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

{
  "mode": "push",
  "webhook_url": "https://open.feishu.cn/open-apis/bot/v2/hook/YOUR_WEBHOOK_ID",
  "interactive": {
    "bridge_url": "http://localhost:5000",
    "timeout_seconds": 300
  }
}

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 running

Workflow

Step 1: Read Config

cat ~/.claude/feishu.json 2>/dev/null

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:

curl -s -X POST "$WEBHOOK_URL" \
  -H "Content-Type: application/json" \
  -d '{
    "msg_type": "interactive",
    "card": {
      "header": {
        "title": {"tag": "plain_text", "content": "TITLE"},
        "template": "COLOR"
      },
      "elements": [
        {"tag": "markdown", "content": "BODY"}
      ]
    }
  }'

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 as a bridge:

Send message to the bridge:

curl -s -X POST "$BRIDGE_URL/send" \
  -H "Content-Type: application/json" \
  -d '{"type": "EVENT_TYPE", "title": "TITLE", "body": "BODY", "options": ["approve", "reject", "custom"]}'

Wait for reply (with timeout):
```
curl -s "$BRIDGE_URL/poll?timeout=$TIMEOUT_SECONDS"
```
Returns: {"reply": "approve"} or {"reply": "reject"} or {"reply": "user typed message"} or {"timeout": true}
On timeout: Fall back to AUTO_PROCEED behavior (proceed with default option).
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:

### Feishu Notification (if configured)

Check if `~/.claude/feishu.json` exists and mode is not "off":
- If **push** mode: send webhook notification with event summary
- If **interactive** mode: send notification and wait for user reply
- If **off** or file absent: skip entirely (no-op)

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.

FAQ

What does the feishu-notify skill do?

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.

How do I install feishu-notify?

Run npx skills add https://github.com/wanshuiyin/auto-claude-code-research-in-sleep --skill feishu-notify in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/feishu-notify/ (personal) or .claude/skills/feishu-notify/ (project).

Which AI agents can use feishu-notify?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is feishu-notify safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains feishu-notify?

It is published by wanshuiyin in wanshuiyin/auto-claude-code-research-in-sleep. It has 493 recorded installs.