wanshuiyin/auto-claude-code-research-in-sleep

feishu-notify

Send notifications to Feishu/Lark.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/wanshuiyin/auto-claude-code-research-in-sleep --skill feishu-notify

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

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

json
{
  "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" valueWhat it doesRequires
Off"off" or file absentNothing. Pure CLI as-isNothing
Push only"push"Send webhook notifications at key events. Mobile push, no replyFeishu bot webhook URL
Interactive"interactive"Full bidirectional. Approve/reject from Feishu, reply to checkpointsfeishu-claude-code running

Workflow

Step 1: Read Config

bash
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:

bash
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:

EventTitleColorBody
experiment_doneExperiment CompletegreenResults table, delta vs baseline
review_scoredReview Round N: X/10blue (≥6) / orange (<6)Score, verdict, top 3 weaknesses
checkpointCheckpoint: Waiting for InputyellowQuestion, options, context
errorError: [type]redError message, what failed
pipeline_donePipeline CompletepurpleFinal summary, deliverables
customCustomblueFree-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:

  1. Send message to the bridge:
bash
   curl -s -X POST "$BRIDGE_URL/send" \
     -H "Content-Type: application/json" \
     -d '{"type": "EVENT_TYPE", "title": "TITLE", "body": "BODY", "options": ["approve", "reject", "custom"]}'
  1. Wait for reply (with timeout):
bash
   curl -s "$BRIDGE_URL/poll?timeout=$TIMEOUT_SECONDS"

Returns: {"reply": "approve"} or {"reply": "reject"} or {"reply": "user typed message"} or {"timeout": true}

  1. On timeout: Fall back to AUTO_PROCEED behavior (proceed with default option).
  1. 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:

markdown
### 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:

SkillEventWhen
/auto-review-loopreview_scoredAfter each round's review score
/auto-review-looppipeline_doneLoop complete (positive or max rounds)
/auto-paper-improvement-loopreview_scoredAfter each round's review score
/auto-paper-improvement-looppipeline_doneAll rounds complete
/run-experimentexperiment_doneScreen session finishes
/idea-discoverycheckpointBetween phases (if interactive)
/idea-discoverypipeline_doneFinal report ready
/monitor-experimentexperiment_doneResults collected
/research-pipelinecheckpointBetween workflow stages
/research-pipelinepipeline_doneFull 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.

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
wanshuiyin
コミュニティ

proof-checker

Rigorous mathematical proof verification and fixing workflow. Reads a LaTeX proof, identifies gaps via cross-model review (external reviewer backend, ultra reasoning), fixes each gap with full derivations, re-reviews, and generates an audit report. Use when user says "检查证明", "verify proof", "proof check", "审证明", "check this proof", or wants rigorous mathematical verification of a theory paper.

1時間の導入数
2
GitHub Stars
2万
更新日
11月19日
wanshuiyin
コミュニティ

pixel-art

Generate pixel art SVG illustrations for READMEs, docs, or slides. Use when user says "画像素图", "pixel art", "make an SVG illustration", "README hero image", or wants a cute visual.

1時間の導入数
2
GitHub Stars
1.9万
更新日
11月14日
wanshuiyin
コミュニティ

citation-crosscheck

Double-blind bibliographic cross-check: one agent extracts each cited entry verbatim from the local .bib, a second independently re-fetches the same paper's record from the web while blind to the .bib, and a third extractor emits a mechanical field-by-field delta to catch dropped/re-ordered authors, wrong years, wrong venues, and bad DOIs/arXiv ids. The main agent (never a shard) assigns the MATCH/MINOR/MISMATCH verdict per reference, and exports a side-by-side spreadsheet. Use when user says \"

1時間の導入数
1
GitHub Stars
1.9万
更新日
11月14日
wanshuiyin
コミュニティ

formula-derivation

Structures and derives research formulas when the user wants to 推导公式, build a theory line, organize assumptions, turn scattered equations into a coherent derivation, or rewrite theory notes into a paper-ready formula document. Use when the derivation target is not yet fully fixed, the main object still needs to be chosen, or the user needs a coherent derivation package rather than a finished theorem proof.

1時間の導入数
1
GitHub Stars
1.9万
更新日
11月14日