Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

jellyfin

Estrellas1

Forks0

Actualizado4 de junio de 2026, 11:16

This skill should be used when the user asks about Jellyfin media server. Triggers include: "check Jellyfin", "Jellyfin library", "who's watching on Jellyfin", "active Jellyfin sessions", "add a Jellyfin user", "Jellyfin metadata", "Jellyfin transcoding", "Jellyfin health", "Jellyfin scheduled tasks", "Jellyfin plugins", or any mention of Jellyfin media server management.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

jmagar

jmagar/lab

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Administradores de redes y sistemas informáticosOcupaciones informáticas y matemáticas·SOC 15-1244

Explorador de archivos

4 archivos

SKILL.md

readonly

name	jellyfin
description	This skill should be used when the user asks about Jellyfin media server. Triggers include: "check Jellyfin", "Jellyfin library", "who's watching on Jellyfin", "active Jellyfin sessions", "add a Jellyfin user", "Jellyfin metadata", "Jellyfin transcoding", "Jellyfin health", "Jellyfin scheduled tasks", "Jellyfin plugins", or any mention of Jellyfin media server management.

Jellyfin

Use this skill for Jellyfin media server workflows. Prefer an available Lab or MCP Jellyfin integration when one is present; otherwise work through the Jellyfin HTTP API, Docker/container inspection, or server logs.

Workflow

Identify the target server, auth source, and scope of change. Do not assume a default server URL or admin token; ask for missing credentials instead of searching broadly.
For read-only checks, use the Jellyfin API or available MCP tools to inspect server info, libraries, users, active sessions, scheduled tasks, devices, and logs.
For library or metadata problems, collect the library id/name, affected item ids, provider ids, scan/task status, and recent Jellyfin log lines before recommending refreshes or metadata edits.
For playback or transcoding problems, gather client, stream type, codec, container, bitrate, subtitle mode, hardware acceleration settings, and the relevant transcode/log output.
For user/account work, confirm the exact user and requested permission change before applying writes.

API Notes

Common REST roots are /System/Info, /Users, /Sessions, /Library/VirtualFolders, /Items, /ScheduledTasks, and /Devices.
Jellyfin typically accepts API keys through X-Emby-Token or Authorization: MediaBrowser Token="<token>" depending on the client path.
Treat delete, metadata rewrite, library rescan, and user-permission changes as writes. Summarize the intended object ids before executing them.

Operational Checks

If Jellyfin is containerized, inspect the container status, mounted config and media paths, network reachability, and recent logs before changing settings.
For database, plugin, or upgrade issues, back up or identify the Jellyfin config/data path first.
When no MCP or authenticated API path is available, provide the exact API or admin-console action the user can run rather than inventing a local command.

Más de este repositorio

mismo repositorio

creating-snippets

jmagar/lab

Use when creating, editing, validating, testing, running, explaining, or removing Labby Code Mode snippets; when a user wants a reusable workflow made from gateway MCP tools; or when building schema-backed snippets from upstream tool ids, JSON schemas, params, inputs, defaults, artifacts, and MCP/CLI snippet actions.

This skill should be used when the user wants to automate an iOS Simulator, drive an Android device or emulator via MCP tools, test on multiple devices simultaneously, run a visual regression baseline on mobile, audit accessibility on a real device, release an app to the Play Store, or use the claude-in-mobile CLI or MCP server. Does not apply for structured end-to-end test reports (use android-app-testing or desktop-app-testing for those).

2026-06-151

mcpjam-inspector

jmagar/lab

Interpret and use `mcpjam` probe, doctor, OAuth, apps conformance, tools, resources, and prompts output conservatively against MCP 2025-11-25. Use when interacting with MCP servers, executing tools, triaging findings, performing security reviews, deciding whether a CLI finding is real or overstated, or turning inspection output into an engineer-facing report with severity and confidence.

2026-06-131

repo-status

jmagar/lab

Audit the current Git checkout, open worktrees, local branches, stale or merged cleanup candidates, merge readiness, conflicts, PR/CI/test state, blockers, and safest merge order. Use when the user asks for repo status, branch/worktree cleanup candidates, stale branch review, conflict investigation, merge readiness, or what must be done before open branches can merge.

2026-06-131

using-labby

jmagar/lab

This skill should be used when the user mentions labby, the labby CLI, the Lab gateway, or any Lab operator surface. Triggers include: "run labby doctor", "check labby health", "start the labby MCP server", "configure ~/.lab/.env", "search upstream MCP tools with Code Mode", "use labby gateway to import servers", "manage the Labby marketplace", "reload the gateway", or any request to run labby CLI commands, inspect gateway upstreams, or dispatch an action against a Lab service.

2026-06-131

name	jellyfin
description	This skill should be used when the user asks about Jellyfin media server. Triggers include: "check Jellyfin", "Jellyfin library", "who's watching on Jellyfin", "active Jellyfin sessions", "add a Jellyfin user", "Jellyfin metadata", "Jellyfin transcoding", "Jellyfin health", "Jellyfin scheduled tasks", "Jellyfin plugins", or any mention of Jellyfin media server management.

Jellyfin

Workflow

Identify the target server, auth source, and scope of change. Do not assume a default server URL or admin token; ask for missing credentials instead of searching broadly.
For read-only checks, use the Jellyfin API or available MCP tools to inspect server info, libraries, users, active sessions, scheduled tasks, devices, and logs.
For library or metadata problems, collect the library id/name, affected item ids, provider ids, scan/task status, and recent Jellyfin log lines before recommending refreshes or metadata edits.
For playback or transcoding problems, gather client, stream type, codec, container, bitrate, subtitle mode, hardware acceleration settings, and the relevant transcode/log output.
For user/account work, confirm the exact user and requested permission change before applying writes.

API Notes

Common REST roots are /System/Info, /Users, /Sessions, /Library/VirtualFolders, /Items, /ScheduledTasks, and /Devices.
Jellyfin typically accepts API keys through X-Emby-Token or Authorization: MediaBrowser Token="<token>" depending on the client path.
Treat delete, metadata rewrite, library rescan, and user-permission changes as writes. Summarize the intended object ids before executing them.

Operational Checks

If Jellyfin is containerized, inspect the container status, mounted config and media paths, network reachability, and recent logs before changing settings.
For database, plugin, or upgrade issues, back up or identify the Jellyfin config/data path first.
When no MCP or authenticated API path is available, provide the exact API or admin-console action the user can run rather than inventing a local command.