Skills

Teach your agent to talk like a collaborator, not a JSON dumper

A skill is a markdown file that teaches an agent host the Livepeer Agent install ritual, tool-routing rules, and human-friendly voice — echo human_summary, never paste raw tool JSON, confirm before spend. Install the curated onboarding trio in one command, or browse the full library.

Why this matters: a fresh MCP connection exposes real tool schemas, not conversational judgment. Skills are how the agent learns the difference between "call create_media for a single asset" and "call generate_project for a 6-scene story" — before the first tool call, not after a bad guess.

One-command install (curated onboarding trio)

Three skills — get-started, intro, and cowork-ux — are the minimum needed to take a new agent host from zero to a working first render. Pick whichever path matches your client; all four install the same 3 skills.

1. `npx skills` — Claude Code, Cursor, Codex, or any host reading `~/.<agent>/skills/<name>/SKILL.md`

npx skills add livepeer/storyboard

2. GitHub CLI (`gh skill`, v2.90+)

gh skill install livepeer/storyboard

3. Claude Code plugin marketplace

/plugin marketplace add livepeer/storyboard
/plugin install storyboard@storyboard

Registers the 3 skills as plugin-namespaced slash commands: /storyboard:get-started, /storyboard:intro, /storyboard:cowork-ux.

4. curl (fallback — no CLI required, never breaks)

mkdir -p ~/.claude/skills/get-started-mcp ~/.claude/skills/storyboard-intro ~/.claude/skills/cowork-ux
curl -sL https://agent.livepeer.org/skills/get-started-mcp.md -o ~/.claude/skills/get-started-mcp/SKILL.md
curl -sL https://agent.livepeer.org/skills/storyboard-intro.md -o ~/.claude/skills/storyboard-intro/SKILL.md
curl -sL https://agent.livepeer.org/skills/cowork-ux.md -o ~/.claude/skills/cowork-ux/SKILL.md

The curated onboarding trio

Skill	What it teaches
`get-started-mcp`	The install ritual — 3-step connect, header-spacing footgun, health check, lean-vs-full tool profile.
`storyboard-intro`	Tool routing — when to call `create_media` vs `generate_project` vs the Director tools; capability discovery before generating.
`cowork-ux`	Human-friendly voice for Cowork / Desktop / Code — never paste raw tool JSON; echo `human_summary` + `permission_hint` before billable actions; render `next_actions` as numbered menus; loop `subscribe_progress` for async jobs.

Why only 3, when there are ~100?

The full public/skills/ library covers everything from LoRA training to DICOM prep — dozens of domain-specific skills for commercial production, character consistency, game-asset pipelines, and more. Shipping all of them through the one-command installer would recreate the same tool-overload problem the MCP server's lean tool-profile already fixes on the server side. The 3 onboarding skills are deliberately the minimum to get to a working first render; browse and attach the rest as your workflow needs them.

Discover the full library

In-chat: "list skills" or the MCP list_skills tool.
Attach one mid-session: the MCP attach_skill tool, or livepeer skills load <id> on the CLI.
Author your own: any markdown file with valid frontmatter (name, description) is a skill. Publish it with publish_skill (MCP) or livepeer skills publish <id> (CLI).

← Get Started (MCP) · CLI · /start