ll-chat-identity

Query an API to determine a chat participant's role type and bindings.

9|Updated Jun 10, 2026
One-click install
npx skills add https://github.com/Katsumitec/Human_First --skill ll-chat-identity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ll-chat-identity
Source: https://github.com/Katsumitec/Human_First/tree/main/projects/ll-ai-first/skills-scripts/ll-bot-skills/ll-chat-identity
Command: npx skills add https://github.com/Katsumitec/Human_First --skill ll-chat-identity

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests, and includes scripts (resource) components.

What problem does it solve?

This Skill provides a detailed analysis of the identity of a chat, identifying the role type and associated bindings.

Core Features & Use Cases

  • Chat Identity Analysis: Determines the role type (MER, CHNL, NONE, CONFLICT) and associated bindings for a given chat.
  • Role Type Identification: Identifies whether the chat is associated with a merchant (MER), channel (CHNL), or has no binding (NONE).
  • Binding Details: Provides detailed information about the merchant or channel bindings, including currencies and channel IDs.
  • Use Case: Ideal for scenarios where accurate identification of chat participants is crucial, such as in customer service or transactional chatbots.

Quick Start

Use the ll-chat-identity skill to get the identity details of the current chat.

Frequently Asked Questions about ll-chat-identity

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

FAQPage Schema
How do I identify the role type of a chat participant in a transactional chatbot?

Chat participant role identification is determined by querying an API to retrieve the role type and associated bindings, suitable for customer service or transactional environments requiring precise identity analysis.

What role types are supported when analyzing chat identity bindings?

Chat identity analysis identifies four role types: MER for merchant bindings, CHNL for channel bindings, NONE for no binding, and CONFLICT for conflicting bindings, providing detailed currency and channel ID information.

Do I need API permissions to determine chat identity and merchant bindings?

API access with appropriate permissions is required to determine chat identity, as the Skill queries the API to retrieve role types and detailed merchant or channel binding information including currencies and channel IDs.

How do I retrieve merchant and channel binding details for a customer service chat?

Merchant and channel binding details are retrieved by querying the API with the chat identifier, returning associated currencies and channel IDs for accurate participant identification in customer service scenarios.

Can I use the requests library to analyze chat identity in transactional environments?

The requests library is used as the dependency for API integration to analyze chat identity, determining role types and associated bindings for transactional chatbot environments.

What does the CONFLICT role type mean when analyzing chat identity?

The CONFLICT role type indicates that the chat identity has conflicting bindings, returned alongside MER, CHNL, and NONE types when the API detects multiple or inconsistent binding associations for the chat participant.