Most OSS projects I've seen die on day two. The tool is fine. The README is decent. The launch post got 40 upvotes. Then the author never posts again, because posting manually every day across Bluesky, Mastodon, Dev.to, and Hashnode is genuinely tedious work that compounds across multiple projects. I built marketing-pipeline to handle the recurring part. After the initial setup, a GitHub Actions cron runs at 14:00 UTC on weekdays and rotates through your projects, angles, and channels — picking whichever angle was used least recently so you're not repeating yourself. Onboarding a new project is one command: marketing onboard --name my-tool --repo owner/repo --kind mcp-server Enter fullscreen mode Exit fullscreen mode That fetches the README, sends it to Claude, and writes problem, facts, and content angles to projects.yml .…