Use PinePaper from Claude — The Skill

4 min read

Want Claude (or another agent that supports Skills) to build PinePaper graphics for you by chat? Install the official PinePaper Skill once and ask in plain English: “animate this logo,” “make a pulsing LIVE badge,” “turn this title into kinetic text and export an MP4.”

The Skill teaches Claude when to reach for PinePaper and how to drive it correctly. Without it, an agent might generate a plain HTML/CSS page or a React component when you wanted a real PinePaper graphic with a real MP4/GIF/SVG export.

Two halves: the Skill is the instruction layer. The MCP server does the actual canvas work. You want both — see API → Guides → Skills for the full developer-side reference (plugin marketplace, Cowork upload, MCP setup, troubleshooting).

Pick your Claude surface

Claude Code (CLI on your machine)

Fastest install — plugin marketplace:

/plugin marketplace add pinepaper/claude-plugins
/plugin install pinepaper@pinepaper-marketplace
/reload-plugins

The plugin includes both the Skill and the MCP server wiring. Done.

Alternative (manual install, no marketplace):

mkdir -p ~/.claude/skills/pinepaper-studio
curl -fsSL https://pinepaper.studio/assets/skills/pinepaper-studio.zip -o /tmp/pp-skill.zip
unzip -o /tmp/pp-skill.zip -d ~/.claude/skills/

Cowork (Claude desktop app)

Option A — Plugin marketplace (Cowork tab → Customize → Plugins → “+” → Add from a repository → point at pinepaper/claude-plugins → Install).

Option B — Upload the Skill:

  1. Cowork tab → Customize → Skills
  2. “+” → “+ Create skill” → “Upload a skill”
  3. Upload pinepaper-studio.zip
  4. Toggle on

If your build supports .skill one-click install, use pinepaper-studio.skill instead. It’s the same bundle with a different extension.

⚠️ Cowork networking caveat

Claude Code runs on your machine — a localhost PinePaper MCP server works directly.

Cowork runs in Anthropic’s cloud. Its MCP connectors go over the public internet from Anthropic’s IP ranges — not your local network. So in Cowork the MCP server must be reachable as a public/remote connector; a localhost-only one won’t work. If MCP tools don’t respond in Cowork, that’s almost always why. (You can still use the Skill’s console-paste fallback — Claude writes pasteable code, you run it in the editor at pinepaper.studio/editor.)

Try it

Once installed, try these prompts (no need to say “PinePaper” — the Skill picks up the intent):

  • “Make a pulsing green LIVE badge with the text ‘LIVE’ for a Twitch overlay.”
  • “Animate the attached SVG logo with a subtle wobble and export as MP4 for Instagram.”
  • “A loading spinner. Three rotating dots. Indigo on a dark background.”
  • “Kinetic text that types out ‘Welcome’ letter by letter, then pulses once.”
  • “A flowchart with three boxes: Start → Process → End, with arrows that pulse.”

You can also invoke the Skill explicitly: type / (Cowork) or /pinepaper:pinepaper-studio (Claude Code).

When something goes wrong

Symptom What to check
Claude generates HTML/CSS instead of a PinePaper graphic Confirm the Skill is enabled in Customize → Skills. If a “frontend-design” plugin is competing, disable it or add “with PinePaper” to your prompt.
Cowork’s MCP tools never respond The MCP server isn’t reachable from Anthropic’s cloud — see the caveat above.
Items appear twice on the canvas The Skill called batch_execute more than once by mistake. Start a fresh job, or remove duplicates from the editor’s Items panel.
The Skill never triggers automatically Check Code execution is enabled in Cowork. Invoke it manually with /.
  • API → Guides → Skills — full developer-facing walkthrough (plugin marketplace, references files, troubleshooting tree)
  • Magic Button — in-editor AI assist that doesn’t need an external agent

Downloads