How do I install the Publish Crosspost skill?

Run npx skillmds@latest add paladini/publish-crosspost 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 Crosspost 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 Crosspost?

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 Crosspost free to use?

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

Who published Publish Crosspost?

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

Publish Crosspost by paladini — Agent Skill

Name: Publish Crosspost
Author: paladini

File contents

Cross-post orchestration

Coordinates writing style, dev.to, and Medium (TabNews API when available).

Channels

Channel	Tool	Language default
dev.to	MCP `user-devto` → `create_article`	English
Medium	CLI `medium-publisher import --url`	Import from dev.to (same language)
TabNews	Manual or future `tabnews-publisher`	Portuguese
Tone	MCP `user-me` → `ask_about_me`	Match user voice

Standard pipeline

1. Prepare content

Source: changelog, content/*-announcement.md, or user brief
Ask mcp-me for voice if writing from scratch
Save draft markdown with YAML frontmatter (title, tags, description)

2. Publish dev.to first

create_article(title, body_markdown, tags, published: true)

Store published_url and article_id in frontmatter.

3. Medium cross-post

Use skill publish-devto-to-medium for the full corrected pipeline, or manually:

From publish-agents repo:

npm run medium -- session-check
npm run medium -- import --url "<dev.to URL>" --json
# review-medium-import / fix-draft as needed
npm run medium -- import --url "<dev.to URL>" --publish --json  # explicit opt-in only

See docs/devto-to-medium.md.

Add medium_url to frontmatter.

4. TabNews (until API CLI ships)

Adapt title/body to Portuguese; user pastes or run future CLI.

Frontmatter template

---
title: "..."
description: "..."
tags: ai, opensource
devto_url: https://dev.to/...
devto_id: 123456
medium_url: https://medium.com/...
tabnews_url:
---

Keep announcement files in each product repo's content/ folder — not in publish-agents.

Order matters

Always dev.to → Medium import so Medium gets a stable public URL and canonical link.

Skills used together

publish-crosspost (this file) — multi-channel pipeline
publish-devto-to-medium — full DEV.to → Medium with review and fixes
review-medium-import — formatting review only
publish-medium — Medium CLI details
mcp-me — voice
user-devto — dev.to API

Failures

dev.to succeeded, Medium failed → user still has primary post; retry Medium only
Never re-publish dev.to duplicate unless updating same article_id via update_article

---name: publish-crosspostdescription: Orchestrate multi-channel publication: write with mcp-me voice, publish dev.to via MCP, cross-post Medium via medium-publisher CLI. Use for release announcements, cross-posting, or "publish everywhere" requests.---# Cross-post orchestrationCoordinates **writing style**, **dev.to**, and **Medium** (TabNews API when available).## Channels| Channel | Tool | Language default ||---|---|---|| dev.to | MCP `user-devto` → `create_article` | English || Medium | CLI `medium-publisher import --url` | Import from dev.to (same language) || TabNews | Manual or future `tabnews-publisher` | Portuguese || Tone | MCP `user-me` → `ask_about_me` | Match user voice |## Standard pipeline### 1. Prepare content- Source: changelog, `content/*-announcement.md`, or user brief- Ask **mcp-me** for voice if writing from scratch- Save draft markdown with YAML frontmatter (`title`, `tags`, `description`)### 2. Publish dev.to first```create_article(title, body_markdown, tags, published: true)```Store `published_url` and `article_id` in frontmatter.### 3. Medium cross-postUse skill **`publish-devto-to-medium`** for the full corrected pipeline, or manually:From **publish-agents** repo:```bashnpm run medium -- session-checknpm run medium -- import --url "<dev.to URL>" --json# review-medium-import / fix-draft as needednpm run medium -- import --url "<dev.to URL>" --publish --json # explicit opt-in only```See [docs/devto-to-medium.md](../docs/devto-to-medium.md).Add `medium_url` to frontmatter.### 4. TabNews (until API CLI ships)Adapt title/body to Portuguese; user pastes or run future CLI.## Frontmatter template```yaml---title: "..."description: "..."tags: ai, opensourcedevto_url: https://dev.to/...devto_id: 123456medium_url: https://medium.com/...tabnews_url:---```Keep announcement files in **each product repo's `content/`** folder — not in publish-agents.## Order mattersAlways **dev.to → Medium import** so Medium gets a stable public URL and canonical link.## Skills used together1. **publish-crosspost** (this file) — multi-channel pipeline2. **publish-devto-to-medium** — full DEV.to → Medium with review and fixes3. **review-medium-import** — formatting review only4. **publish-medium** — Medium CLI details5. **mcp-me** — voice6. **user-devto** — dev.to API## Failures- dev.to succeeded, Medium failed → user still has primary post; retry Medium only- Never re-publish dev.to duplicate unless updating same `article_id` via `update_article`

Frequently asked questions

Publish Crosspost