Documents & Data · IN-DEPTH PROFILE

lark-shared

Lark Shared is the foundation for the other open.feishu.cn Skills.

Best for

Anyone operating lark-cli Skills

What you get

Initialize lark-cli + Choose identity

Main limitation

This is foundational guidance, not a standalone document, calendar, or messaging workflow.

First risk

Credential and authorization handling. Configuration flows expose authorization URLs and manage app credentials. Keep URLs opaque, never log secrets, and verify the intended tenant.

EVIDENCE FRESHNESS

Three checks, kept separate

A recent source check is not a runtime test or security audit.

Upstream sourceChecked 2026-08-20

Pinned revision · 755daa4d

Open pinned commit
SkillSignal profileSource-grounded

Updated 2026-08-20

Runtime & securityNot independently verified

Source review does not certify behavior or safety.

30-SECOND BRIEF

What it does—and when it fits

Lark Shared is the foundation for the other open.feishu.cn Skills. It documents lark-cli configuration, user-versus-bot identity, authorization links and QR codes, permission handling, notices, and safety conventions that domain-specific Skills expect the agent to read first.

INSTALL BY AGENT

Choose your Agent

Paths come from official Agent docs or the universal installer behind skills.sh. Compatibility still follows this Skill's record.

Native

This Skill's current record explicitly names this Agent. Still inspect scripts, permissions, and external dependencies first.

Project scope.claude/skills/lark-shared/
Personal scope~/.claude/skills/lark-shared/

Use project scope for team sharing and personal scope across repositories. The installer defaults to project scope; add -g for personal scope.

Install command (project scope)

This source cannot produce a reliable command. Open the listed source and copy the complete Skill folder manually.

Official agent docs

Claude Code discovers custom Skill folders automatically at project or personal scope.

View path evidence

TYPICAL WORKFLOW

A practical workflow

01

Initialize lark-cli

Guide application configuration and the interactive authorization flow.

02

Choose identity

Distinguish user and bot credentials before resource operations.

03

Handle permissions

Interpret permission failures, notices, and required follow-up safely.

THE TRADEOFFS

Advantages and tradeoffs

Notable strengths

  1. This profile is manually organized around the current upstream SKILL.md workflow.
  2. The capability boundary remains explicitly tied to open.feishu.cn.
  3. Core uses, limitations, and risks are separated for pre-install review.

Limitations

  1. This is foundational guidance, not a standalone document, calendar, or messaging workflow.
  2. Tenant policy and application configuration can still block documented operations.

BEST FIT

Who it is for

Anyone operating lark-cli Skills

Administrators reviewing identity and permission boundaries

BEFORE YOU USE IT

Risks to review before use

High

Credential and authorization handling

Configuration flows expose authorization URLs and manage app credentials. Keep URLs opaque, never log secrets, and verify the intended tenant.

High

External data and identity boundary

Requests access Feishu tenant resources. Use the correct identity, least-privilege scopes, and keep sensitive content out of logs.

SECURITY

What the permission profile means

  • Declared access remains governed by the current upstream SKILL.md and runtime requests.
  • Treat Feishu documents, messages, people, and business records as permission-controlled data.
  • SkillSignal has not independently executed or security-audited this package; external skills.sh labels are not SkillSignal certification.

Not a security certification. External ratings are attributed references. SkillSignal has not independently executed or security-reviewed this Skill.

INSIDE THE PACKAGE

Indexed files

SKILL.mdUpstream Skill instructionsSource-linked

TAGS

feishuauthenticationpermissions

Manually expanded from the current upstream SKILL.md and linked source at open.feishu.cn, checked 2026-08-19. This is an original summary, not an execution result or security certification.