lark-contact
Find Lark Contacts and Resolve User IDs
Finding the correct Lark colleague can be difficult when names are duplicated or only an ID is available. This skill searches contacts and retrieves user details.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "lark-contact" from https://skillstore.io/skills/larksuite-lark-contact.md and its manifest at https://skillstore.io/api/skills/larksuite-lark-contact/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "lark-contact". Find Alice Chen in Lark.
Expected outcome:
- Two matching contacts were found.
- Alice Chen, Finance, alice.chen@example.com, open_id ou_a.
- Alice Chen, Product, a.chen@example.com, open_id ou_b.
- Select the intended contact before continuing.
Using "lark-contact". Look up open_id ou_a.
Expected outcome:
Alice Chen works in Finance and has an active Lark account. Her enterprise email is alice.chen@example.com.
Using "lark-contact". Resolve Alice, Bob, and Priya.
Expected outcome:
- Alice matched one contact.
- Bob matched two contacts and requires confirmation.
- Priya returned no result.
Security Audit
SafeAll 35 static findings are false positives caused by Markdown syntax, relative documentation links, multilingual prose, and documented Lark CLI examples. The reviewed files contain no executable scripts, obfuscated payloads, prompt injection, or unsafe file access.
Risk Factors
⚙️ External commands (14)
📁 Filesystem access (5)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/larksuite-lark-contact/audits/6?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/larksuite-lark-contact?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/larksuite-lark-contact?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/larksuite-lark-contact/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/larksuite-lark-contact.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
larksuite. (2026). lark-contact security audit report (audit version 6) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/larksuite-lark-contact/audits/6BibTeX citation
@techreport{larksuite-larksuite-lark-contact-2026,
author = {larksuite},
title = {lark-contact security audit report (audit version 6)},
institution = {Skillstore},
year = {2026},
number = {6},
url = {https://skillstore.io/skills/larksuite-lark-contact/audits/6},
note = {Author version 1.0.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "lark-contact security audit report (audit version 6)"
version: "1.0.0"
type: report
authors:
- name: "larksuite"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/larksuite-lark-contact/audits/6"
identifiers:
- type: other
value: "skillstore:larksuite-lark-contact:audit:6"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Resolve message recipients
Find the correct colleague and open_id before a messaging workflow.
Enrich contact records
Retrieve names, emails, departments, and activation status for known open_id values.
Verify meeting invitees
Disambiguate colleagues with similar names before passing selected identifiers to a calendar workflow.
Try These Prompts
Find the Lark contact named [name]. Show matching names, departments, emails, and open_id values.
Look up [open_id]. Summarize the user's name, department, email, activation status, and tenant status. Note missing fields.
Search for [name or email] among same-tenant colleagues with enterprise email. Show every candidate and ask me to choose when ambiguous.
Resolve these contacts in parallel: [names]. Match each result to its query, flag partial failures, and identify ambiguous or missing contacts.
Best Practices
- Use a complete enterprise email when available because it usually produces a unique match.
- Confirm the intended person when multiple contacts match before starting any side-effecting workflow.
- Choose user or bot identity according to the requested lookup and available directory permissions.
Avoid
- Do not select the first same-name result without user confirmation.
- Do not use this skill for department trees, messaging, or calendar scheduling.
- Do not assume missing cross-tenant fields indicate invalid data.
Frequently Asked Questions
Can this skill search by name or email?
Can it retrieve a user from an open_id?
Does contact search work with bot identity?
How does it handle duplicate names?
Why are some user fields empty?
Can it list every employee in a department?
Developer Details
Author
larksuiteLicense
MIT
Author version
v1.0.0
Skillstore revision
r2
Ref
ebdfe608f5de2b66ff37ab4af12af8ac4f5e8006
Maintenance freshness
7/25/2026
Usage
8 downloads · 92 views
File structure