lark-apps

Develop, deploy, and operate Miaoda applications via the lark-cli apps command family.

Updated Sep 13, 2026
One-click install
npx skills add https://github.com/U1traVeno/skills --skill lark-apps-u1traveno
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lark-apps
Source: https://github.com/U1traVeno/skills/tree/main/profiles/lark/lark-apps
Command: npx skills add https://github.com/U1traVeno/skills --skill lark-apps-u1traveno

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires lark-cli, and includes references (resource) components.

What problem does it solve? Building and operating Miaoda (Spark) applications requires juggling many CLI commands across creation, local full-stack development, HTML publishing, cloud AI generation, databases, file storage, releases, and observability. This Skill routes each user intent to the correct lark-cli apps command with the right safety gates. ## Core Features & Use Cases - Three development paths: local full-stack development with git, HTML static site publishing, and cloud AI session-based generation, with a decision table to pick the right one. - Full app lifecycle operations: create, update, list, environment variables, database management (tables, SQL execution, import/export, audit, PITR recovery), file storage, plugins, and OpenAPI key management. - Release and observability: deploy full-stack apps with release polling, query logs, traces, runtime metrics (requests, errors, latency, CPU, memory), and PV/UV analytics. - Use Case: A user says "deploy my approval system and give me a shareable link" — the Skill resolves the app_id, commits and pushes code, creates a release, polls until finished, returns the online URL, and offers to widen the access scope. ## Quick Start Ask the assistant to create a new Miaoda app named "todo tool" 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 with lark-cli?▼

Commit and push your code to the sprint/default branch, then run lark-cli apps +release-create --app-id <id> and poll with +release-get until status is finished. The finished response contains the online_url you can share.

How do I publish an HTML page as a shareable Miaoda link?▼

Create an html-type app with +create --app-type html, then run +html-publish --app-id <id> --path ./dist. The entry file must be index.html, and the returned data.url is the published link.

How do I find the app_id for a Miaoda app?▼

Extract it directly from an app_xxx ID or Miaoda link if given, read .spark/meta.json in an initialized project, or run lark-cli apps +list --keyword "<name>" to search by name. Never use a cli_ prefixed Feishu app ID.

Can I query Miaoda app request volume, errors, and latency?▼

Yes, use +metric-list with --metric requests for total and error counts, or --metric latency for p50/p99, plus --since for the time range. For PV/UV and active users, use +analytics-list instead.

What are the limits of lark-cli for Miaoda app management?▼

lark-cli cannot configure in-app RBAC, member roles, collaborator permissions, or automation; those must be done in the Miaoda web console. The +access-scope commands only control runtime visibility of the published app.

Why does a Miaoda database command fail with a dev environment error?▼

Only apps with multi-environment enabled via +db-env-create have a dev branch; other apps store their database in online. Pass --environment online explicitly for those apps, since all db commands default to dev.