screenpipe-team
**screenpipe-team** lets enterprise admins query their organization's Screenpipe telemetry, including device inventory, team member activity, and substring search across screen recordings and audio transcripts stored in the org's cloud storage. Use this skill when users ask about team activity, what the organization worked on, app usage patterns, or any data that requires visibility beyond a single machine; it's only available to users with an enterprise admin API token configured in their local Screenpipe settings.
git clone --depth 1 https://github.com/screenpipe/screenpipe /tmp/screenpipe-team && cp -r /tmp/screenpipe-team/crates/screenpipe-core/assets/skills/screenpipe-team ~/.claude/skills/screenpipe-teamSKILL.md
# Screenpipe Enterprise admin Use `screenpipe team`; it reads the admin token and API base from Screenpipe's Enterprise settings. Never print tokens or read `enterprise.json` into context. ## Choose the smallest command ```bash # Identify a device before searching for one teammate. screenpipe team devices --raw # Search first; default to 24h and at most 20 results. screenpipe team search "TOPIC" --since 24h -n 20 --raw > /tmp/sp-team.jsonl # Fetch a short chronology only after the device and window are known. screenpipe team records --device-id DEVICE --since 4h --kind all -n 50 --raw > /tmp/sp-team.jsonl # Fetch at most 2-3 cited frames, then open the JPEG with your image tool. sp_team_frame_dir="$(mktemp -d)" screenpipe team frame --device-id DEVICE --frame-id FRAME_ID --output "$sp_team_frame_dir/frame.jpg" ``` Only describe pixels after the frame command succeeds and your image tool opens the JPEG. An unavailable frame is not evidence about what was on screen. Keep context small: check `wc -c /tmp/sp-team.jsonl`; if it exceeds 5 KB, filter with `jq` or narrow the query/window instead of printing the whole file. Reference results by timestamp and device, quote only short snippets, respect anonymous `user_*` labels, and do not volunteer unrelated employee data. For the user's own machine, use `screenpipe-api`, not this skill. ## Managed team Pipes ```bash screenpipe team pipes list screenpipe team pipes preview ./my-pipe/pipe.md screenpipe team pipes deploy ./my-pipe/pipe.md screenpipe team pipes schedule my-pipe "every day at 9am" ``` Before any mutation, show the exact preview and target. New deployments default to Cloud Runner; use `--device`, `--member`, or `--all-runtimes` only when the user explicitly chooses that scope. Use `--yes` for automation only after the same preview is accepted. Version conflicts fail closed; re-list and re-preview rather than overwriting a teammate's change. Use `--json` for structured receipts. The CLI explains missing-token and scope errors. Team reads require the relevant `read:devices`, `read:search`, or `read:records` scope; Pipe management requires `write:pipes`. Direct the user to <https://screenpi.pe/enterprise?tab=tokens> to mint or rotate a token, then Settings → Privacy → Admin Team API Token.
Release the screenpipe monorepo. Bumps versions, triggers GitHub Actions for app, CLI, MCP, and JS packages.
Query the user's local and synced-device data via the screenpipe REST API at localhost:3030 — recordings, audio, UI, meetings, connected services, and memory. Use for screen activity, other-device or cross-device history, productivity, media export, connections, or durable memory.
Set up and operate screenpipe from the terminal, including always-on recording, service modes, capture health, storage, local search, pipes, and connections. Use when the user asks to install, run, inspect, query, automate, or debug screenpipe without relying on the desktop app.
Check Screenpipe health status, process state, and diagnose common issues
Retrieve and analyze Screenpipe CLI backend logs and desktop app logs for debugging
Add or change Tauri commands and TypeScript bindings in the screenpipe desktop app. Use when editing #[tauri::command] handlers, lib/utils/tauri.ts, or Rust types exported to the frontend.
Produce a human-facing visual report — a chart, dashboard, scorecard, or styled summary — that renders as a live page in the screenpipe viewer instead of plain text. Use when the task asks for a visual/graphical output rather than a plain note; do NOT use for plain text or raw data (prefer a markdown note for those).
Develop and test Screenpipe Windows-native changes on a disposable Azure VM created from the prepared Screenpipe Windows dev image. Use for Windows compiler, process, service, local API, desktop, capture, installer, or permission behavior. Do not use for React-only work proved by the browser mock.