feishu-notify

Route notifications to Feishu/Lark and capture interactive teammate responses.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/hve4638/hve-cc-marketplace --skill feishu-notify-hve4638
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feishu-notify
Source: https://github.com/hve4638/hve-cc-marketplace/tree/main/aris/skills/skills-codex/feishu-notify
Command: npx skills add https://github.com/hve4638/hve-cc-marketplace --skill feishu-notify-hve4638

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Feishu-notify provides a lightweight mechanism to send status updates and alerts to Feishu/Lark from ARIS-powered workflows, enabling teams to stay informed without logging into separate dashboards.

Core Features & Use Cases

  • Push notifications via Feishu webhook for key events (experiment results, review scores, checkpoints).
  • Interactive bidirectional alerts allowing teammates to approve/reject from Feishu.
  • Zero-impact default when config is missing; safe to enable in production without changes.

Quick Start

Configure a ~/.codex/feishu.json with your mode and webhook details, then trigger a notification from an ARIS workflow.

Frequently Asked Questions about feishu-notify

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

FAQPage Schema
How do I send Feishu webhook notifications for pipeline checkpoints?▼

To send Feishu webhook notifications for pipeline checkpoints, configure the ~/.codex/feishu.json file with your mode and webhook details, then trigger the alert from your ARIS workflow.

Can I capture interactive responses from teammates in Feishu alerts?▼

Yes, you can capture interactive responses from teammates using the bidirectional alert mode, which allows them to approve or reject ARIS workflow events directly within Feishu.

Do I need a configuration file to push alerts to Lark?▼

You do not strictly need a configuration file to push alerts to Lark; the system operates with zero-config defaults when the ~/.codex/feishu.json file is absent, ensuring safe production use.

What is the best way to notify teams about ARIS experiment results?▼

The best way to notify teams about ARIS experiment results is routing push notifications via Feishu webhooks, allowing teams to stay informed without logging into separate dashboards.

Does feishu-notify work without modifying existing production environments?▼

Feishu-notify works without modifying production environments because it applies a zero-impact default when the configuration file is missing, ensuring safe integration without code changes.

Why are my bidirectional Feishu alerts not working?▼

Bidirectional Feishu alerts may not work if the local ~/.codex/feishu.json config is missing or improperly configured to enable the interactive response mode for your ARIS events.