Download the app

Guide /Use PublishPort as a Skill

Use PublishPort as a Skill

Install the PublishPort Skill so your coding agent knows how to publish through your own logged-in browser — 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

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

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.

Two ways it runs

The skill works out which channel it has. Both end up in the same place — your machine:

  • Your agent speaks MCP (claude.ai, Claude Code, Cursor and most others): it goes through your MCP address. Set that up once in Connect your AI.

  • Your agent doesn’t speak MCP: it uses the official CLI, with that same address:

    npx publishport login        # paste the address from the app's Connect AI panel
npx publishport capabilities # which devices are online, which platforms are signed in

Either way, publishing still happens in your own browser session on your own machine, and either way it travels through the relay — so the agent can live anywhere. 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.