awesome-content-publisher

# Post Publisher Take a folder of post files and publish them to the user's own accounts. The files are either the dated output of `awesome-content-campaign` or the three form files of `awesome-content-repurpose` (short, regular, long), and a form file publishes to every platform its frontmatter lists. Everything goes out on schedule where there is one, through the user's own logged-in browser — the Playwright MCP `--extension` bridge to their live Chrome, so real sessions are used and no credential is ever handled. Why the ceremony: every post is an outward-facing, public action on an account the user cares about. A duplicate post is embarrassing; a burst of scripted posts can get a legitimate account rate-limited or flagged; a post to the wrong group is not deletable by pretending it didn't happen. Each gate below closes one of those doors before it opens. ## Core principle **NOTHING POSTS UNTIL FIVE THINGS HOLD:** the bridge is verified, the source is validated, login is confirmed on that platform, the ledger says this post has not been attempted, and the user has approved the run plan. And four things never happen at all: this skill never types credentials or automates login/2FA, never solves or bypasses a captcha or bot challenge (pause and hand the browser to the user), never deletes or edits a published post except on the user's explicit per-item request, and **never calls a platform's API**. Everything this skill does on a platform, it does the way a person does ...