user-info

Retrieve current session user identity and contact details via get_user_info.

5.0k|548|Updated May 14, 2025

Search Tags:#session #privacy #identity #consent #get_user_info #user_profile

Ready to run

npx skills add https://github.com/dtyq/magic --skill user-info

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: user-info
Source: https://github.com/dtyq/magic/tree/main/backend/super-magic/agents/skills/user-info
Command: npx skills add https://github.com/dtyq/magic --skill user-info

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use when you need the current session user's identity or contact info: name, job title, employee number, email, phone, or department.

Core Features & Use Cases

Retrieve the user's profile via get_user_info.
Access fields such as id, nickname, real_name, work_number, position, email, phone, and departments.
Support privacy controls: desensitize phone by default and require explicit consent to access full numbers.

Quick Start

Ask the AI to fetch the current session user's profile to access basic identity details.

Frequently Asked Questions about user-info

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

FAQPage Schema

How do I fetch the current session user's profile and contact details?▼

Fetch the current session user's profile and contact details by calling the get_user_info interface. It returns structured fields including id, nickname, real_name, work_number, position, email, phone, and departments.

How does this skill handle phone number privacy and data desensitization?▼

Phone number privacy is handled by desensitizing phone digits by default. Accessing full, unmasked phone numbers requires passing include_sensitive_fields upon explicit user consent.

Can I use this to enforce routing decisions based on user identity?▼

Yes, you can use this to enforce routing decisions based on user identity. It retrieves the current session user's identity and department info, supporting workflows that require user context for access control.

What user information fields are available when retrieving a user profile?▼

Available user information fields include id, nickname, real_name, work_number, position, email, phone, and departments. These structured fields are returned when retrieving a user profile.

Do I need a specific interface to access sensitive contact info like email and phone?▼

Yes, you need the get_user_info interface to access contact info like email and phone. Retrieving full sensitive fields requires providing include_sensitive_fields with explicit consent.

When should I not use a generic identity retrieval method for consent-based workflows?▼

You should not use generic retrieval methods for consent-based workflows when accessing sensitive contact details. This skill specifically enforces privacy controls and requires explicit consent for full phone numbers.