Skip to content
cccskills
FreePublished on GitHub

codexkit-content-calendar-assembler

Turn launch dates, campaign inputs, and asset requests into a structured content calendar and workback plan. Use when the work is recurring marketing coordination and schedule packaging. Do not use for brand strategy, positioning design, or deep performance interpretation.

The English summary is being prepared. Showing the original description.

See how to install

Files included (2)

  • SKILL.md2.7 KB
  • agents/openai.yaml186 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Content Calendar Assembler

Purpose

Build a reliable publishing and asset schedule from scattered campaign inputs.

When to use

  • campaign dates change often
  • marketing ops or content leads need one clean calendar
  • asset dependencies are getting lost across channels

When not to use

  • the user needs positioning or message strategy
  • success depends on deep channel analysis rather than schedule coordination

Inputs

  • campaign or launch dates
  • channel list
  • asset requests and owners
  • known dependencies and review deadlines

Procedure

  1. Normalize work into campaign, channel, asset, owner, and date.
  2. Build the workback order from launch date backward.
  3. Flag dependencies and missing owners.
  4. Separate confirmed dates from assumptions.
  5. End with a calendar summary and the most likely schedule risks.

Output

  • structured content calendar
  • asset workback plan
  • dependency and risk list

Definition of done

  • the launch plan is visible in one place
  • owners and dates are clear enough to coordinate work
  • the output is ready for a campaign manager review

Examples

  • "Turn these launch notes into a content calendar with owners and dates."
  • "Build a workback plan from this campaign brief and asset list."

Quality Criteria

  • Trigger conditions and input requirements are unambiguous
  • Each automated step produces a verifiable output
  • Error handling and fallback paths are defined
  • Manual override points are documented

Verification (4C)

CheckQuestion
CorrectnessDoes the workflow produce the expected output for the defined inputs?
CompletenessAre all trigger conditions, edge cases, and error paths handled?
Context-fitIs the automation appropriate for the frequency and criticality of this task?
ConsequenceIf this ran unattended and failed silently, what would the downstream impact be?

Edge Cases

  • Input format varies unexpectedly — Add a normalization step at entry. Alert the operator on format mismatches.
  • Downstream system is unavailable — Queue the output and retry with exponential backoff. Alert after N failures.
  • Partial execution completes — Ensure idempotency — re-running from the start produces the same result without duplication.

Changelog

  • v1.0.0 — Initial release

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Design rigorous A/B test plans with hypothesis, sample size calculation, Minimum Detectable Effect (MDE), randomization strategy, and decision rules. Includes guardrail metrics and rollout playbook. Use when planning product experiments, conversion optimization, or data-driven feature decisions.

The English summary is being prepared. Showing the original description.

hoavdc/CodexKit25Updated Oct 11, 2026

Review REST and GraphQL API designs for consistency, usability, and best practices. Covers naming conventions, versioning strategy, error format, pagination, authentication patterns, and breaking change detection. Use when reviewing API specs, designing new APIs, or auditing existing endpoints.

The English summary is being prepared. Showing the original description.

hoavdc/CodexKit25Updated Oct 11, 2026

Write Architecture Decision Records (ADRs) following the Michael Nygard format. Captures context, options considered, decision rationale, and consequences. Use when making technology choices, framework selections, or any architectural decision that future developers need to understand.

The English summary is being prepared. Showing the original description.

hoavdc/CodexKit25Updated Oct 11, 2026

Assess organizational readiness for financial audits (internal or external). Map assertions to account balances, check evidence completeness, score readiness using a Red/Amber/Green framework, and generate a remediation timeline. Aligned with SOX, IFRS, and GAAP audit standards. Use before scheduled audits or when preparing for first-time compliance.

The English summary is being prepared. Showing the original description.

hoavdc/CodexKit25Updated Oct 11, 2026

Design safe recurring Codex automations with clear prompts, outputs, schedules, and gating rules.

The English summary is being prepared. Showing the original description.

hoavdc/CodexKit25Updated Oct 11, 2026

Refine Product Backlog Items to meet INVEST criteria. Write User Stories with Acceptance Criteria in Given/When/Then format, estimate with Story Points, and flag dependencies. Use before sprint planning when backlog items need grooming. Do not use to prioritize the backlog — that is the Product Owner's decision.

The English summary is being prepared. Showing the original description.

hoavdc/CodexKit25Updated Oct 11, 2026

See all skills by hoavdc

Report a problem with this skill