Agent skill
amplitude-user-lookup
This skill should be used when the user asks to "lookup Amplitude user", "find user by device ID", "get user activity from Amplitude", or "search Amplitude user events". Queries Amplitude REST API for user data using Device ID or User ID.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/amplitude-user-lookup
SKILL.md
Amplitude User Lookup
Query Amplitude user data via REST API using Device ID or User ID.
Prerequisites
Set environment variables:
export AMPLITUDE_API_KEY="your-api-key"
export AMPLITUDE_SECRET_KEY="your-secret-key"
export AMPLITUDE_REGION="us" # or "eu" for EU data residency
Get keys from: Amplitude Dashboard > Settings > Projects > General
Quick Start
1. Search User (Device ID -> Amplitude ID)
python scripts/user_search.py "DEVICE-ID-HERE"
2. Get User Activity
python scripts/user_activity.py AMPLITUDE_ID --limit 50
Combined Workflow
# Get Amplitude ID first
AMP_ID=$(python scripts/user_search.py "DEVICE-ID" --json | jq -r '.matches[0].amplitude_id')
# Then get activity
python scripts/user_activity.py $AMP_ID --limit 100
Script Options
| Script | Options |
|---|---|
user_search.py |
--json for raw JSON output |
user_activity.py |
--limit N, --offset N, --direction [latest|earliest], --json |
Rate Limits
- User Search/Activity: 360 requests/hour
- Concurrent requests: 5 max
References
- API Reference: curl examples, response schemas, error codes
- Scripts Guide: detailed script usage and examples
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?