Навыки devrel-content-calendar

📦

devrel-content-calendar

Name: devrel-content-calendar
Author: samber

v1.0.1 Ревизия содержимого r1 Безопасно ⚙️ Внешние команды

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.

Поддерживает: Claude Codex Code(CC)

🥉 78 Бронза

Maintain this Skill? Claim it 🥉 78 Бронза

Установить с помощью моего Агента

Скопируйте этот запрос в своего Агента. Он содержит каноническую страницу Skill и манифест.

Запрос агента

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.

Ваш Агент по-прежнему должен показать план и запросить все подтверждения, требуемые политикой безопасности.

Ресурсы для AI-агентов

Используйте эти ссылки, когда AI-агенту, crawler или script нужен чистый контекст вместо полной страницы.

Markdown-детали GET /skills/samber-devrel-content-calendar.md Подписанный manifest GET /api/skills/samber-devrel-content-calendar/manifest Подписанный lockfile GET /api/skills/samber-devrel-content-calendar/lockfile

Протестировать

Использование «devrel-content-calendar». Plan Q3 for a developer tool with a week-four release, one writer, and a technical reviewer available three hours weekly.

Ожидаемый результат:

Quarter shape: confirm whether launch visibility or long-term adoption matters most before assigning dates.
Capacity model: estimate reviewer passes for each format and reserve 20% of estimated capacity for reactive work.
Release coverage: schedule preparation before week four and follow-up afterward, with named owners and reviewers.
Next input needed: team names, format estimates, audience priorities, and last quarter's shipped work.

Использование «devrel-content-calendar». Audit thirteen weekly blog slots owned by 'content team', with no reviewers, evidence, preparation work, or open capacity.

Ожидаемый результат:

Ownership check failed: assign a specific owner and reviewer to every committed slot.
Capacity check failed: reduce commitments to leave named reactive capacity.
Coverage check failed: add relevant documentation and another surface, with at least two journey stages.
Evidence check failed: attach observed demand or a written hypothesis to each topic.
Anchor check failed: schedule preparation and follow-up around each fixed deadline.

Аудит безопасности

Безопасно

v1 • 25.10.2026 Открыть версионный отчет

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.

Просканировано файлов

768

Проанализировано строк

Пункты проверки

Ложные срабатывания проигнорированы

Факторы риска

⚙️ Внешние команды (1)

SKILL.md:20

Последний завершенный статический и семантический аудит не обнаружил подтвержденных проблем безопасности. Это не доказывает отсутствие побочных эффектов у навыка.

Аудитор:: codex

Поделиться и цитировать этот отчет

Делитесь версионным отчетом об оценке, нейтральным значком, встраиваемой карточкой и цитатами. Skillstore публикует доказательства, не решая, безопасен ли этот Skill.

Открыть версионный отчет

Копировать ссылку на отчёт

https://skillstore.io/skills/samber-devrel-content-calendar/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Значок Markdown

[![Skillstore security assessment](https://skillstore.io/badges/skills/samber-devrel-content-calendar/security.svg)](https://skillstore.io/skills/samber-devrel-content-calendar?utm_source=security_passport_badge)

Значок HTML

<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>

Академические ссылки (APA · BibTeX · CFF)

Цитата APA

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

Цитата BibTeX

@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}
}

CITATION.cff

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"

Оценка Skillstore

Почему такая оценка Достоверность доказательств: Средний

Архитектура

100

Сопровождаемость

Контент

Сообщество

Соответствие спецификации

Что вы можете построить

Plan a release-heavy quarter

Coordinate launch preparation, evergreen guides, and follow-up slots without committing all capacity to one release date.

Size a small team's publishing workload

Identify technical review constraints and replace expensive formats with work that fits available capacity.

Audit an existing community content plan

Find missing owners, unsupported topics, coverage gaps, and overloaded weeks before proposing the smallest necessary changes.

Попробуйте эти промпты

Start a quarterly calendar

Help me plan next quarter's developer content for [product]. Ask about our audience, goals, fixed dates, and capacity before recommending a quarter shape.

Check what the team can ship

We have [writer availability] and [reviewer availability] for [quarter]. Assess [proposed formats and counts], estimate production passes, and recommend cuts with named slack.

Audit a slipping calendar

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.

Coordinate a constrained launch quarter

Plan [quarter] around [release dates], [accepted talks], and [agency commitments]. Use [audience goals], [capacity], and [past results]. Validate each plan section before proceeding.

Лучшие практики

Provide last quarter's shipped and delayed work before accepting default throughput assumptions.
Name each technical reviewer and estimate review passes before assigning publishing weeks.
Validate anchors, mix, capacity, slots, and review rules separately, with explicit decisions at each stage.

Избегать

Fill every week without reserving capacity for reactive work or delayed reviews.
Treat repurposed assets, agency writing, or conference preparation as work that consumes no internal capacity.
Present an evergreen ratio or one company's publishing output as a universal benchmark.

Часто задаваемые вопросы

Does this skill write the scheduled content?

No. It plans the quarter and assigns slots. Individual articles, guides, release notes, and talks belong to separate format-specific workflows.

What information should I provide first?

Provide the product, quarter, audience, funding goal, fixed dates, writer availability, reviewer availability, and recent publishing results.

Can it review a calendar I already have?

Yes. Audit mode checks the existing plan, orders failures by impact, and recommends the smallest changes needed to clear its checks.

Does 80/20 mean evergreen versus trending content?

No. Its 80/20 convention divides committed capacity from reactive room. The evergreen share depends on the chosen quarter shape and team evidence.

Will it publish or synchronize my calendar?

No automated publishing or synchronization integration is included. The output is a planning document with anchors, mix ratios, capacity, slots, and review metrics.

Does it store planning context?

The instructions support persistent memory when available. File-based memory uses devrel-context.md; another existing memory system may be used instead.