Creator Content Ops logo

Creator Content Ops

Community
somnus0x
creator-content-ops

Turn a content creator's AI stack into a factory that sounds like THEM. One voice spine (CONTENT.md) governs every format — FB/blog posts, TikTok carousels, YouTube Shorts, covers — so the output stops smelling like AI and comes out consistent every run. Use when a creator (not a dev) wants to set up Claude Code / an AI agent for content production across channels, or fix output that reads generic, breaks Thai fonts, or looks different every gen. Triggers: "setup AI for content", "brandbook for AI", "AI writes generic", "content creator claude md", "carousel/shorts pipeline", "cover generator".

Overview

Publishersomnus0x
Repositoryagt-skill-pack
Skill namecreator-content-ops
Stars
74
Forks
17
Bundled files
6
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 6 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by somnus0x on GitHub. Read the source before you install it.

Installation

Install the Creator Content Ops AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/somnus0x/agt-skill-pack/tree/main/skills/creator-content-ops
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/somnus0x/agt-skill-pack.git /tmp/agt-skill-pack
mkdir -p .claude/skills
cp -r /tmp/agt-skill-pack/skills/creator-content-ops .claude/skills/creator-content-ops
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Creator Content Ops in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Creator Content Ops on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Creator Content Ops is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

creator-content-ops — make your AI stack sound like YOU, across every channel

You are the example. If you run a page, a channel, a blog, you already have a voice. The problem is your AI doesn't. Ask it to "write like me" and it writes like the internet: ten drafts, ten different people, none of them you. Ask it to "gen a carousel" and the Thai fonts shatter, card 3 looks nothing like card 4, and every regen is a coin flip. That is not a model problem. It is a missing-system problem.

This kit is the system. Not a Canva brandbook with a color palette. A rule set your AI reads before it writes anything, plus the production layer that renders instead of gambles. Four formats, one spine:

  • CONTENT.md — your voice, extracted once, loaded every session. The 3 filters that catch AI-smell before it ships. This is the heart. Everything else reads it.
  • carousel/ — TikTok/IG carousels where AI gens the background and CODE renders the text. Thai never breaks, because it is rendered with a real font, not generated.
  • shorts/ — YouTube Shorts / TikTok clip assembly from your raw material.
  • covers/ — post covers, two paths: a code-composed neutral template (pixel-exact, free, every time) and a Codex ImageGen path (creative, one-offs, diagrams).

The split that makes it a factory, not a craft:

AI gens what needs imagination. Code composes what needs consistency. Backgrounds, art, hero shots → AI. Text, layout, export → code. Never let AI draw the words on the card. Render them.

When to use / not use

Use when a creator wants to set up an AI content stack, or fix these symptoms:

  • output reads generic / "sounds like AI" no matter how you prompt it
  • Thai (or any complex-script) text breaks when AI generates the image
  • a carousel/series comes out inconsistent card-to-card
  • every asset is hand-made one at a time in Canva and it doesn't scale

Do NOT use for: dev-repo setup (that's claude-md-setup — same bones, code target), one-off single images with no voice/consistency need, or video editing craft. This kit is about turning repeatable content into a governed pipeline.

Setup first — build YOUR CONTENT.md before anything else

Do not copy someone else's voice file. Run the interview in SETUP.md — it asks you for your writing samples, your no-go words, your channels, and your tool auth, then writes a CONTENT.md calibrated to you. Ten minutes. Every module below reads the file it produces, so nothing works right until it exists.

1. Read SETUP.md          → answer the interview, hand over 5-10 real samples
2. It writes CONTENT.md   → your voice spine (3 filters + per-platform rows)
3. Wire the modules       → point carousel/shorts/covers at your fonts + CONTENT.md
4. Produce               → every format now reads CONTENT.md before it generates

The modules

ModuleWhat it doesAI or codeDeps
CONTENT.mdvoice spine + 3 AI-smell filters, read every session—none
reference/carousel_factory.pyJSON → PIL render, Thai/Latin tofu-fixcodePillow, fonts
reference/cover_neutral.pypixel-exact cover from a template you rebrandcodePillow, fonts
reference/codex_imagegen.mdcreative backgrounds / diagrams via Codex CLIAICodex CLI authed
reference/shorts_pipeline.mdShorts assembly from raw materialcode + AIffmpeg, Pillow

Principles

  • You are the training data. The kit does not invent a voice. It extracts yours from real samples and enforces it. Garbage samples in, generic voice out.
  • One spine, many formats. A carousel and a Short and a blog post all read the same CONTENT.md. That is why they sound like one person instead of four tools.
  • The kit ships the method, not your moat. Copy the render tricks and the voice system. Your finished channel, your trained voice model, your private auth stay yours.

Portable across agents

Nothing here is Claude-only. CONTENT.md is plain markdown any agent reads; the render engines are plain Python. Claude Code loads the voice file with @CONTENT.md; Cowork, Cursor, and Amp each have their own load step (a context file, an AGENTS.md, a settings path). The method is portable, the wiring per agent is one line.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Creator Content Ops AI skill do?

Turn a content creator's AI stack into a factory that sounds like THEM. One voice spine (CONTENT.md) governs every format — FB/blog posts, TikTok carousels, YouTube Shorts, covers — so the output stops smelling like AI and comes out consistent every run. Use when a creator (not a dev) wants to set up Claude Code / an AI agent for content production across channels, or fix output that reads generic, breaks Thai fonts, or looks different every gen. Triggers: "setup AI for content", "brandbook for AI", "AI writes generic", "content creator claude md", "carousel/shorts pipeline", "cover generat...

Why use Creator Content Ops on TypingMind?

Because you install it once and use it with any model. Creator Content Ops is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Creator Content Ops in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/somnus0x/agt-skill-pack/tree/main/skills/creator-content-ops. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Creator Content Ops?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Creator Content Ops?

As many as you like. As long as a model supports skills, you can use Creator Content Ops with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Creator Content Ops AI skill free?

Yes. It is published on GitHub by somnus0x under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇