CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

lark-apps

妙搭(Spark/Miaoda)应用开发与托管:应用创建、本地全栈开发、云端生成迭代、创意设计(UI mockup / 可交互原型 / 线框图 / 落地页 / 仪表盘 / 幻灯片 deck / 视觉探索)、AI相关能力和飞书平台能力或者其他外部能力集成、日志/Trace/监控指标/PV/UV 查询、环境变量管理、应用协作者与协作权限设置、应用角色与成员管理、自动化触发器(定时/记录变更/Webhook/飞书审批)。当用户要开发/新建一个系统·工具·平台·应用,或要本地开发 / 云端开发 / 修改 / 部署 / 发布 / 上线 / 拿可分享链接,或用 HTML 做页面·网站·部署到妙搭,或要设计 / design / mockup / prototype / wireframe / 做 PPT / deck / 视觉探索,或提到妙搭/Spark/Miaoda 应用(链接形如 `/app/app_xxx` 或 `/page/<token>`,运行时域名形如 *.feishuapp.com)、应用数据库、应用文件存储、开放 API Key、可见范围、应用协作者/开发权限、应用角色/角色成员、线上日志、接口请求量、错误量、延迟、访问量、环境变量、给妙搭应用配自动化任务/定时触发/审批通过后自动触发时使用。不负责普通云盘文件上传(lark-drive)、飞书文档编辑(lark-doc)、原生幻灯片创建(lark-slides)。

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A strong router-style SKILL.md: commands are copy-paste executable, workflows are explicitly sequenced with thorough validation and confirmation gates for destructive operations, and nearly all domain detail is properly deferred to a well-organized references/ directory. The main weaknesses are a missing core bundle file for the creative-design path (a dead link for the entire html app_type), an inlined member-management section inconsistent with the file-per-domain pattern, and duplicated +delete confirmation rules that add token weight.

Suggestions

Add the missing creative-design/creative-design.md to the bundle (or repoint the four references in the 意图路由 table, the app_type 判定表, and the html 主链路 bullet to its actual location) — the app_type=html routing currently dead-ends.

Move the「应用协作者与协作权限设置」section's detail into a references/lark-apps-member.md file (matching the cache/db/env/role pattern), keeping only the routing row and the top risk rules in SKILL.md.

In the access-scope routing row, replace the vague "对应 access-scope reference" with explicit links to references/lark-apps-access-scope-get.md and references/lark-apps-access-scope-set.md, and deduplicate the +delete confirmation protocol between the routing table and「禁止预授权判定底线」②.

DimensionReasoningScore

Conciseness

The body is a dense router that assumes Claude's competence and defers domain detail to references, with no explanation of concepts Claude already knows. Not 5: the +delete confirmation rules are fully duplicated (the routing-table row and "禁止预授权判定底线"② both spell out the same show-then-wait-for-confirmation protocol), the member-management section inlines reference-grade detail, and ② is a single sprawling multi-clause paragraph that could be split and tightened.

4 / 5

Actionability

Fully executable, copy-paste-ready commands throughout: "lark-cli apps +member-add --app-id <app_id> --member-type openid --member-id ou_xxx --perm view --dry-run --as user", "lark-cli apps +get --app-id <meta_token> -q '.data.app.app_id'", "lark-cli apps +metric-list --app-id <app_id> --metric requests --since <range> --as user", with concrete error subtypes ("missing_scope", "feature_not_available", OpenAPI code 3340005) and exact typed-ID examples (ou_/oc_/od-). Common cases are covered with specific flag guidance (e.g., "不传 --series 会同时返回 total/error").

5 / 5

Workflow Clarity

Multi-step processes are explicitly sequenced with validation checkpoints: "进意图路由前先判这步" orders dev-path selection before routing; app_id resolution is an ordered 1-2-3 fallback; release flow specifies polling "+release-get 轮询 finished 给 online_url / failed 给 error_logs" with the PENDING/approval rule; git failures have a feedback loop ("先执行 lark-cli apps +git-credential-init…再重试原 git 命令…如果刷新凭证也失败,停止并向用户报告"). Destructive and batch operations (+delete, +env-delete, +cache-clear, DB ops, batch member removal) all carry explicit --dry-run/confirmation gates, so the destructive-ops validation cap does not apply.

5 / 5

Progressive Disclosure

Structure is mostly excellent — 33 real one-level-deep reference files clearly signaled via the routing table's "按需读取" column — but the bundle check finds real defects: "creative-design/creative-design.md" is the designated load target for all four mentions of the html/creative path (one of three app_types) yet does not exist in the bundle, a dead end for a primary use case; the "应用协作者与协作权限设置" section inlines ~15 lines of reference-grade detail that every other domain (cache, db, env, role) keeps in its own references/ file; and one routing row says "对应 access-scope reference" without naming the actual files. Not 4 because a broken core reference is more than a minor organization gap; not 2 because the remaining 30+ intents route cleanly to well-organized, clearly signaled files.

3 / 5

Total

17

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplary description: it enumerates concrete capabilities, gives an explicit "when to use" clause with natural trigger phrasing in both Chinese and English, defines recognition tokens (ID formats, link shapes, domains), and closes with explicit scope boundaries against sibling skills. It is long, but every clause is load-bearing capability or trigger information rather than padding.

DimensionReasoningScore

Specificity

Lists many concrete, domain-specific actions — "应用创建、本地全栈开发、云端生成迭代、创意设计(UI mockup / 可交互原型 / 线框图 / 落地页 / 仪表盘 / 幻灯片 deck / 视觉探索)…日志/Trace/监控指标/PV/UV 查询、环境变量管理、应用协作者与协作权限设置、应用角色与成员管理、自动化触发器(定时/记录变更/Webhook/飞书审批)" — comprehensively covering the skill's entire command surface. Not 4: coverage has no discernible gaps; every major capability group from the body's routing table is named.

5 / 5

Completeness

Explicitly answers both: what ("应用开发与托管:应用创建、本地全栈开发…自动化触发器…") and when ("当用户要开发/新建…或提到妙搭/Spark/Miaoda 应用…时使用"), with concrete trigger phrases, and additionally states explicit non-goals ("不负责普通云盘文件上传(lark-drive)、飞书文档编辑(lark-doc)、原生幻灯片创建(lark-slides)"). This matches the anchor-5 example pattern exactly.

5 / 5

Trigger Term Quality

Comprehensive natural-language triggers users would actually say: "开发/新建一个系统·工具·平台·应用", "部署 / 发布 / 上线 / 拿可分享链接", "做 PPT / deck", "design / mockup / prototype / wireframe", "接口请求量、错误量、延迟、访问量", plus concrete recognition tokens like "/app/app_xxx", "/page/<token>", "*.feishuapp.com", and "定时触发/审批通过后自动触发". Chinese and English synonyms are both covered; nothing common is missing.

5 / 5

Distinctiveness Conflict Risk

Clear niche (妙搭/Spark/Miaoda app assets) with distinct triggers — app_id format "app_xxx", link shapes "/app/app_xxx" and "/page/<token>", runtime domain "*.feishuapp.com" — and it actively disambiguates against adjacent skills (lark-drive, lark-doc, lark-slides) and warns that /page/ links look like Feishu doc links but are not. Minimal conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

75%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 3 missing, 4 suspicious

Warning

Total

12

/

16

Passed

Repository

larksuite/cli

Path

skills/lark-apps/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.