Security / AGENT SKILL

lark-shared

open.feishu.cn

720.8K installs

Configure Lark CLI authentication, identities, permissions, scopes, and authorization revocation.
Use for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handling _notice JSON.

One new superpower.

Run this command in your project to choose an agent and install the skill.

npx skillycli add https://open.feishu.cn/ --skill lark-sharedView original source

BEFORE YOU INSTALL

Understand the trade-offs.

SECURITY REVIEW

Review incomplete

The available checks do not support a complete conclusion. Review the scope before relying on this result.

No reported risk0 reported findingsIncomplete evidence

Scope & how to read this review

Static inspection of the supplied skill source. “Complete” means the selected source and checks completed; it does not cover every downloaded package, external service, or runtime action.

Source coverage: partial
Reviewed: 2026-10-07
Reviewed version: sha256:1bbfd
Latest catalog version: sha256:1bbfd

The reported findings score starts at 100 and subtracts 35 for each critical finding, 20 for high, 9 for medium, and 3 for low, with a floor of 0. It is shown only for complete, current reviews with all finding details. A score of 100 means no findings were reported in the reviewed source.

Severity describes potential impact, not the probability of harm. Review the conditions and evidence for each finding. A scan is not a safety guarantee.

SKILL QUALITY

Limited evidence for a verdict

50/100Provisional source score

The supplied skill provides concrete shared rules for lark-cli identity, output handling, authorization links, and confirmation retries. It is useful as a routing and conventions layer, but the omitted mandatory references prevent assessment of complete setup and authentication workflows.

low confidenceStatic reviewIntegration skill

The reviewer had limited evidence. These scores describe what was available, not a verified measure of reliability.

What works well

Clearly identifies when each reference must be consulted and specifies reading order.
Provides concrete success indicators, path constraints, and retry behavior.
Explains an identity-related empty-result case that could otherwise be mistaken for successful resource discovery.

Before you rely on it

Supply the five mandatory reference files so their procedures and consistency can be assessed.
Document complete setup and authentication examples, including prerequisites, domain selection, missing-scope recovery, and logout or revocation.
Add representative output fixtures and observable acceptance criteria for authentication, identity selection, notices, and confirmation retries.

Clear instructionsCan your agent understand the task and expected outcome?3/4

The purpose, behavioral rules, and reference triggers are clear. Full outcomes for the advertised authentication and permission tasks depend on unavailable references.

EVIDENCE

SKILL.md: "命中任一触发条件时，**MUST 在执行下一步前读取对应 reference**。命中多条时按表中顺序读取，同一reference只读取一次。"

To improve: State the expected end state for each supported setup, authentication, permission, and notice task.

Complete workflowAre prerequisites, failure cases, and recovery covered?2/4

The file includes useful edge cases and an ordered confirmation-retry procedure, but installation prerequisites and complete authentication workflows are not present in the supplied evidence.

EVIDENCE

SKILL.md: "停下 → **向用户确认**（展示 `action`、`risk` 和关键参数）→ 取得**用户显式同意**后，将 `hint` 指出的确认 flag **追加到你原始 argv 的末尾**后重试"

To improve: Supply the referenced procedures with prerequisites, ordered commands, and recovery paths for expired login, missing scopes, and configuration failures.

Repeatable resultsAre examples and dependencies specific enough to repeat the work?2/4

Specific flags, field names, exit codes, and path rules reduce ambiguity. There are no complete worked command sequences or documented CLI compatibility boundaries in the supplied file.

EVIDENCE

SKILL.md: "`--file`、`--output`、`--output-dir`、`@file` 等路径参数只接受 cwd 下的相对路径，传绝对路径会报 `unsafe file path`。"

To improve: Add copyable command sequences with explicit input assumptions and expected outputs, and identify the CLI versions supporting these contracts.

Checkable outcomesCan you tell whether the task succeeded?2/4

Explicit success indicators and recognizable failure conditions provide some observable checks. No supplied examples or fixtures verify complete setup, login, permission, or notice outcomes.

EVIDENCE

SKILL.md: "判断成功用 `ok == true`（或进程退出码 0），不要用 `code == 0`"

To improve: Provide success and failure output examples plus task-level checks, such as confirming the intended identity and granted domains after login.

Supporting filesDo the supplied scripts and references support the workflow?1/4

The reference index describes a purposeful supporting structure, but none of its mandatory files were supplied. Their content and alignment with SKILL.md cannot be assessed.

EVIDENCE

SKILL.md: "JSON 输出契约 → [`lark-shared-output-contract.md`](references/lark-shared-output-contract.md)。" Supporting reference contents were not available.

To improve: Include all five linked references and check that their commands, output fields, and recovery procedures agree with the shared rules.

Review scope & scoring

Scores describe source evidence: 0 absent or contradicted, 1 weak, 2 incomplete, 3 solid, 4 strong. Supporting files are excluded when not applicable. Instruction skills can demonstrate quality through examples and checkable outcomes without executable tests.

Provisional source score: 50/100
Files reviewed: 1
Source coverage: skill only
Reviewed: 2026-10-06
Rubric: 2026-09-25-v3
Assessed version: sha256:1bbfd
Latest catalog version: sha256:1bbfd

Review limitations

Coverage is explicitly skill-only; all five referenced documents are unavailable.
This assessment is static and does not establish runtime behavior or CLI compatibility.
Safety rules were assessed as procedural guidance, not as proof of implementation quality.

This review does not execute the skill or verify runtime results. Install counts and publisher reputation do not increase the score.

The full skill.

Original instructions from the publisher’s SKILL.md

# lark-cli 共享规则

所有 `lark-*` skill 共享的底座：身份、认证、输出契约与高风险操作。

## 通用准则

1. **调用前先确认用法**：执行前读对应 reference 或跑 `--help`，别猜 flag 盲调。

2. **身份决定你代表谁操作**：`--as user` 代表用户本人（能看到、也能操作其日历、云空间/云盘/云存储等个人资源），`--as bot` 代表应用自己，应用级操作，只能访问bot自己的资源，bot 查用户资源会返回空成功而非报错。动手前先搞清楚身份`identity`。身份模型和权限管理 → [`lark-shared-identity-and-permissions.md`](references/lark-shared-identity-and-permissions.md)。

3. **授权 / 配置类 URL 必须配二维码**：当命令输出 `verification_url`、`verification_uri_complete`、`console_url` 等 URL 字段时，必须用 `lark-cli auth qrcode` 生成并在回复中展示，URL 在前二维码在后；优先生成 PNG（`--output`），仅当用户明确要求时才使用 ASCII（`--ascii`）。URL 原样转发——不编解码、不加标点、不重拼 query，二维码和链接请一起展示给用户。

4. **`--format json`（默认）下，判断成功用 `ok == true`（或进程退出码 0），不要用 `code == 0`**：成功信封没有顶层 `code` / `msg` 字段，`code` 只出现在错误信封的 `error` 内。按 OpenAPI 老格式 `{"code": 0, "msg": "ok"}`判断会把所有成功调用误判为失败——封装写入类命令时尤其危险。JSON 输出契约 → [`lark-shared-output-contract.md`](references/lark-shared-output-contract.md)。


## 安全规则

1. **禁止输出密钥**（appSecret、accessToken等）到终端明文。

2. **写入/删除操作前必须确认用户意图**。

3. 目标命令支持 `--dry-run` 时，用 `--dry-run` 预览危险请求。

4. **退出码 10 是高风险确认门禁（`risk: "high-risk-write"`），不是错误**：停下 → **向用户确认**（展示 `action`、`risk` 和关键参数）→ 取得**用户显式同意**后，将 `hint` 指出的确认 flag **追加到你原始 argv 的末尾**后重试；**绝不**静默加确认 flag 绕过 → [`lark-shared-high-risk-approval.md`](references/lark-shared-high-risk-approval.md)。

5. **文件路径只接受相对路径**：`--file`、`--output`、`--output-dir`、`@file` 等路径参数只接受 cwd 下的相对路径，传绝对路径会报 `unsafe file path`。数据输入（`@file`、大 JSON）优先用 stdin 传入，避免路径和转义问题。


## Reference 强触发索引

命中任一触发条件时，**MUST 在执行下一步前读取对应 reference**。命中多条时按表中顺序读取，同一reference只读取一次。

| 强触发条件（命中任一即必读） | Reference |
|---|---|
| 查看自己是谁(user/bot)、获取当前身份详细字段信息、身份诊断、`--as`选择逻辑、身份延续、登录态、认证、scope、授权和权限管理、`missing_scopes` 或 `console_url`、Agent 准备发起或完成 `auth login` | [`lark-shared-identity-and-permissions.md`](references/lark-shared-identity-and-permissions.md) |
| 需要依赖 JSON 输出契约判断成功 / 失败、读取 stdout / stderr，或为命令编写脚本与封装 | [`lark-shared-output-contract.md`](references/lark-shared-output-contract.md) |
| 准备执行high-risk-write(高风险操作)、判断命令风险等级、遇到退出码 exit 10、`confirmation_required`、确认后重试 | [`lark-shared-high-risk-approval.md`](references/lark-shared-high-risk-approval.md) |
| 首次使用CLI需运行 `lark-cli config init` 完成应用配置、或 CLI 明确提示 `config init --new` | [`lark-shared-config-init.md`](references/lark-shared-config-init.md) |
| 用户询问 notice、CLI版本更新、或输出含 `_notice`（升级 / skills 落后 / 废弃命令提示）| [`lark-shared-update-notice.md`](references/lark-shared-update-notice.md) |