---
name: creator-content-workflow
description: Turn source material (notes, an article, a transcript, a product update) into fact-checked social posts adapted per platform, then review and schedule them. Use when a creator asks to repurpose content, write a thread, plan a week of posts, or adapt one idea for X, Threads, LinkedIn, Instagram, TikTok or YouTube. With the Repping.ai MCP server connected, prepares drafts the creator approves in Repping.ai.
license: MIT
metadata:
  author: Repping.ai
  version: "1.0.0"
  homepage: https://www.repping.ai/mcp
title: creator-content-workflow
canonical_url: https://skilld.dev/gh/reppingai/repping-mcp
last_updated: 2026-11-13T06:30:24.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install reppingai/repping-mcp/creator-content-workflow`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/creator-content-workflow`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/reppingai/repping-mcp/creator-content-workflow) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/creator-content-workflow`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/creator-content-workflow --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/creator-content-workflow --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Creator content workflow

Follow the five steps in order. Do not skip the fact check or the review.

## 1. Gather the source
- Ask for, or read, the source material. Record its URL or file name.
- Ask who the audience is, what the goal is (reach, clicks, replies, sales) and which platforms to target.
- If a Repping.ai connection is available, call `repping_profile`. Then use `repping_read` to see recent posts and the calendar, so you don't repeat topics or double-book a slot.

## 2. Check the facts
- List every claim, number, name and date that the posts will use.
- Mark each one as **supported** (quote where it appears in the source) or **unsupported**.
- Drop unsupported claims, or ask the creator to confirm them. Never invent statistics, results or quotes.

## 3. Draft one core message
- Write the core idea in one sentence of 25 words or fewer.
- Write a hook, the body points and one call to action.
- Match the creator's own voice. If you have past posts, mirror their length, tone and emoji use.

## 4. Adapt per platform
Adapt the structure for each platform. Do not copy the same text everywhere.

| Platform | Shape |
| --- | --- |
| X | Hook post of 280 characters or fewer; a thread of 3–7 posts if needed; link in the last post |
| Threads | Conversational, 500 characters or fewer per post; a question invites replies |
| LinkedIn | First 2 lines decide "see more"; short paragraphs; a lesson framing |
| Instagram | Caption with the first line as the hook, a CTA to the link in bio and 3–5 relevant hashtags |
| TikTok / Reels / Shorts | A spoken script with a 2-second hook, 3 beats and on-screen text cues |
| YouTube community / Facebook | A plain summary plus a question |

Check each platform's current limits before you finalize. Limits change.

## 5. Review, then schedule
- Show every draft in a table: platform, text, character count, media needed, proposed time.
- Ask the creator to approve or edit each draft.
- **With Repping.ai connected:** call `repping_discover` to get the exact schema. Then call `repping_prepare` once per approved draft and give the creator each review link. Nothing publishes until they approve it in Repping.ai. Check outcomes with `repping_action_status`.
- **Without a connection:** output the final copy as a checklist that the creator can paste into any scheduler.

## Rules
- Never publish, schedule or send anything without explicit approval.
- Keep private data out of posts unless the creator includes it on purpose.
- Credit sources and collaborators where the platform supports it.

Repping.ai is a creator workspace with a free Link in Bio page, scheduling across 20 platforms, Auto DMs and analytics: https://www.repping.ai
