Cc-skills find-user
Use when user wants to find, look up, or resolve a Telegram user by username, phone number, or ID, or get someone's Telegram profile info.
install
source · Clone the upstream repo
git clone https://github.com/terrylica/cc-skills
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/terrylica/cc-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/plugins/tlg/skills/find-user" ~/.claude/skills/terrylica-cc-skills-find-user && rm -rf "$T"
manifest:
plugins/tlg/skills/find-user/SKILL.mdsource content
Find Telegram User
Resolve usernames, phone numbers, or IDs to full user/chat profile information.
Self-Evolving Skill: This skill improves through use. If instructions are wrong, parameters drifted, or a workaround was needed — fix this file immediately, don't defer. Only update for real, reproducible issues.
Preflight
- Session must exist:
~/.local/share/telethon/<profile>.session- If missing, run
first/tlg:setup
- If missing, run
Usage
/usr/bin/env bash << 'EOF' SCRIPT="${CLAUDE_PLUGIN_ROOT:-$HOME/.claude/plugins/marketplaces/cc-skills/plugins/tlg}/scripts/tg-cli.py" # By username uv run --python 3.13 "$SCRIPT" find-user @username # By user ID uv run --python 3.13 "$SCRIPT" find-user 2124832490 # By phone (must be in contacts) uv run --python 3.13 "$SCRIPT" find-user +16043008878 # Works for groups/channels too uv run --python 3.13 "$SCRIPT" find-user @channelname EOF
Output
Returns JSON with profile information:
{ "type": "User", "id": 2124832490, "first_name": "Name", "last_name": null, "username": "username", "phone": "1234567890", "bot": false }
For groups/channels:
{ "type": "Channel", "id": 1234567890, "title": "Group Name", "username": "groupname", "participants_count": 42 }
Post-Execution Reflection
After this skill completes, check before closing:
- Did the command succeed? — If not, fix the instruction or error table that caused the failure.
- Did parameters or output change? — If tg-cli.py's interface drifted, update Usage examples and Parameters table to match.
- Was a workaround needed? — If you had to improvise (different flags, extra steps), update this SKILL.md so the next invocation doesn't need the same workaround.
Only update if the issue is real and reproducible — not speculative.