lark-contact

Resolve employee names or emails to Lark open_id values and retrieve contact profiles.

195|12|Updated Jul 19, 2026
One-click install
npx skills add https://github.com/ZJU-REAL/HugAgentOS --skill lark-contact-zju-real
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lark-contact
Source: https://github.com/ZJU-REAL/HugAgentOS/tree/main/src/backend/plugin_bundles/marketplace/feishu-cli/skills/lark-contact
Command: npx skills add https://github.com/ZJU-REAL/HugAgentOS --skill lark-contact-zju-real

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill resolves employees from names or email addresses to reliable Lark open_id values and retrieves contact details from known IDs, preventing messages, group invitations, and calendar actions from targeting the wrong person.

Core Features & Use Cases

  • Contact Search: Find employees by name, email, chat history, organizational status, tenant boundary, or enterprise email.
  • Profile Lookup: Retrieve names, departments, emails, activation status, contact identifiers, and other available details from open_id values.
  • Identity Handling: Distinguish user and bot workflows, account for cross-tenant visibility limits, and support localized display names.
  • Disambiguation: Surface multiple matching contacts for user confirmation before downstream actions with side effects.
  • Use Case: When a user asks to message Zhang San, search the directory, present candidates if necessary, confirm the correct person, and provide the selected open_id for the messaging workflow.

Quick Start

Use the lark-contact skill to find the Lark open_id and department for the employee named Zhang San.

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

Resolve Lark contacts by searching employee names or email addresses to retrieve reliable open_id values and retrieve contact profiles from known identifiers using lark-cli contact commands.

Can I search the Lark directory if multiple employees have the same name?

Yes, the Lark contact search applies disambiguation by surfacing multiple matching contacts for user confirmation before executing downstream actions with side effects like messaging or group invitations.

What contact details can I retrieve from a Lark open_id?

Retrieve names, departments, emails, activation status, contact identifiers, and other available details from known Lark open_id values to verify contacts before messaging or calendar coordination.

Does Lark contact resolution handle cross-tenant visibility limits?

Yes, Lark identity resolution distinguishes user and bot workflows and accounts for cross-tenant visibility limits, supporting localized display names and applying pagination awareness during contact search.

When should I confirm a Lark contact before sending a message or calendar invite?

Confirm Lark contacts before messaging, group invitations, and calendar actions to prevent targeting the wrong person, especially when identity resolution returns multiple matching candidates requiring disambiguation.