lark-apps

Create, develop, and deploy Miaoda applications via the lark-cli apps command family.

Updated May 22, 2026
One-click install
npx skills add https://github.com/CalWade/aigc-creator --skill lark-apps-calwade
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lark-apps
Source: https://github.com/CalWade/aigc-creator/tree/main/.agents/skills/lark-apps
Command: npx skills add https://github.com/CalWade/aigc-creator --skill lark-apps-calwade

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Building and shipping a Miaoda (Spark) application involves many distinct operations—creating the app asset, choosing between local full-stack development, HTML static hosting, or cloud AI generation, managing databases, and deploying releases. This Skill routes every user intent to the correct lark-cli command with the right guardrails, so nothing gets misrouted or deployed prematurely. ## Core Features & Use Cases - Intent Routing: Maps user requests (create, list, update, publish, deploy, set access scope, run SQL) to the exact lark-cli apps +<cmd> command and its detailed reference doc. - Three Development Paths: Distinguishes HTML static publishing (+html-publish), local full-stack development (+init + native git + +release-create), and cloud AI generation sessions (+session-create → +chat → +session-get polling). - Release Guardrails: Enforces that only a +release-get status of finished (with online_url) or a successful +html-publish proves deployment, preventing confusion between dev-mode links and published links. - Use Case: A user says "build me a polling tool and give me a shareable link." The Skill asks whether they prefer local coding or cloud AI generation, creates a full_stack app, drives the chosen workflow, deploys via +release-create, polls until finished, and returns the online_url. ## Quick Start Ask the assistant to create a new Miaoda app named "team poll" and deploy it so you get a shareable link.

Frequently Asked Questions about lark-apps

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

FAQPage Schema
How do I deploy a Miaoda app to get a shareable link?▼

For full-stack apps, commit and push code to the sprint/default branch, run lark-cli apps +release-create, then poll +release-get until status is finished and read the online_url. For HTML sites, run +html-publish and use the returned data.url.

How do I choose between local development and cloud AI generation in Miaoda?▼

Choose local full-stack development if you want to write code yourself in a local IDE; choose cloud sessions if you want the Miaoda AI agent to generate the app conversationally. If the user has not expressed a preference, the Skill requires asking before proceeding.

Does is_published=true mean my latest code is deployed?▼

No. The is_published flag from +list only indicates a historical release exists. To prove the latest version is live, you need a +release-get status of finished for that release_id, or a successful +html-publish response.

How do I find the app_id for an existing Miaoda app?▼

Extract it directly from a user-provided app_xxx ID or Miaoda link, read .spark/meta.json in an initialized project directory, or run lark-cli apps +list --keyword with the app name. Never pass a cli_ prefixed Feishu app ID to apps commands.

Why does +db-execute require the --yes flag?▼

The +db-execute command is classified as high-risk-write because SQL can contain DML or DDL statements. Without --yes it returns confirmation_required with exit code 10; destructive or irreversible statements should first be previewed with --dry-run.

When should I not use the lark-apps skill?▼

Do not use it for regular cloud drive file uploads (lark-drive), Feishu document editing (lark-doc), or native slide creation (lark-slides). It only covers Miaoda application development, hosting, databases, and deployment.