LinkedIn Hand Raiser Post — Output Skill

What this produces: A ready-to-publish LinkedIn hand raiser post with CTA, optimized for authority, distribution, and conversion.

Output format: Text in a code block or saved as li-{{topic-slug}}-hand-raiser.md

Build Process

Step 0: Read Companion Files

1. voice.md — Voice wins over all other rules
2. audience.md — Who the reader is, what converts them
3. soul.md — Why this brand exists
4. offer.md — What Advisory OS sells

Step 1: Run the Intake

Walk through all eight decisions from 01-li-hand-raiser-context.md:

1. CTA Type — Lead Shark comment trigger or workshop registration
2. Asset / Event — What it is, who it's for, what it does, and the status angle
3. Angle — Propose 2–3 with rationale
4. Hook — Propose 2–3 opening lines
5. Arc + CTA Transition — Section flow including where the shift happens
6. Trigger Word — Propose 2–3 with status analysis for each
7. Signature Block — Propose 2–3 positioning statements
8. Format — Text post or carousel. Recommend based on material and CTA type.

For trigger word proposals, always include the status analysis:

• "TRIAGE" — commenter signals: "I score prospects with systems, not gut feel"
• "DECODER" — commenter signals: "I read signals others miss"
• Recommend: TRIAGE, because the post demonstrates a scoring system and the word itself implies analytical rigor

After all decisions are locked, produce the Post Lock:

POST LOCK: [Working Title]
CTA type: [Lead Shark / Workshop registration]
Asset: [One sentence]
Angle: [Angle name]
Status angle: [What taking the action signals about the reader]
Hook: [Opening line]
Arc: [Section flow including CTA transition]
CTA: [Exact CTA text]
Trigger word: [KEYWORD]
Signature: [Positioning statement]
Format: [Text-only / Carousel]

Step 2: Write the First Pass

Before writing a single line:

1. Select the golden example closest to your angle (03-golden-examples.md)
2. Study its structural spine: How does it open? Where does the story or evidence live? When does the insight land? Is the value body scene-led or thesis-led?
3. Write from that structure. The Post Lock tells you WHAT to write. The golden example tells you HOW.

The value body of a hand raiser IS thought leadership content. The same rule applies: if the body announces the insight in the opening and then illustrates it, the structure is backwards. Lead with scene, evidence, or recognition — let the insight emerge, then transition to the CTA.

Writing sequence:

1. Write the hook exactly as locked
2. Build the value body (70–80% of post) — match the golden example's delivery pattern, not a thesis-first lecture
3. Write the CTA transition — spend time here, it's the hardest line
4. Write the CTA (trigger or registration)
5. Write the signature block
6. Check total length: 1,500–2,600 characters
7. Check value-to-CTA ratio: 70/30 to 80/20
8. Read aloud — does the transition feel earned? Does the trigger word feel natural to comment?

The status test during writing: At every structural beat, ask: "What is the reader signaling about themselves by staying with this post?" The hook self-selects. The body elevates. The CTA converts. The trigger word broadcasts.

Step 3: Self-Check Before Delivering

Structural comparison (check FIRST — before anything else):

• [ ] Compare against the selected golden example. Is the value body scene-led or thesis-led?
• [ ] Does the insight emerge through narrative/evidence, or is it announced and then illustrated?
• [ ] If thesis-led: rewrite scene-first before running any other checks. QC cannot fix a structural problem.

Authority checks:

• [ ] Value body delivers genuine insight
• [ ] Evidence is specific
• [ ] Closer is quotable
• [ ] Voice matches voice.md

Distribution checks:

• [ ] Length is 1,500–2,600 characters
• [ ] Body is provocative enough to generate substantive comments alongside triggers
• [ ] No external links (or hybrid trigger approach used)
• [ ] Post stays in Advisory OS topic lane

Status checks:

• [ ] Can articulate in one sentence what commenting signals about the reader
• [ ] Trigger word works as an identity badge
• [ ] Audience segments (if used) are identities the reader wants to claim publicly
• [ ] Signature reinforces the status transfer for thread viewers
• [ ] The CTA doesn't require admitting weakness publicly

Conversion checks:

• [ ] CTA transition is 1–2 lines, natural
• [ ] One action, clearly stated
• [ ] Asset value is obvious in one sentence
• [ ] Trigger word is easy to type and remember

Step 4: Flag Known Weaknesses

• "The CTA transition feels abrupt. May need a bridge sentence."
• "The trigger word SCORING is functional but not as status-charged as TRIAGE."
• "The body doesn't create enough tension for the reader to feel compelled to act."
• "The signature is generic — needs to connect to this specific post's topic."
• "This might generate trigger comments but probably not substantive discussion — the body needs a more provocative claim."

Step 5: Revision + QC

Pass 1 — Copy QC (copy-qc.md): All 11 patterns. Fix P1 and P2.

QC posture: fail-first. When a pattern is detected, the default is FAIL. To keep a flagged line, cite a specific golden example that uses the same structure and was annotated as acceptable in its Copy QC Notes. "I think it works here" is not sufficient — show the precedent or rewrite. If no golden example does the same thing, it fails.

Pass 2 — Sentence Editor (linkedin-sentence-editor.md): All 8 rules. Present changelog.

CTA Templates

Lead Shark Comment Trigger

[CTA transition — 1 line]
[Asset description — 1 sentence]

Comment [KEYWORD] and I'll send it.

I'm Kathryn Brown. I [positioning] for [audience] so [stakes].

Workshop Registration (Hybrid — Recommended)

[CTA transition — 1-2 lines]
[Event description — 1-2 sentences]

[Date] · [Time] · [Format]
[Who it's for — 1-3 segments]

Comment [KEYWORD] and I'll send the registration link.

I'm Kathryn Brown. I [positioning] for [audience] so [stakes].

Workshop Registration (Direct Link — Accept 60% Penalty)

[CTA transition — 1-2 lines]
[Event description — 1-2 sentences]

[Date] · [Time] · [Format]
[Who it's for — 1-3 segments]

Register: [link]

I'm Kathryn Brown. I [positioning] for [audience] so [stakes].

Angle-Specific Build Notes

Transformation Proof

• Lead with the result. Compress the timeline.
• The status play: "This transformation is achievable, and I'm the kind of person who pursues it."
• CTA bridges to the same result for the reader.

Problem-Agitation

• Agitate with observed costs — hours, dollars, client losses. Not hypothetical fear.
• The status play: "I'm honest about what's broken and I fix things instead of ignoring them."
• CTA is the relief. The transition should feel like opening a pressure valve.

Behind the Curtain

• Show enough to be credible. Architecture details build trust.
• The status play: "I'm sophisticated enough to appreciate how this works at a systems level."
• CTA gives access to what you showed a glimpse of.

Scarcity / Timing

• Every constraint must be real. No false scarcity.
• The status play: "I act on opportunity. I move fast."
• Front-load value. The deadline creates urgency only after the reader wants the thing.

Audience Segmentation

• Three segments max. Each specific enough for self-selection.
• The status play: self-selecting into a segment IS the identity act. "I'm the CEO transforming operations" or "I'm the operator becoming the most valuable AI person."
• Place segmentation near the CTA — it's the final qualifier.

Results-First

• Lead number must be specific and surprising.
• The status play: "I'm drawn to concrete results, not theory. I'm pragmatic."
• Context backfill should be compressed. CTA connects: "Here's the system behind this number."

Common First-Pass Mistakes