OpenSkillIndex← back to search
claude-code

Marketing-pipeline draft

Generate social media posts for a project. Draft them yourself following the voice rules below, then validate with the anti-slop gate.

install
source · Clone the upstream repo
git clone https://github.com/robertnowell/marketing-pipeline
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/robertnowell/marketing-pipeline "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/draft" ~/.claude/skills/robertnowell-marketing-pipeline-draft && rm -rf "$T"
manifest: skills/draft/SKILL.md
source content

Draft posts

Generate social media drafts for a project in the marketing pipeline. YOU draft the posts directly — do not call 

marketing draft
(that uses a separate API call).

Step 1: Load project data

marketing plan

Then read the project's entry in projects.yml to get the problem, solution_one_liner, facts, and angles.

Step 2: Draft following these rules

Voice rules (non-negotiable):

  • Lead with the USER'S problem, not the technology. First sentence names the pain.
  • First person, past tense where possible ("shipped", "built", "wrote")
  • Specifics over enthusiasm. Fact density is a virtue; padding is the failure mode.
  • No marketing tokens: "excited", "game-changer", "unlock", "empower", "introducing", "solution", "leverage", "journey"
  • No AI shorthand: "AI-powered", "AI-driven", "powered by AI"
  • No emoji, hashtags, exclamation points, rhetorical questions, URL shorteners
  • No filler openings: "Let's dive in", "In this post", "Buckle up"
  • End with the full github.com/... URL

Channel length limits:

  • Bluesky: 300 characters max (count carefully)
  • Mastodon: 500 characters max
  • X: 280 characters max
  • Dev.to / Hashnode: 150-400 words, prepend 
    # Title
    on first line

Generate 3 candidates for the requested channel. Show all 3.

Step 3: Validate each candidate

Write each draft to a temp file and validate:

echo 'draft text here' | marketing validate --channel bluesky

If FAILED, fix the violations and revalidate. Only present candidates that PASS to the user.

Step 4: Save the best one

Save the user's chosen draft to 

content/drafts/{project}/{channel}/
.

Image posts (for projects with content_source like Kopi)

If the project has a 

content_source
in projects.yml, the post includes a screenshot image. For these:

  1. Fetch the image URL from the content source API
  2. View the image with Read before approving — check that:
    • Hero/header section is fully rendered (no blank or grey areas at top)
    • Content is not cut off at the bottom
    • No broken image placeholders
    • Layout looks complete and professional
  3. If the image has rendering issues, skip it and try the next one
  4. Validate the image programmatically: 
    marketing validate-image --url <image_url>
  5. Write the caption as a human would — NOT a feature checklist. Good: "Dark theme, high-contrast CTAs, the countdown timer is a nice touch. Built with Kopi." Bad: "scored 93/100. Layout hierarchy, mobile readability, CTA contrast checked."
  6. All URLs must start with 
    https://
    — bare domains like 
    trykopi.ai/emails
    won't be clickable