larc-runtime

Orchestrate governed Feishu/Lark tasks through LARC queue and gate controls.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ShunsukeHayashi/lark-harness --skill larc-runtime
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: larc-runtime
Source: https://github.com/ShunsukeHayashi/lark-harness/tree/main/openclaw-larc-runtime
Command: npx skills add https://github.com/ShunsukeHayashi/lark-harness --skill larc-runtime

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Governing OpenClaw-driven tasks for Lark/Feishu requires centralized control over the action lifecycle to prevent unsafe direct API calls, ensuring auditable, repeatable workflows. The skill routes actions through LARC's queue and gate system and coordinates lifecycle transitions so operations stay within governance policies.

Core Features & Use Cases

  • Centralized governance: uses LARC to fetch the next action bundle, apply gate rules, and route actions through the official openclaw-lark plugin for execution.
  • Safe state management: enforces explicit transitions via larc ingress done|fail|followup, ensuring traceable task lifecycles.
  • Clear role separation: LARC handles orchestration (queue, permission, lifecycle) while the official plugin performs Feishu/Lark operations.
  • Addness integration: coordinates coding goals with operation tasks and progress tracking.
  • Use Case: When a governed Feishu task is ready, fetch the next action, read context if needed, and execute through the plugin with governance controls, then update status.

Quick Start

Invoke the larc ingress openclaw flow to fetch the next action bundle and begin its lifecycle under LARC governance.

Frequently Asked Questions about larc-runtime

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

FAQPage Schema
How do I enforce approval gates for Feishu or Lark tasks in OpenClaw workflows?

To enforce approval gates for Feishu or Lark tasks, you route actions through LARC governance, which applies queue and gate rules before operations are executed via the openclaw-lark plugin.

What is LARC governance for Feishu task orchestration?

LARC governance is a centralized control system that manages the action lifecycle of Feishu tasks, preventing unsafe direct API calls by enforcing queue, permission, and state transition rules.

How do I safely manage state transitions for Lark operations without direct API calls?

You manage state transitions safely by using explicit LARC ingress commands like done, fail, or followup, ensuring every task lifecycle remains traceable and governed before plugin execution.

Does LARC orchestration replace the official openclaw-lark plugin?

LARC orchestration does not replace the openclaw-lark plugin; LARC handles queue and lifecycle governance while the official plugin executes the actual Feishu and Lark operations.

How do I start a governed Feishu task using LARC queue management?

To start a governed Feishu task, invoke the LARC ingress openclaw flow to fetch the next action bundle and begin its lifecycle under LARC queue and gate governance.

What limitations exist when separating LARC orchestration from Lark operations?

A key limitation is maintaining strict separation of responsibilities; LARC must only handle orchestration and state updates, while the openclaw-lark plugin must perform all direct Feishu or Lark API operations.