Content Calendar Scheduler

Plan content publishing schedules with editorial calendar views. Use when scheduling posts, planning campaigns, tracking publishing deadlines.

Security Scan

The skill's code, instructions, and resource usage are consistent with a local content-calendar helper; it only writes simple logs to a user data directory and does not request credentials or network access.

Purpose & Capability

Name/description (content calendar / scheduling / drafting) align with the included shell script and SKILL.md. No unrelated binaries, services, or credentials are requested.

Instruction Scope

SKILL.md and the script confine behavior to local content generation helpers and logging. The script only outputs text and appends timestamped entries to $DATA_DIR/history.log; it does not read unrelated system files, contact external endpoints, or attempt to exfiltrate data.

Install Mechanism

No install spec or remote downloads are present; the skill is instruction-only with an included bash script. Nothing in the package pulls code from arbitrary URLs or installs external packages.

Credentials

Only an optional CONTENT_CALENDAR_SCHEDULER_DIR env var is used (with fallback to XDG_DATA_HOME or HOME). No API keys, tokens, or unrelated environment variables are required.

Persistence & Privilege

The skill does not request always:true, does not modify other skills or system-wide agent settings, and its persistent footprint is limited to a per-user data directory where it writes logs.

Assessment

This skill appears to be a simple local CLI helper that writes a history log into ~/.local/share/content-calendar-scheduler (or whatever you set via CONTENT_CALENDAR_SCHEDULER_DIR). Before running, review the included scripts/script.sh if you want to confirm behavior; consider setting CONTENT_CALENDAR_SCHEDULER_DIR to a directory you control if you prefer logs in a custom location. There are no network calls or credential requests in the package.

Content creation and optimization assistant for drafting, outlining, scheduling, and analyzing content from the command line.

Commands

Command	Description
draft	Create a content draft with a target word count (default 800 words)
headline	Generate multiple headline variations for a topic
outline	Produce a structured content outline (Intro → Problem → Solution → Examples → CTA)
seo	Get SEO tips including keywords, title tags, meta descriptions, headings, and internal links
schedule	Generate a weekly content schedule (Mon: Research → Fri: Promote)
hooks	Suggest opening hook styles (Question, Statistic, Story, Bold claim, Controversy)
cta	Generate call-to-action suggestions (Subscribe, Share, Comment, Try it, Learn more)
repurpose	Show repurposing pipeline (Blog → Thread → Video → Carousel → Newsletter)
metrics	Display key content metrics to track (Views, Clicks, Shares, Time on page, Conversions)
ideas	Generate content format ideas (How-to, Listicle, Case study, Interview, Comparison)
help	Show help and list all commands
version	Print current version

Usage

content-calendar-scheduler <command> [args]

All actions are logged to $DATA_DIR/history.log for auditing.

Data Storage

• Default directory: ~/.local/share/content-calendar-scheduler/
• Override: Set the CONTENT_CALENDAR_SCHEDULER_DIR environment variable to change the data directory.
• Files:
  • history.log — timestamped log of every command executed
  • data.log — general data log

Requirements

• Bash 4+ (uses set -euo pipefail)
• No external dependencies or API keys required
• Works on Linux, macOS, and WSL

When to Use

1. Planning a content calendar — Run content-calendar-scheduler schedule to generate a weekly publishing plan with dedicated days for research, writing, editing, publishing, and promotion.
2. Starting a new blog post — Use content-calendar-scheduler draft "topic" to create a draft framework, then content-calendar-scheduler outline "topic" for a structured outline.
3. Optimizing for search engines — Run content-calendar-scheduler seo "keyword" to get SEO recommendations including title tags, meta descriptions, and heading structure.
4. Generating headline ideas — Use content-calendar-scheduler headline "topic" to get multiple headline variations before committing to a title.
5. Repurposing existing content — Run content-calendar-scheduler repurpose to see how to transform a blog post into threads, videos, carousels, and newsletters.

Examples

# Create a draft about remote work
content-calendar-scheduler draft "remote work tips"

# Generate headlines for a topic
content-calendar-scheduler headline "AI in healthcare"

# Get a content outline
content-calendar-scheduler outline "startup funding"

# Get SEO tips for a keyword
content-calendar-scheduler seo "content marketing"

# Generate a weekly schedule
content-calendar-scheduler schedule

# Get opening hook ideas
content-calendar-scheduler hooks

# Generate call-to-action suggestions
content-calendar-scheduler cta

# View content repurposing pipeline
content-calendar-scheduler repurpose

# Check key content metrics
content-calendar-scheduler metrics

# Get content format ideas
content-calendar-scheduler ideas

Output

All command output goes to stdout. Redirect to a file if needed:

content-calendar-scheduler draft "topic" > draft.txt
content-calendar-scheduler outline "topic" > outline.md

Configuration

Set CONTENT_CALENDAR_SCHEDULER_DIR to customize where data is stored:

export CONTENT_CALENDAR_SCHEDULER_DIR=/path/to/custom/dir

---

Powered by BytesAgain | bytesagain.com | [e-mail]