# How Wyndo runs a newsletter from inside Claude Code

Wyndo writes The AI Maker and says roughly 80% of the newsletter operation now runs through Claude Code. The system has five layers: context files, skills, custom commands, MCP connections and CLI tools. Wyndo rarely writes prompts anymore. Instead, Wyndo speaks through WisprFlow and the system triggers the relevant skill.

| | |
|---|---|
| **Who** | Wyndo, writer of The AI Maker ([aimaker.substack.com](https://aimaker.substack.com)), who describes themselves as "not a technical person" |
| **Problem** | Acting as the middleman between chat AI and the places the work actually happens |
| **Stack** | Claude Code, CLAUDE.md and local files, skills, custom commands, WisprFlow (voice), connections to NotebookLM and Nano Banana, CLI tools for Tavily and Google Workspace |
| **Confidence** | Medium (first-person post, but the full breakdown sits behind a paywall) |
| **Last verified** | 2026-10-16 |

## The problem
Wyndo used ChatGPT and Claude chat "for over a year". The pattern was to type a prompt, get an answer, then copy and paste it into wherever the work lived. Wyndo's complaint: "I was always the middleman." That meant moving outputs by hand, re-explaining context in every new chat window and re-uploading files each time.

Wyndo adopted Claude Code around August 2025, three months after first hearing about it, after holding off because the name has "code" in it. The post describes the change as going from middleman to "having an AI agent that lives inside my work. It reads my files, understands my context, triggers workflows, and executes tasks."

## The blueprint (as described in the post)
The free part of the post lists five layers:

1. **Context management.** CLAUDE.md and local files replace the copy-paste loop.
2. **Skills.** Reusable workflows handle SEO, thumbnails, carousels, news digests, draft reviews and social content.
3. **Custom commands.** These trigger everything without writing prompts. Wyndo speaks through WisprFlow, and "the system triggers the relevant skill based on what I said."
4. **MCP connections.** These link Claude Code to external tools like NotebookLM and Nano Banana.
5. **CLI tools.** Wyndo calls these "the faster, token-efficient alternative to MCP" and uses them for services like Tavily and Google Workspace.

According to the post, the work covered runs "from researching topics to writing drafts to creating thumbnails to generating LinkedIn carousels." The paid section promises to show how all five layers fire together in a single workflow, what a typical day looks like, and where to start if you're coming from chat. That material is not in the source text.

## Stated results
- "Roughly 80%" of the newsletter operation runs through Claude Code (Wyndo's own estimate).
- Wyndo rarely writes prompts anymore.
- None stated for time saved, output volume, subscribers or revenue.

## Caveats
- The detailed breakdown is for paid subscribers of The AI Maker. This teardown covers only the free preview, so the specific skills, commands and wiring are not described here.
- The post grew out of a Substack Live with Michael Simmons on Blockbuster Blueprint. Wyndo calls it "not a polished demo or even a curated walkthrough."
- The WisprFlow link in the post includes a code (WYNDO2).
- X: [UNVERIFIED] not checked.

## Sources
- https://aimaker.substack.com/p/claude-code-newsletter-agentic-system (primary: Wyndo's first-person post on The AI Maker; free preview only)

---
*Want agents like these working your distribution? [See the Agent Stack Teardown](/agent-stack-teardown). Get new teardowns weekly: [subscribe](/subscribe) (double opt-in).*