aiskillstore/marketplace / pending/screenrig/screenrig
screenrig
VerifiedFree, 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 41.8 KB |
| agents/openai.yaml | config | 589 B |
| references/advertising.md | markdown | 4.5 KB |
| references/android-device-owner.md | markdown | 1.9 KB |
| references/dashboards.md | markdown | 13.9 KB |
| references/installation.md | markdown | 2.2 KB |
| references/live-view.md | markdown | 3.5 KB |
| references/media-sync.md | markdown | 7.5 KB |
| references/migrate.md | markdown | 2.5 KB |
| references/notifications.md | markdown | 12.9 KB |
| references/playlists.md | markdown | 27.8 KB |
| references/reports.md | markdown | 3.9 KB |
| references/screen-card.md | markdown | 6.6 KB |
| references/sources.md | markdown | 31.9 KB |
| scripts/screenrigexecutable | script | 2.2 KB |
| scripts/screenrig-plugin-freshnessexecutable | script | 24.6 KB |
| skill-report.json | config | 404.5 KB |
references/migrate.md
View on GitHub# Move screens over from another signage system
`migrate` runs in the CLI on the user's machine. The other system's key stays
with you: it is read from the environment or a `--credentials FILE`, goes only to
that system, and never reaches screenRIG. Never put a key in notes, feedback,
chat replies or a command line, and never ask for one to be pasted into chat.
1. `migrate vendors VENDOR` names what the system takes, the variables its key
goes in, and the steps that make a read-only key. Ask the person to make the
key and save it as `NAME=VALUE` lines in a file; name it with `--credentials FILE`.
For a system that is not listed, use `--from files` with a folder or `.zip`
of the media and optional `playlists.csv` (playlist, file, duration, order) and
`screens.csv` (name, group, playlist, timezone).
2. `migrate scan --from VENDOR ...` reads the account, prints a report and writes
`scan.json` into `--dir` (default `./screenrig-migration-VENDOR`). It needs no
sign-in and sends nothing to screenRIG. Show the person the counts, every
`not_imported` reason and the `lossy` changes. Where `next` asks for
originals, have them download the files into one folder and rescan with
`--files DIR`. Add `--timezone ZONE` when screens have no time zone.
3. `migrate apply --dry-run` prints the plan from the project as it is now.
`migrate apply` (Manage access) makes the media, playlists, one waiting
screen per old screen and the campaigns. It is safe to rerun and never
changes what an earlier run made: after any stop (`data.stopped.next` is the
command), failure or `waiting` item, run the same command again. A file
address that no longer works (`vendor_file_gone`) fails that media alone:
run `migrate scan` again, then the same apply. Do not edit or delete the
directory's files until the import is done.
4. Each old display waits under its old name. For each one, install the Player,
then either read its code to `migrate pair CODE --screen ID` (the source id,
or the exact old name), or open its link on the device (`fleet-links show ID`
prints the URL, which is a credential: give it only to the device manager) and
run `migrate apply` again, which finishes the screen. Past the project's 50
links a screen has no link and pairs by code.
5. Verify each screen with `screen show` and `screen screenshot`. Set what the
report said was missing: `screen set-timezone` where `no_timezone`,
`screen assign` where `no_default_playlist`.
6. Tell the person to keep the old system running until every screen matches.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 471k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Unverified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |