feishu-notify

Send notifications and alerts to Feishu/Lark via webhook.

Updated May 22, 2026
One-click install
npx skills add https://github.com/Leo1349/autoresearch --skill feishu-notify-leo1349
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feishu-notify
Source: https://github.com/Leo1349/autoresearch/tree/main/skills/feishu-notify
Command: npx skills add https://github.com/Leo1349/autoresearch --skill feishu-notify-leo1349

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill resolves the issue of efficient communication and status updates within the ARIS ecosystem by providing a robust way to send notifications via Feishu/Lark.

Core Features & Use Cases

  • Notification Delivery: Send messages, updates, and alerts directly to Feishu/Lark.
  • Push & Interactive Modes: Supports both push-only and bidirectional interactive notifications.
  • Internal Utility: Designed for internal use by other ARIS skills but can be manually invoked.
  • Zero-Impact Guarantee: Functions silently if Feishu/Lark configuration is not present.

Quick Start

Send a notification to Feishu/Lark with the command: /feishu-notify "Your message here."

Frequently Asked Questions about feishu-notify

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

FAQPage Schema
How do I send notifications to Feishu or Lark from my research workflows?

To send Feishu or Lark notifications, use a dedicated system that delivers messages and alerts directly to your platform via a configured webhook. Invoke the command with your desired message text.

Do I need a webhook to send status updates to Feishu?

Yes, a configured Feishu or Lark webhook is required to deliver status updates and alerts. Without this configuration, the notification system functions silently with zero impact on your workflows.

Can I use Feishu notifications for bidirectional interactive communication?

Yes, Feishu notifications support bidirectional interactive communication when you connect an optional MCP server. Without the MCP server, the system operates in a standard push-only mode for alerts.

What happens if my Feishu or Lark configuration is missing?

If your Feishu or Lark configuration is missing, the notification system provides a zero-impact guarantee and functions silently. It ensures your internal research workflows continue running without generating errors.

How do I manually trigger a Lark notification for internal communication?

You manually trigger a Lark notification for internal communication by executing the notify command followed by your message string. The system processes the script component and pushes the alert to your Lark channel.