lark-skill-maker

Create new skills with standardized SKILL.md YAML frontmatter and optional metadata.

35|5|Updated May 7, 2026
One-click install
npx skills add https://github.com/yokingma/weclaws --skill lark-skill-maker-yokingma
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lark-skill-maker
Source: https://github.com/yokingma/weclaws/tree/main/resources/skills/managed/lark-skill-maker
Command: npx skills add https://github.com/yokingma/weclaws --skill lark-skill-maker-yokingma

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes how new Skills are defined by requiring a single SKILL.md with a clear name, description, and optional metadata, making discovery and reuse effortless.

Core Features & Use Cases

  • Standardized Skill entry at SKILL.md to enforce consistency.
  • YAML frontmatter supports versioning and required binaries for execution.
  • Templates and guidance to quickly scaffold new Skills for different tools and platforms.

Quick Start

Create a new skill folder, add a SKILL.md with the required frontmatter, and fill the Markdown body with operational instructions.

Frequently Asked Questions about lark-skill-maker

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

FAQPage Schema
How do I create reusable automation skills for software development teams?

You create reusable automation skills by defining a standardized SKILL.md file with YAML frontmatter specifying the name and description, making skill discovery and reuse effortless across projects.

What is the best way to standardize skill templates across different projects?

Standardizing skill templates involves using a single SKILL.md entry point with required YAML frontmatter for consistency, supporting optional metadata like versioning and required binaries for execution.

How does YAML frontmatter work in a SKILL.md file?

YAML frontmatter in a SKILL.md file works by requiring a name and description, while supporting optional metadata including version and required bins, to define execution requirements and skill characteristics.

Do I need specific directories to scaffold new skills for different platforms?

You do not need specific directories to scaffold new skills, but you can use optional directories for scripts, references, and assets to organize operational instructions and supporting files.

Can I use lark-cli to scaffold new skills with required binaries?

Yes, you can use lark-cli to scaffold new skills by defining required binaries in the YAML frontmatter of your SKILL.md, ensuring the execution environment meets the necessary dependencies.