Use the native Screenpipe CLI to query Enterprise team activity or safely preview, deploy, and schedule managed team Pipes. Injected only by the Enterprise app for active admins.
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
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.
# 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.
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.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。
Release the screenpipe monorepo. Bumps versions, triggers GitHub Actions for app, CLI, MCP, and JS packages.
日本語の概要は準備中です。原文の説明を表示しています。
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).
日本語の概要は準備中です。原文の説明を表示しています。
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 starred work, screen activity, other-device or cross-device history, productivity, media export, connections, durable memory, or discovering and automating saved workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Query the user's local and synced-device Screenpipe data via the REST API at localhost:3030. Use for screen activity, meetings, apps, productivity, other-device or cross-device history, media export, retranscription, or connected services.
日本語の概要は準備中です。原文の説明を表示しています。
Turn a recorded software failure into a reproducible bug report with timestamps and observed behavior.
日本語の概要は準備中です。原文の説明を表示しています。