Documents & Data · IN-DEPTH PROFILE

Lark Contact Skill

Lark Contact resolves Feishu people and organizational identities.

Best for

Agents resolving Feishu recipients

What you get

Resolve a person + Retrieve a profile

Main limitation

User and bot identities expose different operations and directory visibility.

First risk

Personal data exposure. Directory searches and profiles contain personal information. Request only necessary fields and do not expose results beyond the user's authorized context.

EVIDENCE FRESHNESS

Three checks, kept separate

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

Upstream sourceChecked 2026-09-23

Pinned revision · a079fd7a

Open pinned commit ↗
SkillSignal profileSource-grounded

Updated 2026-08-20

Runtime & securityNot independently verified

Source review does not certify behavior or safety.

IN PLAIN ENGLISH

What it does—and when it fits

Lark Contact resolves Feishu people and organizational identities. Its upstream SKILL.md separates user and bot capabilities, supports searching people by name or email to obtain open_id, retrieves profiles when permitted, and advises going directly to messaging or calendar Skills when an open_id is already known.

This is aimed at Agents resolving Feishu recipients. Compare the examples below with your task, then review the limitations, permissions, and risks before installing.

What you get
  • Resolve a personSearch by name or email and confirm the intended user.
  • Retrieve a profileFetch permitted user details from a known open_id.
  • Route the next actionPass the resolved identity to messaging or calendar work without redundant contact calls.
What makes it different
  • This profile is manually organized around the current upstream SKILL.md workflow.
  • The capability boundary remains explicitly tied to open.feishu.cn.
  • Core uses, limitations, and risks are separated for pre-install review.
Community signalskills.sh All-time: #23 · 728.4K installs

No verified review text is in the current dataset. Use the linked source for the latest discussion.

Read the source note ↗

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 install (recommended)
npx skills add larksuite/cli --skill lark-contact --agent claude-code
Personal install
npx skills add larksuite/cli --skill lark-contact --agent claude-code -g

Project install stays with this repository for team sharing. Personal install adds -g and works across repositories.

This command adds the Skill instructions only. Install lark-cli and sign in to Feishu separately before use. Official Lark CLI setup ↗

View install paths
Project path.claude/skills/lark-contact/
Personal path~/.claude/skills/lark-contact/
Official agent docs

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

View path evidence ↗

TYPICAL WORKFLOW

A practical workflow

01

Resolve a person

Search by name or email and confirm the intended user.

02

Retrieve a profile

Fetch permitted user details from a known open_id.

03

Route the next action

Pass the resolved identity to messaging or calendar work without redundant contact calls.

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. User and bot identities expose different operations and directory visibility.
  2. Name matches can be ambiguous and must be confirmed with additional attributes.

BEST FIT

Who it is for

→

Agents resolving Feishu recipients

→

Teams automating people-aware workflows

BEFORE YOU USE IT

Risks to review before use

High

Personal data exposure

Directory searches and profiles contain personal information. Request only necessary fields and do not expose results beyond the user's authorized context.

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.

COMMON QUESTIONS

Lark Contact Skill FAQ

What is the Lark Contact Skill?

Lark Contact resolves Feishu people and organizational identities. Its upstream SKILL.md separates user and bot capabilities, supports searching people by name or email to obtain open_id, retrieves profiles when permitted, and advises going directly to messaging or calendar Skills when an open_id is already known.

How do I install the Lark Contact Skill?

Open and review the listed source, choose the project or personal path for your Agent, then verify the first run in a controlled project. Open the listed source and read the current SKILL.md plus only the references required for this task.

Is the Lark Contact Skill safe to use?

SkillSignal checked the source on 2026-09-23, but that is not a runtime test or security certification. Review the “Personal data exposure” risk first and begin with the least access required.

INSIDE THE PACKAGE

Indexed files

SKILL.mdUpstream Skill instructionsSource-linked

TAGS

feishucontactsidentity

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.