Lark CLI Shared Foundation
Auth, identity, permissions and safety rules shared by every lark-cli skill
- What
- Auth, identity, permissions and safety rules shared by every lark-cli skill
- Cost
- Free
- Needs
- a Muse account with skill installation enabled
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — the shared foundation every other lark-* skill builds on: `lark-cli` setup and auth (login, status, logout), the user-vs-bot identity model, business-domain permissions and missing-scope repair, QR-code generation for authorization URLs, the JSON output contract, and explicit safety rules — never print secrets to the terminal, always confirm user intent before write/delete operations. Read this one first; the other skills defer to it on any auth, identity, or scope error. By @larksuite, listed here with credit to its creator. Honest caveats: the underlying skill documentation is written in Chinese; you need a Feishu/Lark account with API access and the lark-cli binary installed; this is plumbing, not a feature — its value is making the other 17 Lark skills work safely. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: a Muse account with skill installation enabled Install "Lark CLI Shared Foundation" for me. Auth, identity, permissions and safety rules shared by every lark-cli skill Repository: https://github.com/larksuite/cli/blob/main/skills/lark-shared/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "lark-shared". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. save my API key in the vault). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.