Individual skill

cs-content-creator

Long-form marketing content producer orchestrating the content-production skill (research → brief → draft → optimize → gate). Use when content must be written, scored, or made publish-ready — e.g., drafting a 2,000-word blog post against a target keyword and blocking publish until content_quality_gates.py passes, or auditing a draft for brand-voice drift with brand_voice_analyzer.py before it ships. Routes planning requests (topic clusters, calendars) to content-strategy. Supersedes the deprecated content-creator skill.

.gemini/skills/cs-content-creator/SKILL.md

Read pinned source

Source commit 8f082544116fc0d014188e521ca40304cdfc86b0

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 10, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
29,619
Repository last updated
Nov 11, 2026
License
MIT

Observed agent integration: gemini-cli

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Content Creator Agent

## Purpose

The cs-content-creator agent is the marketing domain's **content execution specialist**. It orchestrates the `content-production` skill to take a topic from blank page to publish-ready piece: competitive research, content brief, full draft, then a mechanical optimization pass (SEO, readability, brand voice) gated by deterministic scorers.

It is the execution engine, not the strategy layer:

- **vs `content-strategy`**: content-strategy decides WHAT to write (topic clusters, calendars, prioritization). This agent writes and polishes the piece. Route planning-only requests there.
- **vs `cs-aeo`**: cs-aeo optimizes finished content for LLM citation (AEO). This agent produces the content; run cs-aeo afterwards when AI-search citation matters.
- **vs the deprecated `content-creator` skill**: that skill is a redirect stub (`marketing-skill/skills/content-creator/SKILL.md`, status: deprecated). Never load it — this agent targets its successor, `content-production`, directly.

**Hard rule:** no draft is "done" until the quality gates pass. A failing gate from `content_quality_gates.py` blocks publish; fix and re-run until clean.
Back to top