The OSS graveyard is full of tools that only posted once

The launch spike is real. I've watched it happen: you ship, get 40 GitHub stars in a day, maybe a comment or two, and then the repo sits. Not because the tool isn't useful — because keeping up distribution is repetitive manual work that compounds badly against everything else you're actually trying to build.

I built marketing-pipeline to handle the recurring part. The specific thing it does differently: a GitHub Actions cron runs at 14:00 UTC on weekdays, picks the least-recently-used angle for each project, generates a post per channel, and publishes. After initial setup, there's no daily action required.

Onboarding a new project is one command:

marketing onboard --name my-tool --repo owner/repo --kind mcp-server

That fetches the README, extracts the problem statement and key facts, generates a pool of angles, and writes everything to projects.yml. From that point the cron takes over, rotating through projects × angles × channels and enforcing per-channel length limits (280 chars for X, 300 for Bluesky, 150–400 words for Dev.to and Hashnode).

One detail worth knowing: there's a hard-reject gate in pipeline/antislop.py that kills posts containing specific tokens — excited, game-changer, unlock, AI-powered, emoji, hashtags, exclamation points, rhetorical questions — before anything gets published. I wrote it because the default LLM output for "write a social post about my tool" is unusable noise, and I didn't want to manually review every draft.

The kind field routes directory submissions by project type. An mcp-server gets listed on MCP Registry, Smithery, Glama, and PulseMCP. A claude-skill goes to awesome-claude-code (though that one requires a human to submit via their GitHub issue form — the pipeline generates the payload, but their rules don't allow automation). A browser-extension routes to Chrome Web Store, Firefox AMO, and Edge Add-ons.

Requires an Anthropic API key plus credentials for Bluesky, Dev.to, and Hashnode at minimum. Mastodon and Slack are optional.

github.com/robertnowell/marketing-pipeline