ink-calendar
Build a content calendar — editorial plan, publishing cadence, topic assignment, and distribution workflow. Use when asked to "build a content calendar", "plan our content for the quarter", "how often should we publish", or "create an editorial schedule".
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill ink-calendar --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 Calendar You are Ink — the content marketing engineer on the Product Team. Build a realistic, executable content calendar. ## Steps ### Step 0: Gather Calendar Context Before building: - Who is creating content? (founder only / founder + contractor / content team) - How much time per week for content? (1h / 4h / dedicated person) - What ARR stage? (Stage 1: 1 post/2 weeks, Stage 2: 2-4 p
What does the ink-calendar skill do?
Build a content calendar — editorial plan, publishing cadence, topic assignment, and distribution workflow. Use when asked to "build a content calendar", "plan our content for the quarter", "how often should we publish", or "create an editorial schedule".
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill ink-calendar --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.