Workflows that change your week.

LinkedIn + Notion + Claude.

The most-copied content workflow on the internet right now. Notion is the brain, Claude is the writer, LinkedIn is the surface. The whole stack is three connectors and a saved chat.

The skill, in one prompt

CopyRead my Notion "Content Calendar" page. Find the next planned post.
Then read my last 3 published posts (in "Published" sub-page) to study the voice.

Draft three variations of the post:
- Hook A: a contrarian claim
- Hook B: a personal story
- Hook C: a number that surprises

Each variation: 250-400 words, one hook + one story + one ask.
Use my voice from the samples. No "leverage" or "unlock".

Format the output as three numbered drafts I can choose between.
Do NOT publish. I will review and post manually.

Source: Síntesi Studio — Claude + Notion content automation.

The monthly batch.

The leverage move: plan a month of content in one Sunday afternoon. Then your weekly writing sessions become pure execution.

One Notion page per month with the calendar:

Copy# May 2026 · Content Calendar

| Date    | Channel  | Topic                                   | Hook angle      | Status |
|---------|----------|-----------------------------------------|-----------------|--------|
| Mon 5/4 | LinkedIn | What a personal AI second brain can do       | Contrarian      | Draft  |
| Wed 5/6 | LinkedIn | The 60-token trick (Claude Skills)      | Number          | Idea   |
| Fri 5/8 | LinkedIn | Three things I shipped this week        | Personal        | Idea   |
| Wed 5/13| Email    | The agent harness, in plain words       | Education       | Idea   |
| ...     | ...      | ...                                     | ...             | ...    |

The Sunday batch: ask Claude to read the calendar, propose topics for “Idea” rows that fit themes you’ve been writing, and queue first drafts of each. By Sunday night you have a month of starting points. Each weekly session is 30 minutes of edit, not 90 minutes of staring.

Source: Alex’s 11 Claude workflows for freelance ops.

Voice → publication.

You had a thought on a walk. By the time you’re at your desk, a LinkedIn draft is sitting in your inbox.

The pipeline

1. Capture. 60-second voice memo into the Claude mobile app (or your second-brain bot).
2. Transcribe. Whisper (local or hosted).
3. Extract. Claude pulls the one claim worth defending out of the rambling.
4. File the idea. A new row in Notion’s “Ideas” database, with tags + the original transcript.
5. Draft. Claude composes a LinkedIn-ready 350-word draft in your voice.
6. Send to inbox. The draft lands in your Drafts folder. You polish on the train.

End-to-end latency: ~2 minutes from the moment you stop talking. The cost of the thought going from your head to your audience drops by an order of magnitude.

The eleven-workflow freelance ops stack.

From the most-shared Claude workflow post of 2026: how one freelancer runs an entire client-facing business on eleven Claude workflows.

Each workflow is one Cowork saved chat with explicit tool wiring (Notion, Calendar, Gmail, Linear). The author claims the eleven combined save ~9 hours a week. Adopt the three that match your work; skip the others — and where a row links a Cowork recipe above, that recipe is a ready-made, copy-able version you can run today.

Source: growthwithalex.substack.com.

The 4-level investing setup.

From The AI Corner: how to layer Claude across research, projects, skills, and Cowork for investing. Four levels, increasing leverage.

Start at Level 1, not Level 4. Move up only when the level below has become a real habit. The mistake everyone makes: try to wire Cowork to your brokerage on day one and burn out. Spend three weeks at Level 1, three at Level 2, then layer up.

Portfolio analysis with Claude Code.

From Matt Stockton’s portfolio analysis skill: the surprising fact that Claude Code, not the chat app, is the right tool for messy financial data.

Why Code over chat

• Brokerage exports are CSVs in mixed formats. Code can parse them programmatically.
• You have multiple accounts — brokerage, 401k, 529, bank. Code can read all of them in one session.
• You want reproducibility. The Code session is git-tracked.

The workflow

1. Drop holdings CSVs (one per account) in ~/Investments/raw/.
2. Drop a static-assets note with bank balances, employer plans, debts.
3. Run claude in that directory.
4. Ask: “Combine these into a portfolio view. Compute allocation vs my target (60/30/10). Identify the 3 biggest drifts. Suggest two rebalancing trades.”
5. Claude writes a markdown report; you review; you trade.

Total time: 20 minutes a month. Quality higher than most teams’ advisor outputs because the model can question your assumptions exhaustively before concluding.

The twelve-prompt stock analyst.

From The AI Corner: a 12-prompt pipeline that produces an investment-committee-grade analysis on any single ticker.

The twelve, in order:

1. The thesis — “Write the 3-sentence thesis for owning this company.”
2. The history — revenue, margin, FCF trends over 5 years.
3. The unit economics — what makes one dollar of revenue?
4. The moat — quoted, not asserted. Cite the 10-K.
5. The customer — who buys, why, what would make them switch.
6. The competitive set — the three real comparables with one-line takes.
7. The macro — the two macro variables that matter most for this company.
8. The risks — specific, quantified, not generic.
9. The valuation — three frames (DCF, comps, scenario).
10. The pre-mortem — assume the stock is down 50% in 3 years. Why?
11. The trigger — what specific signal would change your mind?
12. The position — size, time horizon, exit rule.

Each prompt is a saved Cowork skill or a slash command in your investing repo. Run all twelve on one ticker in an evening. The output is a markdown file that beats most sell-side reports. For a ready-made starting point that bundles the thesis / risks / valuation prompts into one pass, copy Cowork R01 · The investment memo; for the research-gathering step (prompts 2–7), Cowork R02 · The topic brief.

Weekly automated briefing.

The scheduled version: every Friday at 5pm, Claude reads the week’s news on your watchlist, your Gmail, your scratchpad, and emails you the “here’s what changed and what to do” brief.

Copy# weekly-investing-briefing.md (skill spec)
Every Friday at 17:00 local:

1. Read my watchlist (Notion page "Investments / Watchlist").
2. For each ticker, search news from the last 7 days, top 5 results.
3. Read my Gmail for any "earnings", "analyst", "downgrade" mentions.
4. Cross-reference with my scratchpad notes since last Friday.

Produce a one-screen briefing:

WATCHLIST CHANGES
[ticker]: one-line summary of what changed.

EARNINGS NEXT WEEK
[ticker]: date, consensus EPS, key thing to watch.

DRIFT VS THESIS
Any ticker where the news suggests my thesis needs updating.

ACTION
Zero items, one item, or two items max. Specific.

Email to me. Do not place trades. Do not edit holdings.

Source for this pattern: Growwstacks weekly stock/ETF analysis template.

The daily Cowork briefing.

Adapted from jaindl’s daily-briefing essay: a Cowork chat saved as a starred prompt that runs every morning before you sit down with coffee.

Already covered in depth in the NanoClaw practice (Unit 08). The cross-reference: the same skill can run in Cowork (no Pi required) for users who don’t want hardware. Reach for Cowork if you don’t want a Pi; reach for the Pi when uptime matters.

The reading-list filter.

You have 80 unread articles in Pocket / Instapaper. Six are worth reading. Which six?

CopyRead my Pocket queue (or paste the list of URLs).

For each item:
- Estimate read time
- Tag with one of: PRO (career), HOME (personal), BROAD (curiosity), SKIP

Then for items NOT tagged SKIP, score 0-10 on:
- Specific to my work this quarter (Q3: agents, AI practices, AI eng)
- Novel vs things I've already read this month
- Timeliness (decays after 30 days)

Output the top 6, ranked, with one-sentence pitches.
The rest: pile into "skip" and forget about them.

The dinner-conversation file.

A small, surprising one. You’re having dinner with someone interesting. Five minutes before they arrive, Claude reminds you what the two of you talked about last time, what they care about, and one fresh thing to bring up.

CopyI'm about to have dinner with [person name].

Read my wiki entry for them (people/[slug].md if it exists, otherwise everything in my notes that mentions them).

Tell me:
- Two things we agreed on last time
- One thing they were worried about that I should ask about
- One specific story from my week that connects to something they care about
- One thing I should NOT bring up (anything they were tired of discussing)

Plain words. 200 words max. No "leverage".

The first time you run it, the answer is generic because the wiki is thin. The fifth time you run it (with the wiki having grown from the conversations between), the answer is uncanny. This is what compounding looks like in personal life.

Wire your own.

A dozen workflows shown across this practice. None of them is right for you exactly. The point of the practice is the shape, not the workflows themselves.

The pattern, once and for all

1. Pick one repeated task from your week. Not your year — your week.
2. Identify its inputs (apps, files, notes).
3. Identify the output (one-page memo, draft email, ranked list).
4. Write the prompt that goes from inputs to output. Hand it to Claude once, by hand.
5. If the output is good, save the prompt. Connect the inputs to Cowork. Schedule it.
6. If the output is not good, look at where it broke. Fix the prompt or supply better inputs. Loop.