Mode d’emploi
- Copiez la commande et examinez le paquet avant de l’installer dans votre environnement agent.
- Consultez le document original pour les outils, identifiants et environnements requis.
- Décrivez les entrées et le livrable souhaité ; comparez la sortie aux sources.
npx skills add https://github.com/daymade/claude-code-skills --skill lark-cli-routerAvant de commencer
- L’installation n’inclut ni abonnement au modèle, ni quota API, ni accès aux fichiers.
- Étoiles et installations reflètent l’activité, pas un test indépendant de qualité ou de sécurité.
Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.
Lark CLI Router
Use this as the only model-visible Lark entry point. The CLI's embedded lark-* guides are the version-synced source of truth; this router selects and loads them instead of copying their domain instructions into another static catalog.
Boundaries
- Tencent IMA is a different product. Route IMA notes or knowledge-base tasks to
ima-skill, not here.
- Do not load all Lark guides. Select the smallest matching guide set for the
current task.
- Do not bypass
lark-cliwith browser automation, rawcurl, or guessed API
contracts while the CLI or one of its embedded guides covers the task.
Workflow
1. Confirm the runtime
Run lark-cli --version. If the binary is absent, fail visibly and report that lark-cli is required; do not invent another transport or confuse the separate Skill-install command with a CLI-binary installer.
Set LARK_CLI_NO_PROXY=1 for every invocation in this environment. When stable machine-readable JSON is needed, also set LARKSUITE_CLI_NO_UPDATE_NOTIFIER=1 and LARKSUITE_CLI_NO_SKILLS_NOTIFIER=1 so notices do not pollute the result.
2. Select the embedded guide
Run lark-cli skills list --json. Match the user's intent and any URL path or token to the returned name, description, and metadata.cliHelp.
Do not derive the CLI domain by stripping lark- from the guide name: exceptions exist, and metadata.cliHelp or the guide itself is authoritative. These high-confusion routes need explicit care:
| Intent | Guide |
|---|---|
| auth, login, profile identity, missing scope, user vs bot | lark-shared |
/wiki/ document content | lark-doc |
| wiki space, membership, or node hierarchy | lark-wiki |
| future meeting or room scheduling | lark-calendar |
| ended meeting search, participants, or meeting artifacts | lark-vc |
known note_id | lark-note |
minute_token, 妙记 content, or audio-to-minutes | lark-minutes |
| live meeting participation or in-meeting events | lark-vc-agent |
| file upload, download, move, permissions, metadata, or Office import | lark-drive |
For ordinary docs, sheets, Base, slides, mail, IM, tasks, approval, apps, and other domains, the live skills list descriptions are the routing table. A multi-domain request may select a workflow guide or a small ordered set of domain guides.
3. Load the selected instructions completely
Read the selected guide before acting:
lark-cli skills read lark-doc
lark-cli skills read lark-doc/references/lark-doc-fetch.mdThe first form prints the guide's SKILL.md; the second reads a referenced file. Read every file the selected guide marks required for the current branch.
Embedded reads reject ... Rebase a sibling pointer such as ../lark-whiteboard/references/x.md to:
lark-cli skills read lark-whiteboard/references/x.mdAlways try lark-cli skills read first for Markdown and reference files. If it returns reference ... not found, resolve that exact guide-relative path under ~/.agents/skills/<guide-name>/. Before the first such fallback for a guide, confirm with the host's SHA-256 tool that its installed SKILL.md is byte-identical to lark-cli skills read <guide-name>; a mismatch must fail visibly and trigger a bundle refresh. This explicitly keeps lark-apps/creative-design/ reachable even though the current binary does not embed it.
Machine resources under scripts/ or assets/ are never embedded, so resolve them directly in the same installed bundle. If a required file is absent, stop and report that the disk bundle must be installed or refreshed; do not fabricate a replacement.
4. Inspect, execute, and verify
- Treat
metadata.cliHelpas a help recipe, not always a literal command. Run its
concrete commands; resolve any placeholder from the loaded guide first. If the field is absent, use the guide's own commands or the selected domain's --help.
- Prefer a matching
+shortcut; otherwise use a typed resource command. - Before a typed call whose parameters are not already explicit in the guide,
run lark-cli schema <service.resource.method>.
- Use
lark-cli apionly as the documented escape hatch when no shortcut or
typed command covers the endpoint.
- Preserve any explicitly supplied
--profile; never guess a profile or identity.
Use lark-cli whoami when identity is material or ambiguous.
- For writes, use
--dry-runwhen the command supports a useful preview. If a
high-risk write exits 10, present the proposed action and wait for explicit human confirmation; never append --yes automatically.
- Treat the command as successful only when its process exits
0or its JSON
envelope has ok == true. Do not test for a top-level code == 0.
- After a write, follow the selected guide's domain-specific verification
contract. If it defines none, perform the narrowest independent read that proves the requested state changed. A guide that explicitly forbids an opportunistic second query takes precedence. Report partial results or missing coverage.
On authorization errors, load lark-shared and follow its user/bot and missing- scope branch. Do not turn an auth failure into repeated retries or a browser/raw-API fallback.
