Home
Resources
Agent Skills
Writing voices
Theo — the dense tactical handbook chapter

Theo — the dense tactical handbook chapter

A blog-writing style skill that makes an AI agent write in the dense tactical handbook voice of Julian Shapiro: every sentence carries a usable idea, the core concept is named in bold and defined in one line, and the chapter moves from a principle to a framework to numbered imperative steps, with real before-and-after rewrites and a section on mistakes and exceptions. 1,500 to 4,000 words, organised to scan in two minutes. It works on any business topic. The skill gives a fingerprint table, a seven-step build, sentence rules, truth rules for examples and numbers, a worked opening and a revision pass. It reproduces the moves, never the writer's sentences, frameworks or formulas.

In the voice of Julian Shapiro

Updated 5 October 2026 · By Sadeq

When to use it

Write a blog post in Theo's voice: the dense tactical handbook chapter. Every sentence carries a usable idea; concepts are named and defined in one line; the post moves from a principle to a framework to numbered steps, with before-and-after rewrites and worked examples from real products. Headings that say what the section teaches, short paragraphs, bold for the key term, a formula where one helps. Use when someone asks for a post "in Theo's style", a definitive guide, a playbook, a "how to do X well" chapter, or reference content people bookmark and return to. Works for any business topic. Do not use it for opinion pieces, news or stories — the form has no room for them — and do not use it when the writer has no real method to teach.

Complete file

SKILL.md

---
name: theo
description: >
  Write a blog post in Theo's voice: the dense tactical handbook chapter.
  Every sentence carries a usable idea; concepts are named and defined in
  one line; the post moves from a principle to a framework to numbered
  steps, with before-and-after rewrites and worked examples from real
  products. Headings that say what the section teaches, short paragraphs,
  bold for the key term, a formula where one helps. Use when someone asks
  for a post "in Theo's style", a definitive guide, a playbook, a
  "how to do X well" chapter, or reference content people bookmark and
  return to. Works for any business topic. Do not use it for opinion
  pieces, news or stories — the form has no room for them — and do not use
  it when the writer has no real method to teach.
license: MIT
metadata:
  author: daena-digital
  version: "1.0"
  collection: blog-style-voices
---

# Theo — the dense tactical handbook chapter

Theo writes the chapter you wish someone had handed you before you
started. It is dense on purpose: no warm-up, no filler, every paragraph
either defines something, shows something or tells the reader what to
do. It reads fast because it is organised, not because it is short.

Studied from Julian Shapiro's handbooks and essays at julian.com. This
skill reproduces his *moves*, never his sentences, frameworks, formulas
or section names.

## When to pick Theo over another voice

- The reader wants to learn a method and use it this week.
- The topic has steps, criteria or trade-offs that can be laid out.
- The post should rank for a "how to" query and still be worth
  bookmarking.

Pick Poppy for a friendlier, story-led how-to with fewer, looser points.
Pick Silas when the topic is why a market works the way it does, not how
to do a task.

## The fingerprint

| Trait | Theo does | Theo never does |
|---|---|---|
| Length | 1,500–4,000 words, organised so it scans in two minutes | Padding to hit a length, or a 600-word "guide" |
| Opening | A one-line question or problem, then why it matters in two or three sentences, then what the chapter covers | Anecdote, history, "In this article we will…" |
| Structure | Principle → named framework → numbered steps → examples → common mistakes | One long run of tips with no order |
| Headings | H2/H3 that state what the section teaches: *"Write the header last"* | Labels like "Overview", "Tips", "Conclusion" |
| Definitions | A named concept in **bold**, defined in one sentence, then used consistently | Undefined jargon, or a term that changes meaning |
| Frameworks | One or two original named models; a simple formula where it clarifies (*Conversion = Desire − Friction*) | Five frameworks, or borrowed ones passed off as new |
| Examples | Real, named products and before/after rewrites of actual copy or decisions | Invented "Company X" presented as real |
| Sentences | Mostly 8–18 words, each carrying one idea. Occasional one-line paragraph for emphasis | Long chains, rhetorical flourish |
| Paragraphs | 1–4 sentences | Walls of text |
| Tone | Direct, imperative, friendly. Occasional light aside in parentheses | Lecturing, hype, jokes that cost space |
| Caveats | Named explicitly: "This doesn't apply if…" | Ignoring edge cases, or hedging every line |
| Ending | A short recap of the steps, or a single exercise the reader can do now, then a pointer to the next chapter | An inspirational close or a sales pitch |

## How to build the post

1. **State the job.** One sentence: what the reader will be able to do
   after reading. If it isn't a skill they can practise, this is not a
   Theo post.

2. **Name the core principle.** The one idea everything else follows
   from. Give it a short, plain name in bold and define it in one
   sentence. Make the name original.

3. **Turn it into a framework.** A short ordered model: three to seven
   parts, or a formula with two or three terms. Each part gets a heading.

4. **Write the steps.** Under each part, numbered steps in imperative
   voice: *"List every objection a buyer raised in the last month."* Each
   step is one action.

5. **Show before and after.** For each major step, one real example: a
   weak version and a strong version side by side, with one line on what
   changed. Use the user's own material where possible; otherwise use
   real, named, checkable public examples.

6. **List the mistakes and exceptions.** A short section: when the method
   fails, and the two or three most common ways people misuse it.

7. **Close with a recap or exercise.** A numbered recap of the steps, or
   one task the reader can do in the next hour. Then stop.

## Sentence-level rules

- **One idea per sentence.** If a sentence has "and" joining two ideas,
  split it.
- **Imperatives for steps, declaratives for principles.** "Write the
  header last." versus "Headers do the most work on a page."
- **Cut throat-clearing.** Delete any sentence that only announces what
  the next sentence will say.
- **Specific over general.** "Cut the hero copy to 12 words" beats "keep
  it concise".
- **Bold only the term being defined** or the one phrase the reader must
  remember from that section.
- **Explain jargon once, in plain words**, the first time it appears.
- **Keep asides rare.** One light parenthetical per section is plenty.

## What Theo never licenses

Dense is not the same as authoritative-sounding.

- **No invented examples presented as real.** A before/after must come
  from the user or from a public, named, checkable source. A clearly
  labelled hypothetical is allowed.
- **No invented numbers.** Benchmarks, conversion lifts and percentages
  need a source the reader could check. If there is none, give the rule
  without the number.
- **No borrowed frameworks, formulas or section names** from the writer
  this voice was studied from. Credit any well-known public model by name
  (for example, a named prioritisation score) rather than renaming it.
- **No false completeness.** If the method has limits, the mistakes
  section says so.

## A short illustration

The opening and first section of a Theo chapter for a hypothetical
dental clinic's blog. The clinic and its reminder texts are invented to
show the shape; in a real post they come from the user:

> **How to write appointment reminders people act on**
>
> Most reminder texts are read and ignored. This chapter shows how to
> write one that gets a reply, in four steps you can apply today.
>
> ## The principle: one message, one decision
>
> A reminder works when it asks the patient to make **one decision** —
> confirm, move, or cancel — and makes that decision take one tap.
>
> Everything below follows from that.
>
> ## Step 1: Lead with the time, not the clinic
>
> Patients scan for *when*. Put the day and time first.
>
> **Before:** "Hello from Northside Dental! This is a reminder of your
> upcoming appointment on Tuesday at 3:00pm."
>
> **After:** "Tue 3:00pm — cleaning with Dr. Lee. Reply 1 to confirm,
> 2 to move it."
>
> What changed: the time moved to the front, the greeting went, and the
> decision is now one keystroke.

Note what it does: one-line promise, a bold named principle defined in a
sentence, a heading that teaches, an imperative step, and a real
before/after with a line on what changed.

## Revision pass

1. Can the reader name the core principle and the steps after one skim?
2. Does every heading state what that section teaches?
3. Is each term defined once, in bold, and used the same way after?
4. Does every major step have a before/after or worked example — real or
   clearly labelled hypothetical?
5. Is every number sourced?
6. Delete any sentence that only announces the next one.
7. Is there a mistakes/exceptions section?
8. Does it end on a recap or one exercise, with no pitch?

Knowledge base

What we read to learn Julian Shapiro’s voice

Landing Page Copywriting (Startup Handbook)Hierarchical headings, a simple formula, numbered processes, before/after copy
Retaining Users (Startup Handbook)Opens on a question; one central named concept; many real product examples
Market Pull (Startup Handbook)Term defined in one line, categories listed, exceptions named explicitly
Growth Channels (Startup Handbook)Options compared by business type; worked numerical examples
Writing Well: IntroStates what the reader will learn and why, then the chapter map
Writing Well: RewritingRules as imperatives with before/after sentence rewrites
Start a Startup: IntroHow a handbook is laid out as chapters with core and optional parts