lark-contact

SkillCommunityTranslated from Chinese

This skill provides tools for interacting with the Lark contact directory. It allows agents to resolve names or emails to open_ids and retrieve user details such as department, contact information, status, and signatures.

Compatibility:

Install:

npx skills add open.feishu.cn/lark-contact

View on skills.sh

contact (v2)

CRITICAL, Before starting, you MUST use the Read tool to read ../lark-shared/SKILL.md, which contains authentication and permission handling.

Which command to choose

The user identity and bot identity are two completely independent paths. Determine the current identity first, then choose the command from the table below:

Goal	user identity	bot identity
Search for employees by name / email to get open_id	`+search-user`	Not supported
Get profile of others with known open_id	`+search-user --user-ids <id>`	`+get-user --user-id <id>`
View yourself	`+get-user` or `+search-user --user-ids me`	Not supported
Check colleague's personal status / signature	`user_profiles batch_query`	Not supported

If you already have the open_id and just want to send a message / schedule a meeting, there is no need to go through contact. Use lark-im / lark-calendar directly.

Typical scenarios

Find Zhang San to send him a message: search first, confirm the open_id, then send:

lark-cli contact +search-user --query "张三" --has-chatted --as user
lark-cli im +messages-send --user-id ou_xxx --text "Hi!"

Batch query colleague's personal status / personal signature (use schema to check parameters first).

lark-cli schema contact.user_profiles.batch_query
lark-cli contact user_profiles batch_query \
  --params '{"user_id_type":"open_id"}' \
  --data '{"user_ids":["ou_xxx","ou_yyy"],"query_option":{"include_personal_status":true,"include_description":true}}' \
  --as user

If the search returns multiple results and subsequent operations have side effects (sending messages, inviting to meetings, etc.), list the candidates for the user to choose from; do not choose the first one without authorization.

Notes

41050 / Permission denied: Restricted by the visibility scope of the current identity (both commands may encounter this). Switch to bot identity or have an administrator adjust the visibility scope. See lark-shared for details.
Cross-tenant users (is_cross_tenant=true): Most business fields are empty strings. This is a Feishu visibility rule. Handle empty values in downstream processes.
ID type: Default is open_id. +get-user can change --user-id-type union_id|user_id; +search-user only accepts open_id.

Out of scope for this skill

Send messages / check chat history → lark-im
Schedule meetings / invite to meetings → lark-calendar
Department tree / list employees by department / organizational structure → lark-openapi-explorer to find native interfaces

contact (v2)

CRITICAL — 开始前 MUST 先用 Read 工具读取 ../lark-shared/SKILL.md，其中包含认证、权限处理

选哪个命令

user 身份和 bot 身份是两条完全独立的路径。先确定当前身份,再按下表选命令:

想做什么	user 身份	bot 身份
按姓名 / 邮箱搜员工拿 open_id	`+search-user`	不支持
已知 open_id 取他人资料	`+search-user --user-ids <id>`	`+get-user --user-id <id>`
查看自己	`+get-user` 或 `+search-user --user-ids me`	不支持
查同事的个人状态 / 签名	`user_profiles batch_query`	不支持

已知 open_id 只是想发消息 / 排日程,不必经过 contact —— 直接 lark-im / lark-calendar。

典型场景

找张三给他发消息:先搜,确认 open_id,再发:

lark-cli contact +search-user --query "张三" --has-chatted --as user
lark-cli im +messages-send --user-id ou_xxx --text "Hi!"

批量查同事的个人状态 / 个性签名(先用 schema 看参数)。

lark-cli schema contact.user_profiles.batch_query
lark-cli contact user_profiles batch_query \
  --params '{"user_id_type":"open_id"}' \
  --data '{"user_ids":["ou_xxx","ou_yyy"],"query_option":{"include_personal_status":true,"include_description":true}}' \
  --as user

搜索命中多条且后续操作有副作用(发消息、邀请会议等),把候选列给用户挑;不要擅自选第一条。

注意事项

41050 / Permission denied 受当前身份的可见范围限制(两条命令都可能遇到)。换 bot 身份或让管理员调整可见范围,细节见 lark-shared。
跨租户用户(is_cross_tenant=true)多数业务字段为空字符串,这是飞书可见性规则,下游做空值兜底。
ID 类型:默认 open_id。+get-user 可改 --user-id-type union_id|user_id;+search-user 只接受 open_id。

不在本 skill 范围

发消息 / 查聊天记录 → lark-im
排日程 / 邀请会议 → lark-calendar
部门树 / 按部门列员工 / 组织架构 → lark-openapi-explorer 查找原生接口

Categories:

Communication

Share:

Details:

Installs
275,729
First seen
Jun 10, 2026

View Repository

Auto-fetched from GitHub 10 hours ago.

Stats via skills.sh.

Skills similar to lark-contact:

Installs

Installs

Installs

Which command to choose

The user identity and bot identity are two completely independent paths. Determine the current identity first, then choose the command from the table below:

Goal	user identity	bot identity
Search for employees by name / email to get open_id	`+search-user`	Not supported
Get profile of others with known open_id	`+search-user --user-ids <id>`	`+get-user --user-id <id>`
View yourself	`+get-user` or `+search-user --user-ids me`	Not supported
Check colleague's personal status / signature	`user_profiles batch_query`	Not supported

If you already have the open_id and just want to send a message / schedule a meeting, there is no need to go through contact. Use lark-im / lark-calendar directly.

Typical scenarios

Find Zhang San to send him a message: search first, confirm the open_id, then send:

lark-cli contact +search-user --query "张三" --has-chatted --as user lark-cli im +messages-send --user-id ou_xxx --text "Hi!"

Batch query colleague's personal status / personal signature (use schema to check parameters first).

lark-cli schema contact.user_profiles.batch_query lark-cli contact user_profiles batch_query \ --params '{"user_id_type":"open_id"}' \ --data '{"user_ids":["ou_xxx","ou_yyy"],"query_option":{"include_personal_status":true,"include_description":true}}' \ --as user

Notes

41050 / Permission denied: Restricted by the visibility scope of the current identity (both commands may encounter this). Switch to bot identity or have an administrator adjust the visibility scope. See lark-shared for details.

Cross-tenant users (is_cross_tenant=true): Most business fields are empty strings. This is a Feishu visibility rule. Handle empty values in downstream processes.

ID type: Default is open_id. +get-user can change --user-id-type union_id|user_id; +search-user only accepts open_id.

contact (v2)

CRITICAL — 开始前 MUST 先用 Read 工具读取 ../lark-shared/SKILL.md，其中包含认证、权限处理

选哪个命令

user 身份和 bot 身份是两条完全独立的路径。先确定当前身份,再按下表选命令:

想做什么	user 身份	bot 身份
按姓名 / 邮箱搜员工拿 open_id	`+search-user`	不支持
已知 open_id 取他人资料	`+search-user --user-ids <id>`	`+get-user --user-id <id>`
查看自己	`+get-user` 或 `+search-user --user-ids me`	不支持
查同事的个人状态 / 签名	`user_profiles batch_query`	不支持

已知 open_id 只是想发消息 / 排日程,不必经过 contact —— 直接 lark-im / lark-calendar。

典型场景

找张三给他发消息:先搜,确认 open_id,再发:

lark-cli contact +search-user --query "张三" --has-chatted --as user
lark-cli im +messages-send --user-id ou_xxx --text "Hi!"

批量查同事的个人状态 / 个性签名(先用 schema 看参数)。

lark-cli schema contact.user_profiles.batch_query
lark-cli contact user_profiles batch_query \
  --params '{"user_id_type":"open_id"}' \
  --data '{"user_ids":["ou_xxx","ou_yyy"],"query_option":{"include_personal_status":true,"include_description":true}}' \
  --as user

搜索命中多条且后续操作有副作用(发消息、邀请会议等),把候选列给用户挑;不要擅自选第一条。

注意事项

41050 / Permission denied 受当前身份的可见范围限制(两条命令都可能遇到)。换 bot 身份或让管理员调整可见范围,细节见 lark-shared。
跨租户用户(is_cross_tenant=true)多数业务字段为空字符串,这是飞书可见性规则,下游做空值兜底。
ID 类型:默认 open_id。+get-user 可改 --user-id-type union_id|user_id;+search-user 只接受 open_id。

不在本 skill 范围

发消息 / 查聊天记录 → lark-im
排日程 / 邀请会议 → lark-calendar
部门树 / 按部门列员工 / 组织架构 → lark-openapi-explorer 查找原生接口