devrel-content-calendar skill (samber): plan a quarter of developer content
Plans a quarter of developer-relations content as dated slots with owners, reviewers and capacity limits.
- Installs
- 12.5K
- on skills.sh
- Stars
- 7
- on GitHub
- Files
- 4
- besides SKILL.md
- Updated
- Nov 2026
- last repo commit
devrel-content-calendar makes your agent plan a quarter around the limit that actually binds: reviewer passes, not drafting hours. It collects fixed dates, picks a shape, sets mix ratios, sizes capacity, places dated slots with an owner and reviewer each, and adds a monthly review ritual.
It triggers on a devrel content or editorial calendar, what to publish next quarter, how many pieces a small team can ship, or "we publish randomly". It plans the quarter only; each piece goes to a per-format skill. The folder holds SKILL.md and three reference files and bundles no scripts.
Good for
- DevRel content leads whose plan keeps slipping
- Small teams with one writer and one reviewer who need to know what fits
- Teams balancing launch-tied content against evergreen pieces
Install devrel-content-calendar
Claude Code
- 1
Copy this prompt.
Install the devrel-content-calendar skill in Claude Code. Run this command: /plugin marketplace add samber/developer-relations-skills /plugin install developer-relations-skills@developer-relations-skills Then check that it loaded and tell me how to use it.
- 2
Paste it into Claude Code. It shows the change and asks before running it.
The README recommends installing the whole collection because its skills reference each other, and devrel-content-calendar names other skills in the collection to hand work to. The whole-collection routes add all 93 skills in the repo (counted from the git tree); the repo holds no hooks, agents, commands or MCP server files, and 14 of its skills bundle a script. Pick one route per agent.
From the project README. Source.
What's in the skill
When it loads
Plans a quarter of developer-relations content as a dated slot plan with named owners and reviewers - fixed anchors (releases, launches, CFP deadlines, conferences), a surface, pillar, journey and shelf-life mix, and sizing against real writing and review capacity. Use whenever the user asks for a devrel content calendar, an editorial calendar or content plan for a developer audience, what to publish next quarter, how to balance evergreen against launch-tied content, how many pieces a small team can ship, or says their content plan keeps slipping - even if they only say "we publish randomly". Plans the quarter only; individual pieces go to the per-format skills such as samber/developer-relations-skills@engineering-blog-post.
Sections in SKILL.md
- Interview
- Choosing the quarter's shape
- Workflow
- Benchmarks and baselines
- Pass thresholds
- Invocation examples
- Output shape
- Audience split
- Failure modes
- Metrics
- References
Key facts
- Author
- Samuel Berthe (samber)
- Installs on skills.sh
- 12,516 (as of Nov 2, 2026)
- GitHub stars
- 8 for the whole collection repo (Nov 2, 2026)
- Last commit
- Nov 1, 2026 (whole repo)
- skills.sh audits
- Gen Agent Trust Hub pass, Socket pass, Snyk pass
- Version in SKILL.md
- 1.0.3
- Collection size
- 93 skills in the repo (counted from the git tree)
What it includes
Asks eleven questions one at a time; question 7 (one-off win or asset base) weighs most.
No travel budget or no accepted talk deletes the event-led shape; no launch deletes the launch-dominated shape.
InterviewRanks three shapes and recommends one.
Evergreen-compounding (the default), launch-dominated and event-led. The value inside the quarter and the value a year out are ranked separately.
Choose the quarter's shapeLists fixed dates with an owner and gathers demand-sourced topics and bets.
Anchors are treated as consumed capacity. Each demand item carries evidence and each bet a hypothesis.
Collect anchors and build the poolTurns the funding driver into ratios and estimates each format in review passes.
Compares the total against published throughput figures and the team's own last quarter, then subtracts named slack.
Set the mix and size capacity in passesPlaces anchor-bound pieces, evergreen slots, refresh slots and slack.
Each slot has a title, surface, pillar, journey stage, shelf life, owner, reviewer, anchor, evidence and publish week.
Place the calendarSchedules each derivative of a piece as its own slot with one canonical URL per topic.
Talk, recording, write-up, clips and docs update.
Add the repurposing treeIterates until eight checks pass, then reports which failed and what changed.
Includes a named reviewer on every slot, committed slots at most 80% of capacity, and a preparation and follow-up slot for every anchor.
Pass thresholdsScores an existing calendar against the thresholds and proposes the smallest fixes.
Failures are reported in damage order.
Try: “One writer, one reviewer at four hours a week, twelve weeks. What can we actually ship?”
Audit mode
From the official docs
Permissions
Low risk
The agent can save notes about your company or project to a file called devrel-context.md, so check that file before you commit or share the folder.
What it can do
- Read your data
- Create and change things
- Delete things
- Read-only mode
Watch out for
The notes file can hold unannounced dates
Anchors include launches and conferences, and SKILL.md says to store the anchors. Our advice: check devrel-context.md for embargoed details before you commit or share it. github.com
The plugin route installs the whole collection
The README's plugin and extension routes add every skill in the repo; its git tree holds 93. The repo has no hooks, agents, commands or MCP server files, and 14 of its skills bundle a script. Our advice: use the skills CLI command for this skill if you want only it. github.com
Security advisories
No published security advisories as of Nov 2, 2026.
Technical details
| Turning on read-only | SKILL.md describes no read-only mode. |
|---|---|
| Scopes |
|
Questions
How do I install devrel-content-calendar?
The README says to install every skill in the collection, because its skills reference each other. In Claude Code that is the plugin route in the install box above, which adds all 93 skills in the repo. The skills CLI can add just this one. Our advice: pick one route per agent.
What do I get at the end?
A quarterly plan with five sections: anchors, mix ratios, capacity model, slot table and review ritual with metrics. The slot table has ten columns, and the plan closes with which thresholds passed and what was cut.
Does it write the posts?
It does not. SKILL.md plans the slot and leaves producing each piece to per-format skills such as engineering-blog-post, which the README describes as writing or editing a technical post a skeptical developer audience believes.
How many posts can a small team ship?
SKILL.md quotes Snyk's stated output of one to two blog posts per advocate per month as a challenge tool, not a ceiling, and says to size by reviewer passes and compare with your own last quarter.
Why does it put evergreen content first?
SKILL.md ranks evergreen-compounding first on efficiency because promotional and event work arrives with deadlines and sponsors, while evergreen work gets pushed when week 8 goes wrong. It calls the ranking a correction, not a preference.
Does devrel-content-calendar need an API key, and where does it work?
SKILL.md names no API key, account or environment variable. The README documents installs for Claude Code, Claude.ai (add the repo as a plugin marketplace), Codex, Cursor, Gemini CLI and any Agent Skills-compatible tool through the skills CLI. The install box has the steps for each.
Is devrel-content-calendar safe to install?
It is instructions plus three reference files, and the folder bundles no scripts. SKILL.md may have the agent read your existing files, such as an audience profile or a current calendar, and save quarter ratios, capacity model and kill rules to memory, with devrel-context.md as the file when memory is a file. Our advice: do not put embargoed launch details in a file that is committed or synced.
Information
updated Nov 2, 2026
- Repository
- samber/developer-relations-skills
- Folder
skills/devrel-content-calendar
Sources
Docs, issue trackers and discussions this page is built from.
Show all 2Hide
- developer-relations-skills README · github.com
- devrel-content-calendar SKILL.md · github.com