Documents & Data · IN-DEPTH PROFILE

Lark Apps Skill

Lark Apps is the broad development and hosting workflow for Feishu Miaoda applications.

View listed source ↗Installation guide ↓
Best for

Teams building and hosting Miaoda applications

What you get

Build through the right path + Operate application services

Main limitation

It does not replace lark-drive, lark-doc, or lark-slides for ordinary Drive files, native documents, or native presentations.

First risk

Production, data, access, and credential changes. Releases, SQL, recovery, file deletion, visibility, roles, API-key reset, automations, and whole-environment cache clears can affect users and data. Preview consequential actions and obtain explicit confirmation before clearing an environment or performing any high-risk write.

EVIDENCE FRESHNESS

Three checks, kept separate

A recent source check is not a runtime test or security audit.

Upstream sourceChecked 2026-09-23

Pinned revision · a079fd7a

Open pinned commit ↗
SkillSignal profileSource-grounded

Updated 2026-08-20

Runtime & securityNot independently verified

Source review does not certify behavior or safety.

IN PLAIN ENGLISH

What it does—and when it fits

Lark Apps is the broad development and hosting workflow for Feishu Miaoda applications. Using user identity, it routes between local source development and cloud AI generation, and covers app creation, creative HTML experiences, releases, databases, files, cache, observability, environment variables, collaborators, roles, API keys, plugins, and automation triggers.

This is aimed at Teams building and hosting Miaoda applications. Compare the examples below with your task, then review the limitations, permissions, and risks before installing.

What you get
  • Build through the right pathCreate or find an app, then use local Git development or a cloud generation session by intent.
  • Operate application servicesManage releases, logs, traces, metrics, database environments, files, cache, and runtime variables.
  • Govern access and automationConfigure visibility, collaborators, app roles, API credentials, plugins, and scheduled or event triggers.
What makes it different
  • This profile is manually organized around the current upstream SKILL.md workflow.
  • The capability boundary remains explicitly tied to open.feishu.cn.
  • Core uses, limitations, and risks are separated for pre-install review.
Community signalskills.sh All-time: #52 · 638.8K installs

No verified review text is in the current dataset. Use the linked source for the latest discussion.

Read the source note ↗

INSTALL BY AGENT

Choose your Agent

Paths come from official Agent docs or the universal installer behind skills.sh. Compatibility still follows this Skill's record.

Native

This Skill's current record explicitly names this Agent. Still inspect scripts, permissions, and external dependencies first.

Project install (recommended)
npx skills add larksuite/cli --skill lark-apps --agent claude-code
Personal install
npx skills add larksuite/cli --skill lark-apps --agent claude-code -g

Project install stays with this repository for team sharing. Personal install adds -g and works across repositories.

This command adds the Skill instructions only. Install lark-cli and sign in to Feishu separately before use. Official Lark CLI setup ↗

View install paths
Project path.claude/skills/lark-apps/
Personal path~/.claude/skills/lark-apps/
Official agent docs

Claude Code discovers custom Skill folders automatically at project or personal scope.

View path evidence ↗

TYPICAL WORKFLOW

A practical workflow

01

Build through the right path

Create or find an app, then use local Git development or a cloud generation session by intent.

02

Operate application services

Manage releases, logs, traces, metrics, database environments, files, cache, and runtime variables.

03

Govern access and automation

Configure visibility, collaborators, app roles, API credentials, plugins, and scheduled or event triggers.

THE TRADEOFFS

Advantages and tradeoffs

Notable strengths

  1. This profile is manually organized around the current upstream SKILL.md workflow.
  2. The capability boundary remains explicitly tied to open.feishu.cn.
  3. Core uses, limitations, and risks are separated for pre-install review.

Limitations

  1. It does not replace lark-drive, lark-doc, or lark-slides for ordinary Drive files, native documents, or native presentations.
  2. The local and cloud development paths have different commands, artifacts, and release rules and should not be mixed casually.

COMPARE THE TRADEOFF

Consider these close alternatives

These are deterministic nearby candidates, not paid placements or a universal ranking. Open the full profile before choosing.

01

Same job family · native to Codex + Claude Code

create-llms

Create an llms.txt index from repository documentation.
Tradeoff to check
Detailed package files are not fully catalogued.
First risk
Review before install · Medium
Source state
Pinned · 1f564408
Open create-llms profile ↗
02

Same job family · native to Codex + Claude Code

csharp-docs

Write useful XML documentation for C# APIs.
Tradeoff to check
Detailed package files are not fully catalogued.
First risk
Review before install · Medium
Source state
Pinned · 1f564408
Open csharp-docs profile ↗
03

Same job family · native to Codex + Claude Code

java-docs

Write consistent Javadoc for Java types and APIs.
Tradeoff to check
Detailed package files are not fully catalogued.
First risk
Review before install · Medium
Source state
Pinned · 1f564408
Open java-docs profile ↗
Compare more in the directory →

BEST FIT

Who it is for

→

Teams building and hosting Miaoda applications

→

Feishu developers operating full application lifecycles

BEFORE YOU USE IT

Risks to review before use

High

Production, data, access, and credential changes

Releases, SQL, recovery, file deletion, visibility, roles, API-key reset, automations, and whole-environment cache clears can affect users and data. Preview consequential actions and obtain explicit confirmation before clearing an environment or performing any high-risk write.

High

External data and identity boundary

Requests access Feishu tenant resources. Use the correct identity, least-privilege scopes, and keep sensitive content out of logs.

SECURITY

What the permission profile means

  • Declared access remains governed by the current upstream SKILL.md and runtime requests.
  • Treat Feishu documents, messages, people, and business records as permission-controlled data.
  • SkillSignal has not independently executed or security-audited this package; external skills.sh labels are not SkillSignal certification.

Not a security certification. External ratings are attributed references. SkillSignal has not independently executed or security-reviewed this Skill.

COMMON QUESTIONS

Lark Apps Skill FAQ

What is the Lark Apps Skill?

Lark Apps is the broad development and hosting workflow for Feishu Miaoda applications. Using user identity, it routes between local source development and cloud AI generation, and covers app creation, creative HTML experiences, releases, databases, files, cache, observability, environment variables, collaborators, roles, API keys, plugins, and automation triggers.

How do I install the Lark Apps Skill?

Open and review the listed source, choose the project or personal path for your Agent, then verify the first run in a controlled project. Open the listed source and read the current SKILL.md plus only the references required for this task.

Is the Lark Apps Skill safe to use?

SkillSignal checked the source on 2026-09-23, but that is not a runtime test or security certification. Review the “Production, data, access, and credential changes” risk first and begin with the least access required.

INSIDE THE PACKAGE

Indexed files

SKILL.mdUpstream Skill instructionsSource-linked

TAGS

feishumiaodaapp-platform

Manually expanded from the current upstream SKILL.md and linked source at open.feishu.cn, checked 2026-08-24. This is an original summary, not an execution result or security certification.