lark-skill-maker

Wrap Feishu API tasks into reusable Skills for the Lark CLI.

Updated Feb 14, 2026
One-click install
npx skills add https://github.com/liutao96/skill --skill lark-skill-maker-liutao96
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lark-skill-maker
Source: https://github.com/liutao96/skill/tree/main/lark-skill-maker
Command: npx skills add https://github.com/liutao96/skill --skill lark-skill-maker-liutao96

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Wraps Feishu API tasks into reusable Skills for the Lark CLI.

Core Features & Use Cases

  • Encapsulates single or multi-step CLI workflows that wrap Feishu API calls into shareable Skills.
  • Uses a single SKILL.md as the entry point to drive AI-assisted task execution.
  • Provides a clear template and workflow for defining name, description, and required metadata to standardize Skill creation.

Quick Start

Create a new Skill by adding a SKILL.md at the skill root that defines name, description, and required metadata.

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 Lark CLI Skill?

To wrap Feishu API calls into a reusable Skill, create a SKILL.md file at the skill root directory with the required name and description frontmatter metadata to drive AI-assisted execution.

What do I need to start building a Lark CLI Skill for Feishu API workflows?

You need a SKILL.md file at the skill root directory containing required name and description frontmatter metadata to start building a Lark CLI Skill for Feishu API workflows.

Can I include multi-step CLI workflows and custom scripts in a packaged Feishu Skill?

Yes, you can encapsulate single or multi-step CLI workflows in a packaged Feishu Skill, optionally supporting custom scripts, references, and assets alongside the required SKILL.md file.

What is the best way to standardize Feishu API task automation into shareable units?

The best way to standardize Feishu API task automation is to use a SKILL.md entry point that defines required metadata to package CLI workflows into shareable units.

Are there limitations when using a single SKILL.md file to package Feishu API workflows?

The limitation is that packaging Feishu API workflows requires a SKILL.md file as the mandatory entry point; without proper frontmatter metadata defining the name and description, the AI-assisted execution cannot proceed.

Does Lark CLI support encapsulating multi-step OpenAPI workflows into shareable units?

Yes, Lark CLI supports encapsulating single or multi-step OpenAPI workflows into shareable units by defining a SKILL.md file at the skill root with required metadata to drive task execution.