Individual skill
lark-shared
【何时用:在其他 lark-* 技能遇到认证/授权/身份/配置问题、被要求前置读取,或首次使用 lark-cli 时;泛指需求默认走本地工具】lark-cli 共享规则:首次配置(config init)、认证登录(auth login --domain/--scope,split-flow)、登录态查询与撤销(auth status/logout/whoami)、--as user/bot 身份切换、权限不足与 missing_scope 处理、JSON 输出契约与 _notice、update 更新、高风险操作审批(exit 10)。
pinvou3-app/src-tauri/resources/common/bundle/lark-skills/lark-shared/SKILL.md
Source commit 3cec34e2b6b7da8fbb85b70050dae83ff8b4ee10
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 2, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 2,921
- Repository last updated
- Nov 7, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agent Repository topic
- automation Repository topic
- desktop-app Repository topic
- llm Repository topic
- local-first Repository topic
- mcp Repository topic
- open-source Repository topic
- react Repository topic
- rust Repository topic
- tauri Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 5,051 bytesreferences/lark-shared-config-init.mddoc · 980 bytesreferences/lark-shared-high-risk-approval.mddoc · 2,070 bytesreferences/lark-shared-identity-and-permissions.mddoc · 5,805 bytesreferences/lark-shared-output-contract.mddoc · 933 bytesreferences/lark-shared-update-notice.mddoc · 1,201 bytesreferences/lark-wiki-token-routing.mddoc · 2,488 bytes
Read excerpt
# 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)。
