mcpbeat

Launch Graphics

rivet-dev/launch-graphics

Generate agentOS marketing/launch graphics (launch & social heroes, code-snippet cards) from the committed generators in docs-internal/graphics. Use when asked to make, update, or render an agentOS launch image, social image, "agentOS Apps" graphic, or technical code-snippet image.

357 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
4293
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/rivet-dev/agentos --skill launch-graphics

The instruction itself

3 sections, as written by the author

agentOS launch graphics

Source generators live in docs-internal/graphics/ (committed). Rendered

PNGs go to ~/tmp/agentos-graphics/ — never commit output images.

Generate

node docs-internal/graphics/render-launch.mjs      # launch/social hero → ~/tmp/agentos-graphics/launch.png
node docs-internal/graphics/render-technical.mjs   # code-snippet card  → ~/tmp/agentos-graphics/technical.png
  • Pass an output dir as arg 1 to override (default ~/tmp/agentos-graphics/).
  • render-technical.mjs needs shiki (dev-only, not a repo dep): set

SHIKI_DIR=/path/to/node_modules/shiki or pnpm add -D shiki.

  • After rendering, open the PNG to review before sharing.

Editing

  • Read docs-internal/graphics/README.md first — it records the brand

decisions (palette, fonts, "Apps" treatment, tile styling) to stay on.

  • Change layout/typography/snippets in the render-*.mjs files or

snippets.json; keep new external logos vendored in docs-internal/graphics/assets/.

  • Iterate by re-running and viewing the PNG; tune sizes/spacing until it reads right.

How to use it

Copy the folder

Take rivet-dev/launch-graphics from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.

Install what it needs

The instructions reference pnpm. Without those the skill loads but fails at the first command.