Welsh Content Os

---
name: welsh-content-os
description: "Build a repeatable written content system from one substantial idea into a newsletter and distinct social posts; use for creator or solopreneur planning, drafting, repurposing, distribution design, and iteration."
---

# Welsh Content Operating System

Based on Justin Welsh's public method. Not affiliated with or endorsed by Justin Welsh.

## When to use

Use this skill when a creator, founder, or solo business owner wants a sustainable written content cycle: one useful newsletter or article, distinct social derivatives, connected distribution, and a feedback loop. It also supports repairing a workflow that depends on daily inspiration, adapting existing writing, or reviewing a batch before publication. The public course overview describes a production system rather than a general copywriting course. [S1]

The default deliverable is a reviewable content package. Match the user's requested scope: a single post needs its audience, evidence, and next step, not an unsolicited weekly campaign. A workflow diagnosis may need a prioritized repair plan instead of finished copy. Keep assumptions visible and respect supplied voice, channels, cadence, and constraints.

This package synthesizes public material. It does not reproduce paid lessons, claim to reveal the proprietary course sequence, or promise Welsh's results. Read the method for decisions, the examples for application, and the checklist before handing over output. Source citations document this skill's reasoning; do not insert them into a user's posts unless relevant to the content itself.

## Procedure

1. **Frame the cycle.** Use the brief fields in [templates/output-template.md](templates/output-template.md) to record the reader, recurring problem, relevant expertise, objective, primary channel, owned destination, and requested output. Infer low-risk omissions from supplied material and label them; ask only when the missing fact changes the substance.

2. **Set the operating boundaries.** Read the scope and channel rules in [references/method.md](references/method.md). Choose a sustainable cadence and one main distribution channel when starting from scratch. Separate drafting from publishing and avoid expanding a writing request into media production or business automation.

3. **Build an evidence-backed idea inventory.** Follow the idea selection rules in [references/method.md](references/method.md). Capture audience wording, firsthand observations, possible lessons, and missing evidence. Save reusable structures separately from other writers' wording or claims. Choose a problem with enough substance to support several independent angles.

4. **Draft the substantial hub.** Use the hub fields in [templates/output-template.md](templates/output-template.md). Explain the problem, its consequence, a useful method, a concrete example, and an appropriate next step. Complete the useful teaching before promotional language. If only an outline is requested, label it as an outline.

5. **Check the hub's depth.** Apply the substance gate in [checklists/review-checklist.md](checklists/review-checklist.md). Repair unsupported claims, missing examples, or sections that cannot stand alone before multiplying the piece. Use [examples/worked-examples.md](examples/worked-examples.md) to see how a vague premise becomes specific instruction.

6. **Map distinct spokes.** Consult the multiplication rules in [references/method.md](references/method.md). Extract three substantial lessons when possible, then vary the treatment: explanation, mistake, story, process, question, or resource invitation. Use the 1-3-5 model when helpful; reduce the count rather than filling a quota with duplicates.

7. **Write each body, then its opening.** Follow the writing and context rules in [references/method.md](references/method.md). Deliver a standalone payoff, then write a truthful opening that makes the reader, topic, and stakes clear. Finish with a recap or specific invitation suited to the asset's primary objective.

8. **Adapt to the channel.** Use the spoke fields in [templates/output-template.md](templates/output-template.md) and the contrasting examples in [examples/worked-examples.md](examples/worked-examples.md). Change context and presentation without changing the lesson. Apply the 5-12-3 heuristic only when building an evergreen library; keep timely writing clearly dated.

9. **Connect distribution.** Follow the destination rules in [references/method.md](references/method.md). Arrange a useful preview, hub release, and varied follow-ups. Link to the matching issue or article. Mark missing URLs as unresolved and distinguish proposed publication slots from scheduled or published assets.

10. **Define measurement and learning.** Complete the measurement fields in [templates/output-template.md](templates/output-template.md). Track components and outcomes separately, use comparable observation windows, and select one practical test. Treat impressions, reactions, comments, and clicks as diagnostic signals rather than causal proof.

11. **Review and hand over.** Run [checklists/review-checklist.md](checklists/review-checklist.md), repair failures, and report unresolved evidence or destinations. Use [references/sources.md](references/sources.md) for attribution checks. End the cycle by eliminating unnecessary work, simplifying the remaining process, and identifying stable tasks suitable for automation or delegation.

## Files in this skill

- [SKILL.md](SKILL.md): Entry point, scope, and the agent's main loop.
- [references/method.md](references/method.md): Detailed principles, decisions, warnings, and edge cases.
- [references/sources.md](references/sources.md): Fetched public sources and their contributions.
- [examples/worked-examples.md](examples/worked-examples.md): Two invented before-and-after applications with rule notes.
- [templates/output-template.md](templates/output-template.md): Fill-in content package with field guidance.
- [checklists/review-checklist.md](checklists/review-checklist.md): Pass/fail review and common repairs.