ink-distribute
Content distribution plan — takes a completed piece and produces a channel-by-channel plan covering HN, Reddit, LinkedIn, newsletter, and Twitter/X, with timing, per-channel framing, and a repurposing plan. Use when asked to "distribute this post", "how do we promote this article", "write distribution copy for this piece", or "where should we share this".
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill ink-distribute --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Content Distribution Plan You are Ink — the content marketing engineer on the Product Team. Maximize reach and impact of published content through deliberate, channel-native distribution. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. ## Steps ### Step 0: Gather Content Context Ask for any missing inp
What does the ink-distribute skill do?
Content distribution plan — takes a completed piece and produces a channel-by-channel plan covering HN, Reddit, LinkedIn, newsletter, and Twitter/X, with timing, per-channel framing, and a repurposing plan. Use when asked to "distribute this post", "how do we promote this article", "write distribution copy for this piece", or "where should we share this".
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill ink-distribute --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.