Set up Feishu/Lark after installing feishu2codex: install the official lark-cli runtime if missing, initialize app configuration, start browser/device OAuth, and verify the signed-in account.
3 stars
0 votes
0 copies
4 views
Added September 12, 2026
ai-agentsrustgobashnodegit
Works with
cli
Security analysis
A96/100
mediumInstalls packages at runtime which could introduce malicious dependencies
Installs into .claude/skills of the current project.
Are you the author of Lark Setup?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/thedixitjain-lark-setup)
---
name: lark-setup
description: "Set up Feishu/Lark after installing feishu2codex: install the official lark-cli runtime if missing, initialize app configuration, start browser/device OAuth, and verify the signed-in account."
category: ai-agents-and-harness
source_repo: hashgraph-online/awesome-codex-plugins
source_path: "plugins/zlsbksdxl/codex-lark/skills/lark-setup/SKILL.md"
source_url: https://github.com/hashgraph-online/awesome-codex-plugins/blob/HEAD/plugins/zlsbksdxl/codex-lark/skills/lark-setup/SKILL.md
---
# Set up Feishu/Lark
Use this workflow when the user installs `feishu2codex`, asks to connect Feishu/Lark, or a bundled Lark skill cannot run because `lark-cli` is missing or unauthenticated.
## 1. Ensure the official runtime exists
The plugin's trusted `SessionStart` hook normally installs the matching runtime before this Skill runs. Check the result without changing state:
```bash
command -v lark-cli && lark-cli --version
```
If `lark-cli` is still missing, verify that `npm` is available, then install the runtime version matching the bundled Skills:
```bash
npm install --global --no-audit --no-fund @larksuite/cli@1.0.73
```
Run `lark-cli --version` again and require version `1.0.73` before continuing. If `npm` is unavailable, tell the user that Node.js/npm is required and stop before attempting authentication.
## 2. Configure and authenticate
Read the sibling `../lark-shared/SKILL.md` completely, then follow its configuration and split OAuth flow exactly. In particular:
- initialize missing app configuration with `lark-cli config init --new`;
- prefer least-privilege domain or scope authorization for the user's intended workflow;
- return the unmodified verification URL and generate the required QR code;
- never print app secrets, access tokens, device codes, or stored credentials;
- verify completion with `lark-cli auth status --json --verify`.
Do not claim setup is complete until the verification response reports a valid signed-in user identity.
---
**Source:** [`hashgraph-online/awesome-codex-plugins`](https://github.com/hashgraph-online/awesome-codex-plugins) → `plugins/zlsbksdxl/codex-lark/skills/lark-setup/SKILL.md`
