Mastering Claude Co-Work
Course
Mastering Claude Co-Work
Module 10 of 18

Content Creation and Repurposing

Turn one source into ten outputs — build a content repurposing pipeline that handles the mechanical work automatically.

What you'll learn

Build a complete content repurposing pipeline from a single URL or recording to multiple output formats
Configure a skill that preserves brand voice by feeding existing examples to the Skill Creator
Design a content workflow that uses at least two connectors in sequence
Apply the "Garbage In, Treasure Out" principle to multi-source content synthesis

The Content Operations Problem

Most people who create content are leaving enormous value on the table. They record a podcast episode that has 45 minutes of insight and extract it into one audio file. They write a detailed client proposal that contains paragraphs that would make excellent LinkedIn posts. They run a customer call with quotable moments that never become marketing material.

The bottleneck isn't ideas — it's bandwidth. Repurposing content is mechanical, repetitive work: transcribing, summarizing, reformatting, adapting for different platforms, maintaining consistent voice across formats. It's exactly the kind of work Co-Work was designed to eliminate.

Content repurposing pipeline: one input fans out to multiple simultaneous outputs — social captions, email, blog, slides, video script

Garbage In, Treasure Out

Personal Framing — Jenny (Anthropic)

"Garbage In, Treasure Out" is a personal framing articulated by Jenny at Anthropic. It is her individual explanation, not official product messaging. The underlying capability it describes — Co-Work's ability to synthesize value from messy, multi-source inputs — is verified.

Jenny's framing inverts the traditional computing axiom. In standard software, bad input produces bad output — GIGO. In Co-Work content work, the messy inputs that would defeat traditional tools are exactly where Co-Work excels. Raw transcripts with filler words. Meeting recordings where three people talk over each other. Rough notes that are half-formed ideas. PDF reports with dense data tables.

Co-Work doesn't need clean input. It can extract signal from noise. That means your starting material doesn't need to be polished — it needs to be present. The synthesis is Co-Work's job.

The Repurposing Pipeline Architecture

The fundamental pattern: one input source, processed by Co-Work, producing multiple simultaneous outputs tailored for different contexts.

Input sources:

  • YouTube URL — Co-Work extracts the transcript via YouTube connector or Chrome
  • Meeting recording — upload or reference via Drive; Co-Work transcribes and analyzes
  • PDF or document — uploaded or referenced from Drive; Co-Work reads and extracts
  • Web article URL — Co-Work reads via Chrome or web connector
  • Raw notes — pasted directly into the conversation or saved in the content folder

Output formats (all generated from the same input in one pass):

  • LinkedIn post — professional, voice-matched, 150–300 words
  • Twitter/X thread — headline hook + 5–7 supporting points
  • Email newsletter paragraph — summary for existing subscriber context
  • Blog post outline — H2 structure with key points per section
  • Slide deck outline — 5–8 slides with titles and bullet points
  • Video script intro — 60-second hook version of the same content

Brooke Wright built and documented this end-to-end repurposing workflow. Paul extended it into a full content OS. The key insight they share: Co-Work generates all formats simultaneously, not sequentially. You're not running one prompt per format — you're running one repurposing skill that outputs everything at once.

YouTube Transcript Extraction with Timestamps

For video content, Jack Roberts recommends extracting transcripts with two levels of timestamps: chapter-level (by major topic) and minute-level (for precise quotes). The prompt structure:

Extract the transcript from [YouTube URL].
Format: Chapter headings with timestamps, then
line-by-line transcript with minute markers.
Identify the top 5 most quotable moments with exact text.

The output gives you: timestamped show notes for the video description, specific quotes for social posts, chapter titles for long-form content, and a searchable reference document for future repurposing runs.

Brand Voice Preservation

Automated content generation has one persistent failure mode: it sounds like it was generated by a machine. The technical execution is correct, but the voice is generic. This destroys the value for anyone who has spent years building a recognizable communication style.

Brand voice preservation flow: examples go into voice-reference.md, skill references it, outputs maintain consistent voice

Brooke Wright's solution is the voice reference document. The process:

  1. Identify your 3–5 best existing content pieces — the ones that best represent your authentic voice
  2. Create a file called voice-reference.md in your Content folder
  3. Add those examples in full, with a note about what makes each one work
  4. When creating your Content Repurposer skill, feed these examples to the Skill Creator
  5. Add to the skill instructions: "Match the voice, sentence length, and energy of the examples in voice-reference.md"
Examples Solve the Voice Problem

Feed the Skill Creator 3–5 examples of your best existing content. Voice consistency is not solved by describing your voice — it is solved by showing it. The more representative your examples, the more accurately Co-Work will match your style in generated outputs.

The Monday Morning Insights Ritual

Personal Workflow — Jenny (Anthropic)

The Monday Morning Insights Ritual is Jenny's personal workflow at Anthropic. It is her individual practice, not an official Anthropic recommendation or product feature. The underlying capability — multi-source synthesis followed by presentation generation — is verified.

Jenny describes her Monday morning ritual as a three-prompt sequence that turns a week's worth of inputs into actionable priorities plus a shareable presentation:

  1. Multi-source synthesis: Pull in data from multiple sources (user research, analytics, customer feedback, market signals) and synthesize into key themes
  2. Feature priorities: From the themes, extract what the team should focus on this week and why
  3. Presentation: "These are my insights. Create a presentation with 8 slides." Export to Google Slides via connector
Monday Morning Insights Ritual: multi-source input flows to synthesis, then priorities, then presentation

This same pattern applies far beyond Monday mornings. Quarterly business reviews. Client check-ins. Research summaries. Any workflow where the value is in synthesizing multiple sources into a coherent narrative and then formatting it for presentation.

Presentation Creation

When Co-Work generates a slide deck outline, the natural next step is exporting to a real presentation. With the Google Slides connector active, the prompt is straightforward:

Take these insights and create a presentation
with 8 slides in Google Slides.
Title slide, 6 content slides with bullet points,
closing next-steps slide.

Four sources — Jenny, Paul, Jack Roberts, and Brooke Wright — all describe presentation generation as one of the highest-ROI Co-Work workflows. The manual version takes an hour or more; the automated version takes a few minutes of review and editing.

Content Operations OS

Paul's content OS is the full stack version of what this module introduces. It combines everything:

  • A dedicated ~/CoWork/Content/ folder with a voice-reference document and content-specific claude.md
  • A Content Repurposer skill that takes any input format and produces all outputs simultaneously
  • A Voice Checker skill that reviews outputs against the voice reference before finalizing
  • A Content Calendar skill that suggests what to publish and when based on pipeline state
  • Scheduled weekly runs that process accumulated inputs and surface content ideas
Always Review Before Publishing

Auto-generated content requires human review before publication. Co-Work can match your voice closely — but factual accuracy, nuance, and context-specific judgment still require your eyes on the output. Build a review step into every content workflow before any content leaves your drafts folder.

Build-Along Exercise

Build a Content Repurposing Skill

Step 1: Find your source material. Choose one YouTube video or web article URL that is relevant to your work. This becomes the test input for your repurposing skill.

Step 2: Manual pass first. Run the repurposing manually: extract key points from the source, write one LinkedIn post in your voice, write one email paragraph. This is the quality benchmark your skill needs to match.

Step 3: Create your voice reference. Create voice-reference.md in your Content folder. Paste in 2–3 of your best existing content pieces with notes on what makes each work. This file becomes the voice anchor for your skill.

Step 4: Build the skill. After the manual run, say "This was fantastic. Create a skill now." Review the generated skill. Add an instruction line: "Match the voice and style of examples in voice-reference.md." Adjust trigger keywords to include "repurpose", "content brief", "content from URL".

Step 5: Test on a different URL. Run the new skill on a different source URL. Compare the output quality and voice consistency against your manual benchmark. Use the reflection prompt to improve the skill based on what you observe.

Success criteria: One "Content Repurposer" skill that takes a URL and produces at least two on-brand outputs without manual prompt engineering. Voice reference integrated. Output reviewed and passes your quality standard.

Knowledge Check
I have built a Content Repurposer skill that works from a URL input and produces multiple formats simultaneously
My skill includes a voice reference document — and I understand why examples solve voice consistency better than descriptions
I understand "Garbage In, Treasure Out" — Co-Work's strength is synthesizing messy inputs, not requiring clean ones
I can configure a content pipeline that uses at least two connectors in sequence (e.g., YouTube + Google Slides)
I always review auto-generated content before publishing — the review step is built into my workflow, not an afterthought