Plan a Realistic DevRel Content Calendar
Developer-content plans slip when writing commitments ignore technical review and fixed deadlines. This skill builds quarterly publishing slots with named owners, reviewers, capacity estimates, and reserved reactive time.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "devrel-content-calendar" from https://skillstore.io/skills/samber-devrel-content-calendar.md and its manifest at https://skillstore.io/api/skills/samber-devrel-content-calendar/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Using "devrel-content-calendar". Plan Q3 for a developer tool with a week-four release, one writer, and a technical reviewer available three hours weekly.
Expected outcome:
Using "devrel-content-calendar". Audit thirteen weekly blog slots owned by 'content team', with no reviewers, evidence, preparation work, or open capacity.
Expected outcome:
Both static findings are false positives: the evaluation prompt discusses content planning, and the backticks format a memory filename. No evidence found of reconnaissance, shell execution, exfiltration, or instructions intended to manipulate the audit in the reviewed files. Optional context persistence is part of the documented planning workflow.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
https://skillstore.io/skills/samber-devrel-content-calendar/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/samber-devrel-content-calendar?utm_source=security_passport_badge)<a href="https://skillstore.io/skills/samber-devrel-content-calendar?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/samber-devrel-content-calendar/security.svg" alt="Skillstore security assessment" loading="lazy"></a><iframe src="https://skillstore.io/embed/skills/samber-devrel-content-calendar.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>samber. (2026). devrel-content-calendar security audit report (audit version 1) [Author version 1.0.1]. Skillstore. https://skillstore.io/skills/samber-devrel-content-calendar/audits/1@techreport{samber-samber-devrel-content-calendar-2026,
author = {samber},
title = {devrel-content-calendar security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/samber-devrel-content-calendar/audits/1},
note = {Author version 1.0.1}
}cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "devrel-content-calendar security audit report (audit version 1)"
version: "1.0.1"
type: report
authors:
- name: "samber"
date-released: "2026-10-25"
url: "https://skillstore.io/skills/samber-devrel-content-calendar/audits/1"
identifiers:
- type: other
value: "skillstore:samber-devrel-content-calendar:audit:1"
description: "Skillstore immutable audit report identifier"
Coordinate launch preparation, evergreen guides, and follow-up slots without committing all capacity to one release date.
Identify technical review constraints and replace expensive formats with work that fits available capacity.
Find missing owners, unsupported topics, coverage gaps, and overloaded weeks before proposing the smallest necessary changes.
Help me plan next quarter's developer content for [product]. Ask about our audience, goals, fixed dates, and capacity before recommending a quarter shape.
We have [writer availability] and [reviewer availability] for [quarter]. Assess [proposed formats and counts], estimate production passes, and recommend cuts with named slack.
Audit this existing developer-content calendar: [calendar]. Report failed checks in damage order and propose minimal changes. Ask for missing evidence, owners, reviewers, and capacity.
Plan [quarter] around [release dates], [accepted talks], and [agency commitments]. Use [audience goals], [capacity], and [past results]. Validate each plan section before proceeding.
Author
samberLicense
MIT
Author version
v1.0.1
Skillstore revision
r1
Ref
e7963efdc368d1561443c6903135858aa85494b1
Maintenance freshness
10/25/2026
Usage
0 downloads · 0 views
File structure
Write Clear Go Documentation
Go projects often have incomplete comments, examples, and contributor guidance that slow adoption and maintenance. This skill provides structured guidance for writing, reviewing, and organizing documentation that matches Go conventions.
Optimize Go Performance With Profiling
Go services often slow down from allocations, GC pressure, I/O waits, or inefficient hot paths. This skill maps profiling signals to focused Go performance fixes and benchmark validation.
Stay Current with the Go Ecosystem
Go developers can lose time sorting through scattered news, communities, and learning sources. This skill provides a focused directory and practical update routine.
Design a Focused Developer Relations Charter
Developer relations teams can spread limited capacity across activities without a clear business purpose. This skill guides interviews and decisions into a focused, reviewable charter.
Build Go Collection Pipelines with samber/lo
Manual Go collection transformations can become repetitive and difficult to optimize. This skill applies samber/lo helpers while explaining package choice, compatibility, errors, and performance tradeoffs.
Build Reliable Go CLI Commands
Go CLI projects often become inconsistent around command structure, validation, hooks, output, and tests. This skill provides practical Cobra patterns for predictable commands and maintainable test suites.
Plan Agile Sprints With Clear Capacity
by shubhamsaboo
Sprint planning often stalls when scope, estimates, and capacity are unclear. This skill guides Claude, Codex, and Claude Code to create sprint goals, backlog tables, risks, and done criteria.
Plan Focused, Achievable Sprints
by C0ntr0lledCha0s
Teams often overcommit because backlog priority, capacity, and dependencies are considered separately. This skill combines them into a structured sprint plan with measurable goals.
Manage Proxmox Storage Capacity
by DataKnifeAI
Proxmox storage can become hard to track across nodes, pools, and workloads. This skill helps Claude, Codex, and Claude Code review storage capacity, utilization, and expansion needs.
Monitor Proxmox Performance and Capacity
by DataKnifeAI
Proxmox teams need a clear view of node and workload health. This skill guides Claude, Codex, and Claude Code through monitoring, bottleneck analysis, and capacity planning.
Generate Infrastructure Reports
by DataKnifeAI
Network teams need clear reports from scattered infrastructure data. This skill turns health, device, client, WiFi, firewall, and capacity data into structured reports.
Find and Prioritize Content Gaps
by aaron-he-zhu
Content teams often lack evidence for what to publish next. This skill compares competitor coverage and turns missing opportunities into a prioritized editorial plan.