person-to-user-map

Resolve and cache user identifiers across Slack, GitLab, and Jira.

4|Updated Apr 10, 2023

Search Tags:#cache #slack #jira #gitlab #map #user #identifiers

One-click install

npx skills add https://github.com/dudeofawesome/nix-config --skill person-to-user-map

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: person-to-user-map
Source: https://github.com/dudeofawesome/nix-config/tree/main/modules/presets/home-manager/paciolan/llms/skills/person-to-user-map
Command: npx skills add https://github.com/dudeofawesome/nix-config --skill person-to-user-map

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maps people to their identifiers across Slack, GitLab, and Jira, reducing repeated API calls by leveraging a local cache.

Core Features & Use Cases

Centralized cache of user identities used by cross-tool workflows
Resolve names, nicknames, and emails to Slack, GitLab, and Jira IDs
Writes updates back to the cache to accelerate future lookups

Quick Start

Ask the AI to resolve a user name or email to their Slack, GitLab, and Jira IDs, updating the cache as needed.

Frequently Asked Questions about person-to-user-map

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

FAQPage Schema

How do I map a user's email to their Slack, GitLab, and Jira IDs without repeated API calls?▼

You can map emails to platform IDs by resolving them through a local YAML cache. This person-to-user-map checks the cache first and only queries Slack, GitLab, and Jira APIs on misses, writing updates back to minimize future API calls.

What is the best way to cache user identifiers for cross-tool workflows?▼

The best way to cache user identifiers is using a centralized YAML file stored at $XDG_DATA_HOME/person-to-user-map.yaml. This approach accelerates future lookups by resolving names and emails locally before hitting external APIs.

Does this user mapping approach work with Slack, GitLab, and Jira MCP servers?▼

Yes, user mapping works directly with Slack, GitLab, and Jira MCP servers. When a cache miss occurs, it queries these servers to resolve the requested identifiers and then writes the results back to the local cache.

Can I resolve nicknames to platform user IDs across multiple tools?▼

Yes, you can resolve nicknames to platform user IDs. The mapping supports resolving names, nicknames, and emails to their corresponding Slack, GitLab, and Jira identifiers while caching the results locally.

Why does my cross-tool workflow need a centralized user identity cache?▼

A centralized user identity cache is needed to reduce repeated API calls across Slack, GitLab, and Jira. By checking the cache first, workflows avoid rate limits and latency associated with resolving the same user identifiers multiple times.

What are the limitations of using a local YAML cache for user mapping?▼

A limitation of a local YAML cache is that it only updates during an API lookup on a cache miss. If a user's identifier changes on Slack, GitLab, or Jira without a corresponding cache update, the stored mapping becomes stale.