Use PublishPort as a Skill

Install the PublishPort Skill so your coding agent knows how to publish through your own logged-in browser — send your agent one line and it installs itself, or run one command. Works with Claude Code, Cursor, Codex, Copilot and 70+ other agents.

A Skill is a set of instructions an agent loads on demand — the manual, not the tools. The PublishPort Skill teaches your agent how to drive your publishing setup properly: check which accounts are signed in, read each platform’s real command schema instead of guessing, stage long text and media as files, show you the post before it goes out, and confirm it landed instead of retrying blindly and posting twice.

It’s free and open source: github.com/karuha-m/publishport-skill.

Install it

Easiest — let your agent do it. Send it this line; it installs the skill and then walks you through authorizing it (details in Connect your AI):

Read https://www.publishport.app/skill.md and follow it to set up PublishPort for me.

Any agent — one command. Works with Claude Code, Cursor, Codex, Copilot, Gemini, OpenCode and 70+ others through skills.sh:

npx skills add https://www.publishport.app/skill.md

Or from the public repo: npx skills add karuha-m/publishport-skill.

Add -g to install it globally instead of into the current project, or -a cursor to target one specific agent.

Claude Code — as a plugin:

/plugin marketplace add karuha-m/publishport-skill
/plugin install publishport@publishport

By hand — just the file:

mkdir -p ~/.claude/skills/publishport
curl -fsSL https://raw.githubusercontent.com/karuha-m/publishport-skill/main/skills/publishport/SKILL.md \
  -o ~/.claude/skills/publishport/SKILL.md

claude.ai: download publishport-skill.zip from the releases page and upload it under Settings → Capabilities → Skills.

Restart your session afterwards so the skill is picked up.

How it reaches your machine

The skill is the manual; the work is done by the official CLI (npx publishport). Every command travels through the PublishPort relay and executes on your machine, in your own browser session — so the agent can live anywhere.

The first time, your agent runs publishport login and hands you an authorization link. You check the confirmation code on the page and click Authorize, and the agent is ready to work. From then on publishport capabilities shows which devices are online and which platforms are signed in.

If your agent is already connected to PublishPort over MCP, the skill uses those MCP tools instead; the result is the same. Keep the desktop app running — it owns the browser the commands drive. The skill adds know-how, not access.

Try it

Ask, in a fresh session:

Which platforms can you publish to right now?

Your agent should list the platforms you’re signed in to. Then give it something real to do — see your first AI publish.

If it doesn’t trigger

Skills load on demand, matched against what you ask. If the agent ignores it, say the name outright (“use the publishport skill”), or check that it’s actually installed — /plugin for the plugin route, ls ~/.claude/skills (or your agent’s own skills directory) for the file route.