resolving-identity

Resolve current user identity and team membership across providers for session-based routing.

3|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/kazukinagata/waggle --skill resolving-identity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resolving-identity
Source: https://github.com/kazukinagata/waggle/tree/main/skills/resolving-identity
Command: npx skills add https://github.com/kazukinagata/waggle --skill resolving-identity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Resolve current user identity and team membership across providers to enable context-aware actions.

Core Features & Use Cases

  • Resolve Current User: determine and store the active user's identity.
  • Resolve Team Membership: optionally fetch and set the current team and member list when a teams database is configured.
  • Resolve Org Members (on demand): fetch organization members when explicitly requested.

Quick Start

Detect the active provider and run this skill to populate current_user and current_team in the session.

Frequently Asked Questions about resolving-identity

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

FAQPage Schema
How do I resolve current user identity for session-based authentication?

Identity resolution determines and stores the active user's identity during session-based authentication workflows, ensuring a current_user value is always available for contextual routing and access decisions.

What's the best way to fetch organization members on demand for authorization?

Fetching organization members on demand retrieves team data explicitly when requested during identity resolution, enabling contextual access decisions without persistently storing the full member list in the session.

How does team membership resolution work when a teams database is configured?

Team membership resolution optionally fetches and sets the current team and member list in the session when a teams database is configured, populating current_team for authorization workflows.

Can I use identity resolution across multiple authentication providers?

Identity resolution detects the active provider and resolves current user identity and team memberships across different authentication providers to enable context-aware actions within a single session.

Why does my session-based workflow require a current_user value?

Session-based workflows require a current_user value to satisfy authorization and personalization requirements, ensuring contextual routing decisions always have an active user identity available for access control.

Do I need a teams database to resolve user identity and organization members?

A teams database is not required to resolve user identity, but it is necessary to optionally fetch and set the current team and member list for organization member resolution during authentication.