wecomcli-contact
Find WeCom Contacts and User IDs
Similar names and incomplete contact details can make employee lookup difficult. This skill guides WeCom directory searches and presents identifiers, departments, and matching details.
Installer avec mon Agent
Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.
Review the Skillstore skill "wecomcli-contact" from https://skillstore.io/skills/wecomteam-wecomcli-contact.md and its manifest at https://skillstore.io/api/skills/wecomteam-wecomcli-contact/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Votre Agent doit toujours présenter son plan et demander toute confirmation exigée par la politique de sécurité.
Ressources lisibles par les agents
Utilisez ces liens lorsqu’un Agent IA, un crawler ou un script a besoin d’un contexte propre au lieu de lire toute la page.
Tester
Utilisation de « wecomcli-contact ». Illustrative request: Find Alex Chen and show the user ID and department.
Résultat attendu:
- Illustrative result, not live directory data.
- Name: Alex Chen; user ID: alex.chen; department: Product / Design.
- Management role: not provided.
Utilisation de « wecomcli-contact ». Illustrative request: List all contacts matching Li Wei.
Résultat attendu:
- Illustrative partial result, not live directory data.
- Li Wei; user ID: li.wei.sales; department: Sales.
- Li Wei; user ID: li.wei.support; department: Customer Support.
- The current response contains only some results. The API reported a result limit.
Audit de sécurité
SûrAll 20 static findings are false positives: Markdown backticks were misidentified as execution, and readable Chinese documentation triggered the entropy heuristic. No evidence found of prompt injection, credential theft, or unauthorized data transfer in SKILL.md. The external CLI and required shared skill were not included, so their behavior remains outside this review.
Facteurs de risque
Partager et citer ce rapport
Partagez le rapport d’évaluation versionné, le badge neutre, la carte intégrable et les citations. Skillstore présente les preuves sans décider si ce Skill est sûr.
Copier le lien du rapport
https://skillstore.io/skills/wecomteam-wecomcli-contact/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportBadge Markdown
[](https://skillstore.io/skills/wecomteam-wecomcli-contact?utm_source=security_passport_badge)Badge HTML
<a href="https://skillstore.io/skills/wecomteam-wecomcli-contact?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/wecomteam-wecomcli-contact/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Carte intégrable
<iframe src="https://skillstore.io/embed/skills/wecomteam-wecomcli-contact.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Citations académiques (APA · BibTeX · CFF)
Citation APA
wecomteam. (2026). wecomcli-contact security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/wecomteam-wecomcli-contact/audits/1Citation BibTeX
@techreport{wecomteam-wecomteam-wecomcli-contact-2026,
author = {wecomteam},
title = {wecomcli-contact security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/wecomteam-wecomcli-contact/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "wecomcli-contact security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "wecomteam"
date-released: "2026-10-22"
url: "https://skillstore.io/skills/wecomteam-wecomcli-contact/audits/1"
identifiers:
- type: other
value: "skillstore:wecomteam-wecomcli-contact:audit:1"
description: "Skillstore immutable audit report identifier"
Score Skillstore
Pourquoi ce score Niveau de confiance des preuves: MoyenCe que vous pouvez créer
Identify a colleague
Search by English name or pinyin and compare department paths before choosing the intended person.
Retrieve a user identifier
Find a contact and report the returned userid after resolving ambiguous matches.
Review matching names
Request all contacts matching a name and retain any warning that the returned list is incomplete.
Essayez ces prompts
Find contacts matching [name] in the WeCom directory.
Search for [pinyin or English name]. Show user IDs and department paths so I can select the correct person.
Search the WeCom directory for [keyword one], [keyword two], and [keyword three]. Preserve result order and show matched keywords.
List all contacts matching [name] using list mode. Include returned user IDs, department paths, and management roles, and report any result-limit hint.
Bonnes pratiques
- Complete the wecomcli-shared prerequisite checks before running any wecom-cli command.
- Resolve ambiguous identities using returned identifiers and department paths while preserving API result order.
- Use list mode only for explicit complete-list requests, and always report nonempty result-limit hints.
Éviter
- Guessing search keywords when neither the request nor context supplies them.
- Treating the first match as the intended person without resolving ambiguity.
- Claiming a list is complete despite a result-limit hint, or presenting a management role as a general job title.