# 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

```bash
npx skillstore add larksuite/lark-contact
```

## Metadata

- Status: approved
- Slug: larksuite-lark-contact
- Version: 1.0.0
- Author version: 1.0.0
- Skillstore revision: r2
- Version status: valid
- Tree hash: 0bca2b90e40834efe83f074041460cd83b267cb57c72d2c4bca3ce7fa23c2d43
- Author: larksuite
- GitHub username: larksuite
- License: MIT
- Repository: https://github.com/larksuite/cli/tree/main/skills/lark-contact/
- Ref: ebdfe608f5de2b66ff37ab4af12af8ac4f5e8006
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, filesystem
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/larksuite-lark-contact
- Manifest: https://skillstore.pages.dev/api/skills/larksuite-lark-contact/manifest

## Capabilities

- Search Lark users by name, email, phone number, or prior chat relationship.
- Resolve up to 20 queries in parallel and identify which query matched each result.
- Retrieve up to 100 users by open\_id with names, emails, departments, and account status.
- Fetch users by open\_id, union\_id, or user\_id with user or bot identity where supported.
- Filter results by enterprise email, tenant boundary, chat history, or organization status.
- Guide disambiguation when multiple users share a name before messages or calendar actions.

## Use Cases

- 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.

## Prompt Templates

### Find one contact

```
Find the Lark contact named [name]. Show matching names, departments, emails, and open_id values.
```

### Look up a user ID

```
Look up [open_id]. Summarize the user's name, department, email, activation status, and tenant status. Note missing fields.
```

### Filter and disambiguate

```
Search for [name or email] among same-tenant colleagues with enterprise email. Show every candidate and ask me to choose when ambiguous.
```

### Resolve a contact batch

```
Resolve these contacts in parallel: [names]. Match each result to its query, flag partial failures, and identify ambiguous or missing contacts.
```

## Limitations

- Contact search requires user identity; bot identity only supports direct retrieval with an ID.
- Search does not paginate automatically; refine queries when more results are available.
- Cross-tenant users may omit email, department, status, and other business fields.
- Department trees, messaging, and calendar scheduling require other Lark tools.

## 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.

## Anti Patterns

- 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.

## Security Audit

- Audited at: 2026-07-23T16:05:35.621\+00:00
- Summary: All 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.

## Stats

- Views: 93
- Downloads: 12
- Favorites: 0
- Popularity score: 0
