How do I install the Publish Medium skill?

Run npx skillmds@latest add paladini/publish-medium in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Publish Medium safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Publish Medium?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Publish Medium free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Publish Medium?

paladini (@paladini) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Publish Medium by paladini — Agent Skill

Name: Publish Medium
Author: paladini

Publish Medium

Publish or cross-post to Medium via the medium-publisher CLI (Playwright). Use when the user asks to publish on Medium, cross-post from dev.to/TabNews, import a story URL, or run medium-publisher login/session-check/import/publish.

paladini b288c2a 2 files · 4.7 KB Updated Sep 17, 2026

File contents

Publish to Medium

Uses @paladini/medium-publisher from the publish-agents repo — not harness-score or other product repos.

⚠️ Wrong directory = `Missing script: "medium"`

npm run medium only works inside publish-agents:

cd D:\code\publish-agents
npm run medium -- login

From any directory (Windows):

D:\code\publish-agents\scripts\medium.ps1 login

Or after npm link in packages/medium-publisher:

medium-publisher login

Set PUBLISH_AGENTS_ROOT=D:\code\publish-agents if the repo lives elsewhere.

Prerequisites

Node.js 20+
Repo at D:\code\publish-agents (or PUBLISH_AGENTS_ROOT)
Built once: npm install && npm run build
One-time login: see commands above

Login (reuse your Chrome/Edge session)

Default config uses system-profile — your real Chrome Default profile.

If already logged into Medium in Chrome:

Close all Chrome windows.
medium-publisher login → press Enter when /me/stories loads.

If Chrome must stay open:

medium-publisher browser-start
medium-publisher login --browser cdp

Isolated Playwright Chromium (no profile):

medium-publisher login --browser bundled

Config: %APPDATA%\medium-publisher\config.json — copy from packages/medium-publisher/config.example.json.

Workflow (cross-post — preferred)

Confirm source URL is public (dev.to or TabNews).
Session check:

npm run medium -- session-check

Dry-run import (creates draft + extract, no publish):

npm run medium -- import --url "https://dev.to/..." --dry-run --json

Import draft:

npm run medium -- import --url "https://dev.to/..." --json

Review formatting — follow skills/review-medium-import/SKILL.md (compare DEV.to markdown, fix code blocks/headings via fix-draft).
Publish only when user confirms:

npm run medium -- import --url "https://dev.to/..." --publish --json

Record returned medium_url in the announcement markdown frontmatter (medium_url:).

Workflow (local markdown — fallback)

When no public URL exists:

npm run medium -- publish --title "..." --body-file ./post.md --dry-run
npm run medium -- publish --title "..." --body-file ./post.md --publish --json

When session fails (exit 3)

Tell the user to run interactive login — do not store passwords in repo files:

npm run medium -- login

Style / content

For tone and structure, consult mcp-me (ask_about_me) before writing. After DEV.to import, run review-medium-import or use publish-devto-to-medium for the full pipeline. See docs/devto-to-medium.md.

Do not

Commit storageState.json or .env with credentials
Gate CI on Medium publish (flaky browser)
Use Playwright when TabNews API CLI exists (future tabnews-publisher)

Troubleshooting

See TROUBLESHOOTING.md.

---name: publish-mediumdescription: Publish or cross-post to Medium via the medium-publisher CLI (Playwright). Use when the user asks to publish on Medium, cross-post from dev.to/TabNews, import a story URL, or run medium-publisher login/session-check/import/publish.---# Publish to MediumUses **`@paladini/medium-publisher`** from the **publish-agents** repo — **not** harness-score or other product repos.## ⚠️ Wrong directory = `Missing script: "medium"``npm run medium` only works inside **publish-agents**:```powershellcd D:\code\publish-agentsnpm run medium -- login```From **any** directory (Windows):```powershellD:\code\publish-agents\scripts\medium.ps1 login```Or after `npm link` in `packages/medium-publisher`:```powershellmedium-publisher login```Set `PUBLISH_AGENTS_ROOT=D:\code\publish-agents` if the repo lives elsewhere.## Prerequisites- Node.js 20+- Repo at `D:\code\publish-agents` (or `PUBLISH_AGENTS_ROOT`)- Built once: `npm install && npm run build`- One-time login: see commands above## Login (reuse your Chrome/Edge session)Default config uses **`system-profile`** — your real Chrome Default profile.**If already logged into Medium in Chrome:**1. Close **all** Chrome windows.2. `medium-publisher login` → press Enter when `/me/stories` loads.**If Chrome must stay open:**```powershellmedium-publisher browser-startmedium-publisher login --browser cdp```**Isolated Playwright Chromium (no profile):**```powershellmedium-publisher login --browser bundled```Config: `%APPDATA%\medium-publisher\config.json` — copy from `packages/medium-publisher/config.example.json`.## Workflow (cross-post — preferred)1. Confirm source URL is **public** (dev.to or TabNews).2. Session check:```bashnpm run medium -- session-check```3. Dry-run import (creates draft + extract, no publish):```bashnpm run medium -- import --url "https://dev.to/..." --dry-run --json```4. Import draft:```bashnpm run medium -- import --url "https://dev.to/..." --json```5. **Review formatting** — follow `skills/review-medium-import/SKILL.md` (compare DEV.to markdown, fix code blocks/headings via `fix-draft`).6. Publish only when user confirms:```bashnpm run medium -- import --url "https://dev.to/..." --publish --json```7. Record returned `medium_url` in the announcement markdown frontmatter (`medium_url:`).## Workflow (local markdown — fallback)When no public URL exists:```bashnpm run medium -- publish --title "..." --body-file ./post.md --dry-runnpm run medium -- publish --title "..." --body-file ./post.md --publish --json```## When session fails (exit 3)Tell the user to run **interactive login** — do not store passwords in repo files:```bashnpm run medium -- login```## Style / contentFor tone and structure, consult **mcp-me** (`ask_about_me`) before writing. After DEV.to import, run **review-medium-import** or use **publish-devto-to-medium** for the full pipeline. See [docs/devto-to-medium.md](../docs/devto-to-medium.md).## Do not- Commit `storageState.json` or `.env` with credentials- Gate CI on Medium publish (flaky browser)- Use Playwright when TabNews API CLI exists (future `tabnews-publisher`)## TroubleshootingSee [TROUBLESHOOTING.md](./TROUBLESHOOTING.md).

Frequently asked questions