lark-contact

Resolve Feishu/Lark employee names or emails into open_id identifiers.

1|2|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/chenguojun06-star/fz66666 --skill lark-contact-chenguojun06-star
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lark-contact
Source: https://github.com/chenguojun06-star/fz66666/tree/main/.agents/skills/lark-contact
Command: npx skills add https://github.com/chenguojun06-star/fz66666 --skill lark-contact-chenguojun06-star

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the challenge of finding and resolving employee identities in Feishu/Lark by converting names or emails into open_id values and retrieving reliable user profiles when needed.

Core Features & Use Cases

  • Employee Identity Resolution: Search users by name, email, or chat relationship to obtain open_id identifiers for downstream actions.
  • User Profile Lookup: Retrieve employee details such as name, department, email, and contact information from known open_id values.
  • Use Case: When you need to send a message or schedule a meeting with a person identified only by name, use this Skill to find the correct employee identity before proceeding.

Quick Start

Ask the lark-contact skill to find the Feishu employee identity for a person by name or email and return the matching open_id.

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 employee's open_id from their name or email?

To find a Feishu employee's open_id from their name or email, you can resolve Lark contacts by searching user identities and retrieving the matching open_id identifier for downstream actions like messaging or scheduling.

Can I retrieve user profile details like department and email using a Lark open_id?

Yes, you can retrieve user profile details like department and email using a Lark open_id. The contact lookup process validates permissions and fetches reliable employee information from known user identifiers.

Does resolving Lark contacts require specific permission validation?

Yes, resolving Lark contacts requires permission validation. The process uses lark-cli contact commands with user or bot identity handling to ensure secure access to employee profile information and open_id resolution.

What is the best way to resolve Lark employee identities before scheduling a meeting?

The best way to resolve Lark employee identities before scheduling a meeting is to search by name, email, or chat relationship. This obtains the correct open_id identifier, ensuring you target the right employee for downstream workflows.

When do I need to resolve Feishu user identities into open_id values?

You need to resolve Feishu user identities into open_id values for identity-aware workflows. This applies to contact lookup scenarios before messaging, scheduling, or any action requiring accurate employee identification in Lark.

Why does my Lark contact lookup fail to return employee profile information?

Lark contact lookup may fail to return employee profile information due to insufficient permission validation or incorrect identity handling. Ensure lark-cli contact commands are properly configured with the correct user or bot identity permissions.