lark-contact

Resolves Lark contact names and emails to open_ids and retrieves user profiles.

Updated Jun 29, 2026
One-click install
npx skills add https://github.com/trungpr1990-coder/AMI-MAKEUP --skill lark-contact-trungpr1990-coder
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lark-contact
Source: https://github.com/trungpr1990-coder/AMI-MAKEUP/tree/main/.agents/skills/lark-contact
Command: npx skills add https://github.com/trungpr1990-coder/AMI-MAKEUP --skill lark-contact-trungpr1990-coder

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires lark-cli, and includes references (resource) components.

What problem does it solve? When working with Feishu/Lark messaging or scheduling, you often have a person's name or email but need their open_id, or you have an open_id and need to look up their name, department, email, or personal status. This Skill bridges that gap using the lark-cli contact commands. ## Core Features & Use Cases - Name/Email to open_id Resolution: Search employees by name, email, or phone keyword with filters like has-chatted, enterprise email, same-tenant, and employment status. - open_id Reverse Lookup: Retrieve name, department, email, activation status, personal status, and signature for known open_ids, in both user and bot identities. - Batch Fanout Queries: Search up to 20 names in parallel with per-query error reporting, or batch-validate up to 100 open_ids. - Use Case: You want to message a colleague named Zhang San. Search by name, confirm the correct candidate from the results, get the open_id, then hand off to the lark-im skill to send the message. ## Quick Start Ask the assistant to find the open_id of a colleague by name using the lark contact search, then look up their profile details.

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 Lark user's open_id by name?▼

Use lark-cli contact +search-user with the --query flag and the person's name, optionally adding filters like --has-chatted. The command returns matching users with their open_id, which you then pass to messaging or calendar commands.

How to look up Lark user details from an open_id?▼

Run lark-cli contact +search-user --user-ids <id> as user identity for full fields like department and email, or +get-user --user-id <id> as bot identity for basic info. User identity returns richer fields than the bot path.

Can I search multiple Lark contacts at once?▼

Yes, use --queries with a comma-separated list of up to 20 names for parallel search. Each result carries a matched_query field, and partial failures do not affect other queries.

Why does Lark contact search return permission denied error 41050?▼

Error 41050 means the current identity's visibility scope does not cover the target user. Switch between user and bot identity, or ask an administrator to adjust the visibility scope in the Lark admin console.

What are the limitations of Lark contact search?▼

Search only works under user identity and does not auto-paginate; has_more=true means you should refine the query. It also does not support department tree traversal or listing employees by department, which require the native OpenAPI.