feishu-evolver-wrapper

Orchestrates the evolution loop with Feishu reporting, lifecycle control, and dashboards.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/dingdyan/openclaw-workspace-v2 --skill feishu-evolver-wrapper-dingdyan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feishu-evolver-wrapper
Source: https://github.com/dingdyan/openclaw-workspace-v2/tree/main/skills/feishu-evolver-wrapper
Command: npx skills add https://github.com/dingdyan/openclaw-workspace-v2 --skill feishu-evolver-wrapper-dingdyan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires dotenv, commander, and includes scripts (resource) components.

What problem does it solve?

It solves the operational problem of running the capability evolution loop while keeping Master stakeholders continuously informed with Feishu card updates, lifecycle control, and dashboards.

Core Features & Use Cases

  • Feishu reporting injection: Enables rich card reporting by managing Feishu-related environment variables for the evolver flow.
  • Evolution lifecycle management: Provides start/stop/status/ensure routines, including watchdog-driven self-healing for stuck or unhealthy runs.
  • Dashboards and history exports: Generates dashboards from recorded evolution events and exports cycle history to Feishu Docs when configured.
  • Safety and reliability guardrails: Implements a kill switch, log deduplication, secret scanning before sending cards, and optional self-repair on critical git-sync failures.

Quick Start

Run the evolution loop with Feishu reporting by executing: node skills/feishu-evolver-wrapper/index.js.

Frequently Asked Questions about feishu-evolver-wrapper

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

FAQPage Schema
How do I send evolver lifecycle status updates to Feishu interactive cards?

To send evolver lifecycle status updates to Feishu interactive cards, use this wrapper to orchestrate the evolution loop with injected Feishu reporting. It manages environment variables and pushes human-readable status updates directly to configured Master environments.

Can I automate self-healing for stuck or unhealthy evolution loop runs?

Yes, you can automate self-healing for stuck or unhealthy evolution loop runs using the built-in watchdog. The watchdog monitors runs and automatically triggers self-repair routines, including optional recovery on critical git-sync failures.

How do I generate dashboards from recorded evolution events?

You can generate dashboards from recorded evolution events by relying on local event and history assets. The wrapper processes these records to build dashboards and can export cycle history directly to Feishu Docs.

Do I need specific environment variables to enable Feishu reporting in the evolver workflow?

Yes, you need specific environment variables like FEISHU_APP_ID or related tokens to enable Feishu reporting. Proper Feishu targeting and authentication configuration is required to inject rich card reporting into the evolver workflow.

What safety guardrails are implemented when sending Feishu card updates?

Safety guardrails for sending Feishu card updates include a kill switch, log deduplication, and secret scanning before dispatch. These ensure reliable reporting and prevent sensitive data leakage during evolution lifecycle management.