lark-contact

Resolve Lark contact names or emails to open_ids and fetch user details.

4|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/FradSer/skills --skill lark-contact-fradser
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lark-contact
Source: https://github.com/FradSer/skills/tree/main/skills/lark/lark-contact
Command: npx skills add https://github.com/FradSer/skills --skill lark-contact-fradser

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Translates Lark/Feishu contact references from a name or email into the corresponding open_id, and supports reverse lookup by open_id to reveal name, department, email, contact details, status, and signature. It enables workflows where a user needs to message someone or schedule on their behalf, or verify what an open_id represents, without performing department-tree traversals or bulk directory operations.

Core Features & Use Cases

  • Resolve identifiers by name or email to obtain the open_id.
  • Retrieve user details by open_id, including basic and selected profile fields.
  • Distinguish between user and bot contexts to guide actions like messaging or scheduling.
  • Provide safe disambiguation guidance when multiple matches exist.
  • Note: This skill does not perform department-tree operations or bulk directory scans.

Quick Start

Ask the AI to locate a user by name or email to retrieve their 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 Lark user's open_id from their name or email?

To find a Lark user's open_id, you can use this skill to search contacts by name or email. It translates the provided identifier into the corresponding open_id for use in messaging or scheduling workflows.

Can I retrieve Lark contact details like department and phone using an open_id?

Yes, you can retrieve Lark contact details by performing a reverse lookup using an open_id. This fetches identity details including name, department, email, phone, status, and signature for the specified user.

Does this skill support searching the Lark department tree or bulk directory scans?

No, this skill does not support department-tree operations or bulk directory scans. It is designed specifically for resolving individual user identifiers and fetching specific profile fields rather than traversing organizational structures.

What is the best way to resolve multiple matches when searching for Lark contacts?

When searching for Lark contacts yields multiple matches, the skill provides safe disambiguation guidance. This helps you distinguish between user and bot contexts to identify the correct user before taking action.

How do I get Lark user details for scheduling workflows without bulk directory operations?

You can get Lark user details for scheduling workflows by asking the AI to locate the user by name or email. It identifies the correct user and presents profile fields like department and status without requiring bulk directory scans.