lark-skill-maker

Wrap Feishu API calls into reusable Lark Skills with SKILL.md metadata.

3|1|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/HuXiangyu123/CUA-Lark-Agent --skill lark-skill-maker-huxiangyu123
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lark-skill-maker
Source: https://github.com/HuXiangyu123/CUA-Lark-Agent/tree/main/lark-cli/skills/lark-skill-maker
Command: npx skills add https://github.com/HuXiangyu123/CUA-Lark-Agent --skill lark-skill-maker-huxiangyu123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers convert Feishu API operations into reusable Lark Skills, enabling consistent automation and multi-step workflows without rewriting common logic.

Core Features & Use Cases

  • Create reusable Skill templates for Feishu API interactions via lark-cli.
  • Encapsulate atomic API calls or multi-step orchestrations for rapid deployment and sharing.
  • Version, share, and compose Skills to accelerate automation across projects.

Quick Start

Install the Skill tooling and run a sample to wrap a Feishu API call into a Lark Skill.

Frequently Asked Questions about lark-skill-maker

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

FAQPage Schema
How do I wrap Feishu API calls into a reusable automation workflow?

To wrap Feishu API calls into reusable automation workflows, use lark-cli scaffolding to define a Skill with a SKILL.md frontmatter, encapsulating single atomic calls or multi-step orchestrations for rapid deployment and sharing.

What is a Lark Skill and how does it standardize Feishu actions?

A Lark Skill is a standardized, shareable template that encapsulates Feishu API interactions, allowing teams to execute multi-step workflows consistently across projects without rewriting common logic.

Do I need lark-cli to create and scaffold a Skill for Feishu API operations?

Yes, you need lark-cli to scaffold the Skill structure, which requires defining metadata fields like name, description, and version in a SKILL.md frontmatter, alongside optional scripts, references, and assets.

What's the best way to share and version Feishu API automations across different projects?

The best way to share and version Feishu API automations is by composing them into Lark Skills, which support version tracking and sharing metadata to accelerate consistent deployment across multiple projects.

Can I compose multi-step workflows across projects using Feishu Skills?

Yes, you can compose multi-step workflows across projects by encapsulating atomic Feishu API calls into individual Lark Skills and orchestrating them together for standardized automation.