Welsh Content Operating System
Build a repeatable written content system from one substantial idea into a newsletter and distinct social posts
Based on Justin Welsh's public method.
Not affiliated with or endorsed by Justin Welsh. Each step cites the public work it comes from: 11 sources.From newsletter teaser to a useful spoke
Extracts a standalone lesson from a substantial newsletter and gives it clear reader context.
Cash planning matters for restaurant owners. My latest newsletter explores profit, payment timing, and useful ways to manage your finances. Read it to learn more.
Restaurant owners: why did a profitable month leave you short of cash? Recorded sales, card deposits, payroll, and supplier bills happen on different schedules. Use a weekly cash calendar to see that timing gap. The full newsletter walks through a small example ledger.
Illustration from the skill's worked example, not a recorded run.
What it does
When your agent should reach for this skill.
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. 1
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.
The method
11 steps, restated from Justin Welsh's public work. Numbers link to the sources.
1Frame the cycle
Use the brief fields in 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.
2Set the operating boundaries
Read the scope and channel rules in 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.
3Build an evidence-backed idea inventory
Follow the idea selection rules in 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.
4Draft the substantial hub
Use the hub fields in 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.
5Check the hub's depth
Apply the substance gate in checklists/review-checklist.md. Repair unsupported claims, missing examples, or sections that cannot stand alone before multiplying the piece. Use examples/worked-examples.md to see how a vague premise becomes specific instruction.
6Map distinct spokes
Consult the multiplication rules in 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.
7Write each body, then its opening
Follow the writing and context rules in 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.
8Adapt to the channel
Use the spoke fields in templates/output-template.md and the contrasting examples in 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.
9Connect distribution
Follow the destination rules in 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.
10Define measurement and learning
Complete the measurement fields in 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.
11Review and hand over
Run checklists/review-checklist.md, repair failures, and report unresolved evidence or destinations. Use 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.
Worked example
How the method plays out on one case.
1: A bookkeeper explains restaurant cash timing
Brief and selection
Reader: Independent restaurant owners who see accounting profit but worry about making payroll.
Writer: A bookkeeper with permission to discuss a fictional ledger, without claiming it represents a client.
Objective: Teach a weekly cash check and invite readers to the full issue.
Primary channel: LinkedIn. Owned destination: A planned newsletter issue about cash timing.
Idea inventory:
| Candidate | Evidence available | Decision | | --- | --- | --- | | Become financially successful | No defined problem or method | Reject as too broad. | | Why profit does not mean cash is available for payroll | Illustrative dated receipts and payments | Select: recognizable problem and three usable lessons. | | How much cash every restaurant should keep | No context-specific basis | Hold for research; avoid a universal reserve claim. |
Weak first draft
Hub: Restaurant finance is complicated. Profit is important, but cash flow is even more important. Track your KPIs, optimize your working capital, and plan ahead. Subscribe for more tips.
Social post: This cash-flow secret will transform your business. Every owner needs better KPIs. Agree? Follow me, subscribe, and book a call at my homepage.
The draft gives no usable process, relies on unexplained terms, promises an unsupported transformation, and asks for several unrelated actions. There is too little substance to multiply.
Improved hub draft
Title: A profitable month can still leave a restaurant short on payroll day
Monthly profit and Friday's bank balance answer different questions. Profit describes income and costs for a period. The cash available for payroll depends on when money actually arrives and leaves.
Consider this invented week: Your restaurant starts Monday with £4,000 available. A £3,000 supplier bill is due Tuesday, £2,000 in card receipts arrives Thursday, and £4,000 payroll leaves Friday. With no other movements, Friday's balance is £1,000 short. The expected receipts do not cover the dated payments.
Before the week begins:
- Write down the cash available now.
- Put expected receipts on their likely arrival dates.
- Put payroll, supplier bills, and other payments on their due dates.
- Calculate the running balance after each movement.
- Investigate any shortfall early, including whether receipt dates are dependable and which payment terms can be discussed.
This calendar is a planning aid, not a guarantee. Unexpected costs and delayed receipts still matter. Start with the dates you know, then update the calendar as the week changes.
Try the check before your next payroll run. The aim is to see a timing problem while there is still time to address it.
Improved spokes
A. Explanation, LinkedIn, standalone education
Restaurant owners: A profitable month does not tell you whether Friday's payroll is covered.
Check when receipts reach the bank and when bills leave it. Put both on a dated calendar and calculate the balance after each movement. A monthly total can hide the day that creates a shortfall.
B. Process, LinkedIn, conversation
Before payroll week, give your restaurant's cash forecast five rows: starting cash, expected deposits, supplier payments, payroll, and other bills.
Add dates, then calculate the balance after each payment. That turns a vague worry into a specific day to investigate.
Which arrival or payment date is hardest for you to predict?
C. Resource invitation, LinkedIn, article visit
A restaurant can expect enough receipts for the month and still run short on Friday.
In my cash-timing issue, an invented week starts with £4,000 and ends £1,000 short after supplier payments, deposits, and payroll. The useful part is seeing the shortfall before Friday.
Read the dated walkthrough here: [cash-timing issue URL pending].
Distribution and measurement
Use B as a pre-release insight, publish the hub, then A and C on separate planned slots. C stays in draft until its exact issue URL exists. Record impressions and useful questions for A and B, and article clicks for C. Collect subscriptions only if the destination provides that metric. No results are claimed.
Rules that changed the result
- A recognizable cash problem replaces a broad aspiration, applying the context test. 5
- A worked ledger gives the hub enough teaching to support independent spokes. 23
- Bodies contain the promised value before openings are polished. 4
- The conversation question asks about actual experience; the resource post has a different primary job. 6
- The link continues the same topic rather than sending readers to a homepage. 9
1 more worked example in examples/worked-examples.md.
What's in the package
7 files, pinned at d5668a9. Open any file on GitHub.
SKILL.mdEntry point the agent loads: when to use the skill and the procedure.6,114 bytesLICENSEApache-2.0 license.10,756 bytesreferences/method.mdThe method in full, step by step, with citations.14,083 bytesreferences/sources.mdEvery public source the method is built from.3,635 bytesexamples/worked-examples.mdWorked examples showing the method applied end to end.9,341 bytestemplates/output-template.mdThe output format the agent fills in.6,829 byteschecklists/review-checklist.mdChecks the agent runs before handing back the result.5,217 bytes
Sources
The public work this skill is built from. Read Justin Welsh's originals.
- Justin Welsh, The Content Operating System, public course overview and FAQlearn.justinwelsh.me
- Justin Welsh, How to Build Digital Leverage (aka work smarter), June 10, 2023justinwelsh.me
- Justin Welsh, How 1 piece of content becomes 16: The 1-3-5 Method, July 27, 2024justinwelsh.me
- Justin Welsh, My Writing Process for 162.597M+ Impressions On LinkedIn., October 8, 2022justinwelsh.me
- Justin Welsh, The #1 Reason Content Fails, June 7, 2023justinwelsh.me
- Justin Welsh, Reverse engineering LinkedIn success, October 12, 2024justinwelsh.me
- Justin Welsh, How to Use 'Engagement Loops' to Grow Your Brand & Business, January 13, 2024justinwelsh.me
- Justin Welsh, Create Better Content, Faster, with ChatGPT., January 21, 2023justinwelsh.me
- Justin Welsh, A Complete Guide to Passive Sellingjustinwelsh.me
- Justin Welsh, Leverage is the solopreneur cheat code., September 20, 2025justinwelsh.me
- Justin Welsh, 4 Questions for Better Weekly Productivity, July 2, 2022justinwelsh.me
The skill file also covers: Files in this skill. Read the full SKILL.md.
Edge wrote this skill from Justin Welsh's public writing and talks listed above. It is not affiliated with or endorsed by Justin Welsh. If something misrepresents the method, write to [email protected] and we will correct or remove it.