lark-contact

Resolves Lark employee names and emails to open_ids and looks up user profiles.

Updated Jun 22, 2026
One-click install
npx skills add https://github.com/sliec/shared-files --skill lark-contact-sliec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lark-contact
Source: https://github.com/sliec/shared-files/tree/main/skills/lark-contact
Command: npx skills add https://github.com/sliec/shared-files --skill lark-contact-sliec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When working in the Feishu/Lark ecosystem, you often know a colleague's name or email but need their open_id to send messages, schedule meetings, or add them to groups. This Skill bridges that gap by resolving names and emails to open_ids, and reverse-lookup of open_ids back to names, departments, and contact details. ## Core Features & Use Cases - Name/Email to open_id Resolution: Search employees by name, email, or phone keyword with filters like chat history, enterprise email, tenant boundary, and employment status. - open_id Profile Lookup: Retrieve a user's name, department, email, and contact info from a known open_id, with support for union_id and user_id types. - Batch Fanout Queries: Query up to 20 names in parallel or batch-validate up to 100 open_ids in one call. - Use Case: You want to message "张三" — first search to confirm the correct person's open_id among same-name candidates, then hand the ID to the lark-im skill to send the message. ## Quick Start Ask the assistant to find the Feishu open_id for a colleague named 张三 so you can send them a message.

Frequently Asked Questions about lark-contact

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find a Feishu user's open_id by name?

Run lark-cli contact +search-user --query "name" with user identity to search employees by name, email, or phone. Add filters like --has-chatted or --has-enterprise-email to narrow results, then confirm the correct candidate before using the open_id.

How to look up a Lark user's department and email from an open_id?

Use lark-cli contact +get-user --user-id <id> --as bot, or +search-user --user-ids <id> with user identity for richer fields like department and email. The default ID type is open_id, but get-user also accepts union_id and user_id.

Can I search multiple Feishu employees in one command?

Yes, use --queries with a comma-separated list of up to 20 keywords for parallel fanout search, or --user-ids with up to 100 open_ids for batch validation. Partial failures do not affect other queries in the batch.

Why does Feishu contact search return permission denied error 41050?

Error 41050 means the current identity's visibility scope does not cover the target user. Switch to bot identity or ask an administrator to adjust the visibility range, as both search and get commands are subject to these scope limits.

What are the limitations of Lark contact search?

Search requires user identity and does not auto-paginate; has_more=true means you should refine the query. It cannot traverse department trees or list employees by department, and cross-tenant users return empty business fields.