菜单
This skill should be used when the user asks about Plex watch statistics, current streams, who is watching Plex, active sessions, playback history, most-watched content, user activity, library stats, stream analytics, or anything related to Tautulli monitoring and analytics.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when creating, editing, validating, testing, running, explaining, or removing Labby Code Mode snippets; when a user wants a reusable workflow made from gateway MCP tools; or when building schema-backed snippets from upstream tool ids, JSON schemas, params, inputs, defaults, artifacts, and MCP/CLI snippet actions.
Use when creating, editing, validating, testing, running, explaining, or removing Labby Code Mode snippets; when a user wants a reusable workflow made from gateway MCP tools; or when building schema-backed snippets from upstream tool ids, JSON schemas, params, inputs, defaults, artifacts, and MCP/CLI snippet actions.
This skill should be used when the user wants to automate an iOS Simulator, drive an Android device or emulator via MCP tools, test on multiple devices simultaneously, run a visual regression baseline on mobile, audit accessibility on a real device, release an app to the Play Store, or use the claude-in-mobile CLI or MCP server. Does not apply for structured end-to-end test reports (use android-app-testing or desktop-app-testing for those).
Interpret and use `mcpjam` probe, doctor, OAuth, apps conformance, tools, resources, and prompts output conservatively against MCP 2025-11-25. Use when interacting with MCP servers, executing tools, triaging findings, performing security reviews, deciding whether a CLI finding is real or overstated, or turning inspection output into an engineer-facing report with severity and confidence.
Audit the current Git checkout, open worktrees, local branches, stale or merged cleanup candidates, merge readiness, conflicts, PR/CI/test state, blockers, and safest merge order. Use when the user asks for repo status, branch/worktree cleanup candidates, stale branch review, conflict investigation, merge readiness, or what must be done before open branches can merge.
This skill should be used when the user mentions labby, the labby CLI, the Lab gateway, or any Lab operator surface. Triggers include: "run labby doctor", "check labby health", "start the labby MCP server", "configure ~/.lab/.env", "search upstream MCP tools with Code Mode", "use labby gateway to import servers", "manage the Labby marketplace", "reload the gateway", or any request to run labby CLI commands, inspect gateway upstreams, or dispatch an action against a Lab service.
| name | tautulli |
| description | This skill should be used when the user asks about Plex watch statistics, current streams, who is watching Plex, active sessions, playback history, most-watched content, user activity, library stats, stream analytics, or anything related to Tautulli monitoring and analytics. |
Monitor and analyze Plex Media Server usage through Tautulli's comprehensive analytics API. Track current streams, historical playback data, user activity, and library statistics.
This skill provides read-only access to Tautulli analytics:
All operations are GET-only and safe for monitoring and analytics.
Note: This skill complements the plex skill by adding analytics and historical data that Plex Media Server doesn't expose directly.
Credentials are configured in the arrs plugin settings (userConfig). A SessionStart hook writes them to ~/.config/lab-arrs/config.env, which the scripts load automatically — no manual file editing. Variables used:
# Tautulli Analytics
TAUTULLI_URL="http://192.168.1.100:8181"
TAUTULLI_API_KEY="<your_tautulli_api_key>"
TAUTULLI_URL: Your Tautulli server URL with port (default: 8181)TAUTULLI_API_KEY: Your Tautulli API keyGetting your API key:
All commands use the tautulli-api.sh wrapper script and return JSON output.
The helper script is located at: scripts/tautulli-api.sh
Get server identity and version:
./scripts/tautulli-api.sh server-info
Monitor active streams and current playback:
# All active sessions
./scripts/tautulli-api.sh activity
# Activity with session details
./scripts/tautulli-api.sh activity --details
Returns: Current streams with user, media, player, bandwidth, transcode info
View historical playback data:
# Recent history (default: 25 items)
./scripts/tautulli-api.sh history
# History with filters
./scripts/tautulli-api.sh history --user "username" --limit 50
./scripts/tautulli-api.sh history --days 7 --media-type movie
./scripts/tautulli-api.sh history --section-id 1 --limit 100
# Search history
./scripts/tautulli-api.sh history --search "Inception"
Parameters:
--user <username>: Filter by username--section-id <id>: Filter by library section--media-type <type>: Filter by movie, episode, track, etc.--days <n>: History from last N days--limit <n>: Maximum results (default: 25)--search <query>: Search in titlesTrack user activity and viewing patterns:
# All users watch stats
./scripts/tautulli-api.sh user-stats
# Specific user details
./scripts/tautulli-api.sh user-stats --user "username"
# Top users by play count
./scripts/tautulli-api.sh user-stats --sort-by plays --limit 10
Parameters:
--user <username>: Specific user statistics--sort-by <metric>: Sort by plays, duration, last_seen--limit <n>: Maximum results--days <n>: Stats from last N daysAnalyze library usage and popular content:
# All library sections
./scripts/tautulli-api.sh libraries
# Specific library stats
./scripts/tautulli-api.sh library-stats --section-id 1
# Popular content in library
./scripts/tautulli-api.sh popular --section-id 1 --limit 10
./scripts/tautulli-api.sh popular --media-type movie --days 30
Parameters:
--section-id <id>: Specific library section--media-type <type>: Filter by type (movie, show, artist)--days <n>: Timeframe for popularity--limit <n>: Maximum resultsView recently added media with rich metadata:
# Recently added (default: 25 items)
./scripts/tautulli-api.sh recent
# Recent with filters
./scripts/tautulli-api.sh recent --section-id 1 --limit 50
./scripts/tautulli-api.sh recent --media-type movie --days 7
Get homepage dashboard statistics:
# Overview stats (most popular, most active, etc.)
./scripts/tautulli-api.sh home-stats
# Stats for specific timeframe
./scripts/tautulli-api.sh home-stats --days 30
Analyze stream types and platform usage:
# Plays by stream type (direct/transcode)
./scripts/tautulli-api.sh plays-by-stream --days 30
# Plays by platform
./scripts/tautulli-api.sh plays-by-platform --days 30
# Plays by date/time
./scripts/tautulli-api.sh plays-by-date --days 30
./scripts/tautulli-api.sh plays-by-hour --days 7
./scripts/tautulli-api.sh plays-by-day --days 30
Monitor concurrent stream patterns:
# Concurrent stream history
./scripts/tautulli-api.sh concurrent-streams --days 30
# Peak concurrent streams
./scripts/tautulli-api.sh concurrent-streams --days 7 --peak
Get detailed metadata for specific media:
# By rating key
./scripts/tautulli-api.sh metadata --rating-key 12345
# By GUID
./scripts/tautulli-api.sh metadata --guid "plex://movie/5d776..."
When the user asks about Plex analytics:
activitypopular --media-type movie --days 30history --limit 25user-stats --user "username" --days 7recent --limit 10plays-by-hour --days 30concurrent-streams --days 7 --peakAll commands return JSON with standard Tautulli response structure:
{
"response": {
"result": "success",
"message": null,
"data": { ... }
}
}
Use jq to extract and format data:
# Get just the data
./scripts/tautulli-api.sh activity | jq '.response.data'
# Extract specific fields
./scripts/tautulli-api.sh history | jq '.response.data.data[] | {user: .friendly_name, title: .full_title, date: .date}'
This skill complements the plex skill:
Use both together:
plex skill searchtautulli skill analyticstautulli skillThe arrs plugin supports one Tautulli instance configured via plugin settings. To monitor a different Tautulli server, update the URL and API key in the arrs plugin settings.
For detailed API reference, see: