Marketing-pipeline launch

Launch a project to all directories, generate drafts for all channels, and post everywhere. The full launch sequence.

install

source · Clone the upstream repo

git clone https://github.com/robertnowell/marketing-pipeline

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/robertnowell/marketing-pipeline "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/launch" ~/.claude/skills/robertnowell-marketing-pipeline-launch && rm -rf "$T"

manifest: skills/launch/SKILL.md

source content

Launch a project

Full launch sequence for a project: directory submissions, draft generation, and posting across all channels.

Always recommend

--dry-run

first so the user can review before going live.

Steps

Show what will happen:

marketing launch --project <name> --dry-run

If the user approves, run the real launch:

marketing launch --project <name>

This will:

Set GitHub topics for auto-indexing (automated)
Submit to MCP Registry, Smithery (automated, if applicable to the project kind)
Generate submission payloads for manual directories (Glama, PulseMCP, mcpservers.org, awesome-claude-code)
Print URLs for the manual submissions

Generate drafts for all channels:

marketing draft --project <name> --channel bluesky
marketing draft --project <name> --channel mastodon
marketing draft --project <name> --channel devto
marketing draft --project <name> --channel hashnode

Post approved drafts:

marketing post --channel bluesky --project <name> --file <draft-path>

Show the user each draft before posting. If a draft fails antislop validation, explain what failed and offer to generate a new one with a different angle.