looking-up-members

Name: looking-up-members
Availability: InStock
Author: Kazu

Resolve member names or emails to provider user IDs.

3|Updated Mar 21, 2026

Search Tags:#delegation #resolve #identity #provider #lookup #org_members #teamsdb

Ready to run

npx skills add https://github.com/kazukinagata/waggle --skill looking-up-members

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: looking-up-members
Source: https://github.com/kazukinagata/waggle/tree/main/skills/looking-up-members
Command: npx skills add https://github.com/kazukinagata/waggle --skill looking-up-members

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Resolve member names or emails to provider user IDs to enable accurate identity resolution in workflows.

Core Features & Use Cases

Exact email and name matches against org_members to locate precise IDs.
Partial name matching to surface multiple candidate IDs for user confirmation.
TeamsDB fallback to gather member data when org_members is empty.
Session-level caching to speed up repeated lookups within a workflow.

Quick Start

Trigger resolving-identity to map a given query (name or email) to the corresponding provider user ID.

Frequently Asked Questions about looking-up-members

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I resolve member emails to provider user IDs for workflow delegation?▼

To resolve member emails to provider user IDs, you can use exact email matching against org_members to locate the precise ID needed for accurate identity resolution and delegation tasks.

What happens if org_members is empty when I try to look up provider IDs?▼

When org_members is empty, a TeamsDB fallback mechanism gathers the necessary member data to ensure identity resolution can still proceed and map queries to provider user IDs.

Can I search for provider user IDs using partial names instead of exact matches?▼

Yes, partial name matching surfaces multiple candidate provider IDs simultaneously, allowing you to review ambiguous results and confirm the correct user identity before assignment.

Do I need resolving-identity data to look up member names and provider IDs?▼

Yes, resolving-identity data is required to ensure predictable outcomes and safe caller behavior when mapping member names or emails to their corresponding provider user IDs.

How can I speed up repeated member lookups within a single workflow?▼

You can speed up repeated member lookups using session-level caching, which stores previously resolved provider user IDs to avoid redundant queries during the same workflow execution.