name: content-from-delivery description: > Turn a finished client engagement into 3 LinkedIn posts in under 3 minutes. Describe what you delivered, what changed, and what the client's situation was before you started. The skill extracts the story at three levels and produces 3 posts from different angles, ready to publish. Use when you've finished a piece of client work and want to turn it into content before the details fade. Works with bullet points, rough notes, or polished summaries. Triggers: "content from delivery", "turn this engagement into posts", "write posts from client work", "extract content from this project", or any request to turn completed work into content. metadata: author: Kathryn Brown, Advisory OS version: "1.2.0" updated: "2026-04-16"
Content-from-Delivery
Turn the work you already did into the content you never get around to writing. One engagement in, 3 posts out.
Core Principle
Read before writing. Absorb the full engagement description before producing anything. The quality of the posts depends on pulling out three distinct layers of the story — the flat version, the version with numbers, and the version that starts where the reader starts.
What This Skill Does
You describe a completed client engagement — what the situation was, what you delivered, what changed. Bullet points, rough notes, a paragraph — the skill extracts structure from whatever you paste. It produces:
Job 1: Three-Layer Extraction — Pulls the engagement apart at three levels so the posts have depth, not just surface.
Job 2: Three LinkedIn Posts — Each from a different angle, anonymized, ready to copy-paste and publish. Each post leads with the prospect's situation, not your expertise.
Input
Describe a completed engagement. Include whatever you have:
- What the client's situation was before you started
- What you delivered
- What changed as a result
- Any specific numbers (fees, hours, percentages, timelines)
Rough notes are fine. The more specific the numbers, the stronger the posts.
If you also have output from the Scope-to-SOW skill, paste that too — the SOW sections map directly to the extraction layers.
Three-Layer Extraction
Before writing any posts, extract the engagement at three levels:
Surface
The version the practice owner would write themselves. Accurate but flat. No numbers, no emotion, no prospect hook. This is the version that says "helped a client streamline their operations."
Format: 2-3 sentences.
Real
What emerges with specifics. Numbers, before/after, actions taken, timeline. The version that says "founder was working 60-hour weeks. Within 90 days, the team was handling 80% of decisions independently. Revenue grew 30% the following quarter."
Format: Full paragraph with at least one specific number.
If the input doesn't contain enough detail: Flag what's missing. "Missing: timeline for results" or "Missing: quantified outcome." Partial extraction is better than fabricated numbers.
Prospect
The version that starts where the reader starts. Mirrors their current situation. The version that opens with what the client was living with before you showed up — so a practice owner reading it thinks "that sounds like my firm."
Format: 2-3 sentences. Starts with the client's situation, not the provider's action.
Three LinkedIn Posts
Three different posts from the same engagement. Each uses a different angle. All posts follow these rules:
Structure rules:
- One sentence per line — every sentence gets its own line
- Opens with a specific scene or situation — not a thesis, lesson, question, or instruction to the reader. The reader should be in the scene, not told to imagine one.
- Includes at least one outcome number from the Real layer — dollars, time saved, timeline compression, or measurable before/after. Scene details (duration of a call, size of a team) don't count.
- No three consecutive sentences with the same opening word or parallel structure. Vary sentence subjects and rhythm.
- Anonymized — no client name, no identifying details. Change industry if needed to protect identity while keeping the pattern
- Generalize delivery tools and methods. The post is about the outcome and the capability, not the tooling. "A repeatable system" not "a markdown file plus a set of agents."
- Aspirational — the reader finishes thinking "I want that" not "I'm guilty of that"
- Ends with what was built or gained, not what was broken
- 150-250 words each
- No hashtags, no emoji
The three angles:
Post 1: The Pattern
Opens with a scene. A specific person in a specific situation. The systemic pattern emerges from the story — the reader recognizes it in their own practice without being told to. Never include a sentence that names, labels, or announces the pattern. Includes at least one outcome number from the Real layer — not a scene detail.
Post 2: The Before/After
Opens where the client started. Walks through the transformation. The "after" is aspirational — the reader sees where they want to be.
Post 3: The Capability
Opens with what the practice owner built and now owns. Show the capability in use, not as an inventory of what was installed. Focuses on the permanent capability created — the system, the asset, the repeatable process. The reader finishes thinking "I want to build that."
Quality Check (Internal — never shown to the user)
This section is an internal gate. Run it silently before presenting. Use it to correct the posts. Do not include the Quality Check in the output. The user should never see a Pass/Fail table or a "weakest post rewrite" note — they should see three finished posts that have already been through the gate.
Before presenting, check four things and rank the posts internally:
| Check | Question |
|---|---|
| Scene-led | Does each post open with a person in a situation — not a thesis, lesson, or instruction to the reader? |
| Specificity | Does each post contain at least one outcome number from the Real layer — dollars, time saved, timeline compression, or measurable before/after? Scene details (call duration, team size) don't count. |
| Aspiration | Would the reader want their network to see them engaging with this? |
| Anonymization | Could two or more details across any post identify the client when read together? |
Two enforcement rules:
- Failed checks: If any post fails a check, fix the post and re-check it before presenting. The output contains only the corrected post — no flag, no note about what was fixed.
- Weakest post: Rank the three posts strongest to weakest internally. Rewrite the weakest before presenting. Verify the rewrite internally: quote the original line(s) and the replacement line(s) to yourself, then confirm the replacement text is actually in the final post. If it isn't, the rewrite didn't happen — redo it.
If all three posts pass all checks with no meaningful differentiation between them, re-examine — the QC is being too generous.
What the user sees: The Engagement Snapshot, the Three-Layer Extraction, and the three finished posts. Nothing else.
Rules
- One engagement per run. Don't mix multiple clients or projects.
- Anonymize by default. Change names, industry, or details as needed. Keep the pattern — change the specifics. Check whether two details together could identify the client.
- Numbers over adjectives. "$200K in one quarter" not "significant revenue growth." Every post needs at least one concrete number.
- Scene-led, not thesis-led. Every post opens with a specific person in a specific situation. Never open with a thesis ("Every consulting engagement has the same leak").
- No fabrication. If the input doesn't contain a number, flag what's missing. A post with "Missing: quantified outcome" tells the user what to add.
- Three posts always. Produce all three angles every run.
- Output as a markdown file. Name:
[engagement-type]-content-[YYYY-MM-DD].md - First person for posts. Posts are in the writer's voice — first person, conversational, one sentence per line.
Output Format
# Content-from-Delivery
| | |
|---|---|
| **Client type** | [Anonymized — industry, size] |
| **Scope** | [What was delivered] |
| **Timeline** | [Duration] |
| **Outcome** | [One-sentence headline result] |
---
## Three-Layer Extraction
### Surface
[2-3 sentences — the flat version]
### Real
[Full paragraph — numbers, before/after, timeline]
### Prospect
[2-3 sentences — starts where the reader starts]
---
## Post 1: The Pattern
[One sentence per line. 150-250 words.]
---
## Post 2: The Before/After
[One sentence per line. 150-250 words.]
---
## Post 3: The Capability
[One sentence per line. 150-250 words.]Do not include a Quality Check section in the output. The QC runs internally before presenting and is used to correct the posts. The user sees only the snapshot, extraction, and three finished posts.
What Makes This Different
Most practice owners finish client work and move on. The outcome exists in their notes and fades before the next sales conversation.
This skill catches outcomes before they disappear. You describe the engagement in whatever form you have. The three-layer extraction pulls out the story you didn't know was there. You get 3 posts you can publish today.
If you also have the Client Intelligence Brief skill, they pair: the brief reveals what's happening with active clients. This skill turns what already happened into content that attracts the next one.