Skip to content

aiskillstore/marketplace / pending/screenrig/screenrig

screenrig

Verified

Free, agent-driven digital signage. Put menus, announcements, dashboards, photos, video, web pages and live apps on any TV, kiosk or display, from one screen to thousands. Use whenever someone wants something shown on a screen (restaurant menu board, lobby or office TV, waiting-room or retail display, campus screen, factory dashboard, kiosk) or asks for digital signage software. Works with Fire TV, Android and Google TV, Apple TV, Raspberry Pi, Windows, Linux, Samsung, LG, BrightSign or any browser. Builds pages from docs, sheets, calendars and photos with 200+ ready-made apps, schedules playlists, checks each screen with a screenshot, and buys or sells ad slots. Not for screen recording or screen sharing.

FileKindSize
SKILL.mdskill md41.8 KB
agents/openai.yamlconfig589 B
references/advertising.mdmarkdown4.5 KB
references/android-device-owner.mdmarkdown1.9 KB
references/dashboards.mdmarkdown13.9 KB
references/installation.mdmarkdown2.2 KB
references/live-view.mdmarkdown3.5 KB
references/media-sync.mdmarkdown7.5 KB
references/migrate.mdmarkdown2.5 KB
references/notifications.mdmarkdown12.9 KB
references/playlists.mdmarkdown27.8 KB
references/reports.mdmarkdown3.9 KB
references/screen-card.mdmarkdown6.6 KB
references/sources.mdmarkdown31.9 KB
scripts/screenrigexecutablescript2.2 KB
scripts/screenrig-plugin-freshnessexecutablescript24.6 KB
skill-report.jsonconfig404.5 KB

references/reports.md

View on GitHub
# Reports, exports and schedules

Reports read aggregates (uptime rollups, alert history, screen state, direct campaign delivery), never raw events.

## Read a rollup

- `reports list` names the kinds and their filters: `fleet_health`, `uptime`, `publishing`, `alerts`, `alert_log` and `proof_of_play`.
- `reports show KIND --from DAY --to DAY` covers inclusive UTC days (default 30). A folder row counts every screen in it and in the folders inside it, and the first row is the whole project. `--group-by screen|tag`, `--folder-id ID` (with `--direct`: the folder's own screens or child folders) and `--tag TAG` narrow it.
- Rows carry `id`, `parent_id` and `depth` for a folder outline. Availability is online over recorded time; `recorded` says how much of the period screens reported.

## Write a file

- `--format csv|xlsx|pdf --output FILE` on `reports show`, `alerts list`, `project uptime|health-trend`, `screen uptime|health-history`, `playback list|plays|totals|completeness` and `ads reports delivery|fill|spend`, `ads direct report`. The envelope has `path`, `bytes` and `sha256`; quote them with the file.
- A sponsor's statement: `reports show proof_of_play --advertiser "Acme" --from 2026-10-01 --to 2026-10-31 --format pdf --output acme.pdf`. A play counts when the screen reports the media completed.

## Email on a schedule

- `reports subscriptions create --name NAME --kind KIND --cadence daily|weekly|monthly [--weekday D --day-of-month N] --hour H --timezone ZONE --format pdf|xlsx|csv --recipients MEMBERS [--filter NAME=VALUE]`.
- Recipients are project members (user id or member email; `owner` is the project's owner); anyone else is refused. Each run covers the period before it in UTC days. A failed run retries, then waits; read `last_status` and `last_error`. At most 50 per project.

## Export a project

- `project export DIR` writes `export.json` (every file with size and SHA-256), JSON for screens, folders, tags, schedules, playlists with every revision, campaigns, cards, sources, notifications, webhooks and application metadata, `media/files` with `media/manifest.json`, CSV under `data/` and `log/events.jsonl`. Secrets are never written. `--no-media` skips media and `--since DAY` starts the CSV data and the event log. Rerunning keeps complete media and continues partial downloads; `data.complete` false means a section failed: inspect its warning for recovery steps. `export_application_content_omitted` means retain the original application archives alongside this export for release files, including older playlist pins. Rerunning refreshes metadata; `--no-media` also reports this omission.

## Audit log

- `audit list` shows the project's configuration changes newest first: who (`actor`: person, agent, service client, staff, system), `source` (dashboard, api, cli, mcp, staff, device, webhook, system), `action` (`screen.update`, `playlist.create`), the `resource` and `changes`, each with a JSON Pointer `path` and its `before` and `after`. Filters: `--actor ID`, `--actor-kind`, `--source`, `--resource-type`, `--resource-id`, `--action CODE` (a trailing `*` is a prefix), `--field /label`, `--since`, `--until`, and `--after CURSOR` for the next page.
- `audit show ID` prints one entry. A credential reads `(redacted)` on both sides; everything else is the stored value. Pages and media bytes are not copied: the entry links the revision.
- `audit export --format csv|xlsx|pdf --output FILE` writes one row per changed field with the chain head in the file (the last 30 days unless `--since` says otherwise). Quote `path`, `bytes` and `sha256`.
- `audit head` prints `SEQ:HASH`; keep it. `audit verify` recomputes the hash chain (exit 13 and the entries at fault when it fails); `--anchor SEQ:HASH` also proves the history up to a kept head is unchanged. An entry has no `seq` for a few seconds after the change.
- Entries are kept 400 days and no command edits or deletes one. `project export DIR` writes `log/audit.jsonl` and `log/audit-head.json`.

rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).Stars: 198kUpdated Claude CodeCodexUnverifiedInstall
doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.Stars: 198kUpdated Claude CodeCodexVerifiedInstall