feishu-notify

Send Feishu/Lark notifications via webhook or interactive modes.

2|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/chenghaoYang/auto-coder-trainer --skill feishu-notify-chenghaoyang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feishu-notify
Source: https://github.com/chenghaoYang/auto-coder-trainer/tree/main/aris/skills/feishu-notify
Command: npx skills add https://github.com/chenghaoYang/auto-coder-trainer --skill feishu-notify-chenghaoyang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Send notifications to Feishu/Lark. Internal utility used by other skills, or manually via /feishu-notify. Supports push-only (webhook) and interactive (bidirectional) modes. Use when user says "发飞书", "notify feishu", or other skills need to send status updates.

Core Features & Use Cases

  • Internal utility for ARIS workflow notifications.
  • Push-only webhooks for automated alerts; interactive mode for confirmations.
  • Zero-impact fallback when config is missing; skills remain unaffected.

Quick Start

Instruct the Feishu notifier to dispatch a status update to Feishu for the current 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 notifications from an automated workflow?

You can send Feishu notifications from automated workflows by configuring a webhook URL for push-only automated alerts, or by enabling interactive bidirectional mode for confirmations. The notifier acts as an internal utility invoked by other skills.

Can I send Lark alerts without blocking my current workflow process?

Yes, sending Lark alerts never blocks your workflow. The notifier enforces zero-overhead fallback when configuration is missing, ensuring your skills and workflows remain completely unaffected by notification failures.

What is the difference between push-only and interactive Feishu notification modes?

Push-only mode uses webhooks to send automated one-way alerts to Feishu, while interactive mode enables bidirectional communication for confirmations. Both modes are configurable and stored in a local configuration file.

Do I need a configuration file to push webhook alerts to Feishu?

You need a configuration file stored locally to define your webhook and mode settings. However, if no config exists, the notifier enforces a zero-impact fallback, meaning alerts simply do not fire without breaking your workflow.

How do I trigger a Feishu status update manually during a task?

You can trigger a Feishu status update manually by instructing the notifier to dispatch a message for the current workflow. It responds to direct commands like sending a status update to Feishu.