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

# 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

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.