heath-gtm/Skill-Builder / builtgtm-content-structure
builtgtm-content-structure
VerifiedThe structural forcing function for any Sales Operator piece. Triage the type first (Build Log, Lens, Field, Signal, Playbook, Newsletter, Impact), then lock the shape: the hook is the person or the question, one spine, the story first (or an honestly labeled theory), scar before lesson, confidence stated, one thing left unresolved, cut the thrash. Trigger on "structure this", "how should this be laid out", "is this thrash", "tighten this piece", "what type is this", "structure my playbook / article / post".
Canonical reference
brand/voice.md in the Sales Operator repo (Built-GTM/Built-gtm) is the voice
canon and beats every other voice source, including this skill. WRITING.md in the
same repo holds the locked article spine. When they are reachable (a local checkout
at ~/Developer/Built-gtm, or the repo), read both first. If this skill and
voice.md disagree, voice.md wins, and this skill gets updated in the same session.
builtgtm-content-structure
The forcing function for any Sales Operator piece, before a word gets written or after a draft sprawls. The brand skill (builtgtm-brand) owns the voice. This skill owns the shape: what type of piece this is, what question the reader is asking, and the structure that answers it without thrash.
The posture sits under every shape: curious, not certain. A piece works something out in the open. It shows the approach, says how sure Heath is, and names what is still unresolved. It never hands down a verdict or claims the right way.
It also governs Company Impacts: the three biggest areas as STAR examples, built to reference and speak to, with the receipts file (the career evidence ledger) holding the detail.
The one rule above all others
One piece, one spine. A Sales Operator piece carries one question or idea, grounded in one real story when there is one, ending in one thing worth trying and one thing still open. More than one thesis and the reader leaves with none. If you wrote three ideas, you have three pieces. Split them.
STEP 0. Triage the piece type
Before structuring anything, name the type. The reader's question and the right shape both flow from it.
| Type | Reader's question | Goal | Ships to | Template |
|---|---|---|---|---|
| Build Log | "What did you build, and what happened?" | One build, the approach, what broke | Ghost + LinkedIn | Build Log |
| Lens | "How do you read this, and how sure are you?" | A position, with its confidence and limits | Ghost | Lens |
| Field | "What are other operators figuring out?" | Curated, credited, learn first | Ghost / LinkedIn | Field |
| Signal | "What might be coming?" | A short hypothesis and what would test it | Signal | |
| Playbook | "What could I build tomorrow, step by step?" | A build guide with failure points | Ghost | Playbook |
| Impact | "What did you change there, and can I believe it?" | The 3 biggest areas as STAR, built to reference and speak to | Lab / resume / interviews / AI context | Impact |
| Newsletter | "One story, one build, one open question this week?" | The weekly edition | Ghost | Newsletter |
If you are unsure, ask. If you cannot ask, default to Build Log. It is the spine of the brand.
Universal rules. Every piece.
- The hook is a person or a question. Open on the moment Heath was wrong, stuck, or proud of the wrong thing, or on the question he is working out. Never a statistic, never a verdict. No context-bombing, no runway.
- One spine. One idea, one story, one thing worth trying, one open question. Cut the rest.
- Story first, theory allowed. Reach for a real moment from the seat first, because the story is what lands. It is not a hard lock: a piece that is theory by nature (MCP or CLI, say) ships as a working theory, labeled as one, with what would test it. Never invent a story. Never dress a theory up as experience.
- The approach, not the receipt. Show what was actually done: the steps, the order, the fork, what broke. A number describes what happened, late and in floors format (90%+); it never makes the argument.
- Scar before lesson. The failure comes before the instruction. Self-implicating first.
- Confidence stated, something unresolved. Mark how sure Heath is with the nearest real experience. Name at least one thing he has not figured out.
- Humanize the numbers. 47% becomes "about 1 in 2." Weekly targets become daily rituals.
- Cut 30%. If you can remove a third and lose nothing, it is not done.
- No bow, no verdict close. No "in conclusion," no binary choice. End on the thing worth trying and the open question.
- Voice lock. Run builtgtm-brand, then builtgtm-voice-checker. No em or en dashes, no emoji as decoration, none of the press-release words.
- Ships to a channel, not a dashboard. The Sales Operator publishes on Ghost and LinkedIn.
Apply these before the type template.
The scroll test (the 30-second test)
Open the draft. Read only the first line and the subheads. Ask:
- Do I know the question or idea from the hook alone?
- Is there a person or a scar I can feel, or is it clearly labeled as theory?
- Can I see the approach, and how sure Heath is?
If any answer is no, the piece is buried or thrash. Fix that before writing the body.
Templates by type
Build Log
- The moment it went wrong. Specific: what it was costing, in human terms.
- What I tried first and why it failed. The scar.
- What I actually built, and how. The steps and the fork.
- What happened. At most one number, floors format, and what still breaks.
- The stack. Copy-pasteable. Named tools.
- What I have not solved yet.
- The one thing worth stealing. One line.
Present tense. If it has not run yet, it is a hypothesis and says so.
Lens
- The question Heath is working out, or the belief he had to revise.
- The old way: its true part first, then where it broke for him.
- The three reads. Where AI helps, where AI hurts, where AI optimizes. Take a position and say how sure.
- What he is trying instead, and how. Grounded in a story, or labeled as theory.
- Where it might not hold, and what would change his mind.
- The open question for the operator.
Field
- What another operator shipped or figured out. Named and credited.
- What Heath learned from it that he had not seen. Learn first.
- Their result, described in their terms, not claimed as his.
- What to try in your own seat, and where it might not transfer.
Signal
One observation. One hypothesis. How sure. What would prove it wrong. Four lines maximum.
Playbook (the strategic spine)
Same discipline as a strategic plan: the outcome up top, no thrash, defensible, honest about limits.
- The hero line. The outcome in one line. Example: "Cut SDR research from about four hours to under twenty minutes."
- The summary box, above the fold. What this builds, what it costs to not build it, who it is for, and where it might not fit. Not collapsible.
- The one-sentence spine. "This playbook is N steps. Each one has a trigger, a build, and a failure point." Keep N small. If N is over 7, it is two playbooks.
- Prerequisites. The stack and access you need before step 1. Honest. A working ugly thing beats a perfect plan.
- The steps. Each step: the trigger, the build (named tools), the failure point (the scar, what breaks here and how to know), and the check (how you know it worked). Numbered. Motion verbs.
- What happened when it ran. Floors, not trophies, and what it cost to get there. If it has not run end to end, say so.
- What is still unresolved.
- The one thing worth stealing, if they build nothing else.
- Optional: what I would do differently. The next-version note. No bow.
Hard rule: one outcome per playbook. Two outcomes is two playbooks.
Impact (a company or career record. Built to reference and speak to, not to read.)
Private career material, not public brand content. "Receipts" here means the career evidence file, which stays.
Three jobs:
- Give a model or a teammate instant context on a company Heath was at.
- Let him reference his three biggest impact areas and speak to each as a STAR example: Situation, Task, Action, Result.
- Show range as a sales leader, a revenue leader, and a GTM leader.
The narrative, the detail, and the source documents live in the receipts file. This file is the scannable index, not the essay.
Structure:
- Frontmatter, machine-readable. Company, website, company size, ARR range, the teams managed and their sizes, title, dates, leadership tags, and a one-line summary that names the three areas.
- The headline. One line. The headline result, with the swing.
- The impact areas, ordered as a story arc. Three to six. One area per major motion or function owned. Each is a STAR block:
- A title and a leader tag (Sales leader, Revenue leader, or GTM leader).
- Situation. What was broken. One line, with the number that shows it.
- Task. What he owned. One line.
- Action. What he did. One or two lines.
- Result. The numbers. Scannable.
- Receipts. A pointer to the detail in the receipts file.
- The numbers. One quick-reference table of the headline figures.
- Receipts pointer. The detail layer lives in the receipts file, not here.
Rules:
- The test for an area: can he speak to it cold? If not, it is detail for the receipts file. Avoid the resume trap of fifteen bullets.
- STAR, not prose. Each area is scannable in ten seconds.
- Every Result carries a number. Every area maps to a leader identity.
- Humanize the numbers: "nearly half our users were on free; I got it under one in six." Keep one precise anchor where it lands; push the exact ledger to receipts.
Newsletter (the weekly edition)
One story (the scar or the build, or a labeled theory). One build (what to try this week). One open question (what Heath is still working out). No fluff. No motivational content.
How to apply this skill
- Read voice.md if reachable. Triage the type (STEP 0). If unsure, ask.
- Run the scroll test on the hook and subheads before writing the body.
- Lay out the type template.
- Enforce the universal rules. Cut to one spine.
- Final pass: builtgtm-brand, then builtgtm-voice-checker.
- Output: the structured piece, or a flagged edit that names each violation and its fix.
Relationship to the other skills
- builtgtm-brand. The voice. Load first.
- This skill. The shape. Load before structuring or auditing a piece.
- builtgtm-post-writer, builtgtm-article-writer, builtgtm-newsletter-writer, builtgtm-playbook-writer, builtgtm-shortform-writer. The generators. They write inside this structure.
- builtgtm-voice-checker. The final gate.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |