← All skills
SEOv1.0.0 · 2026-08-07
Distribution Kit
The reason this runs the same day the pillar publishes: without distribution, even a perfect pillar takes 6 to 12 months to rank. The kit is how the post earns its first six months of readers while search catches up.
What it does
- Extract the distributable core
- Build the four pieces natively
- Sequence the day
- Log it
SKILL.md
---
name: distribution-kit
description: Turn a published pillar into a 4-channel distribution kit — LinkedIn post, Instagram carousel brief, Reel script, and email draft — shipped the same day the pillar goes live. Use when asked to distribute or promote a blog post, repurpose a pillar for social, turn an article into LinkedIn or Instagram content, build a launch kit for new content, get traffic before rankings arrive, or someone says 'we published it and nobody saw it'. For the pillar itself, see blog-content-writer. For each channel's craft, see the social skills.
metadata:
version: 1.0.0
---
# Distribution kit
The reason this runs **the same day the pillar publishes**: without
distribution, even a perfect pillar takes **6 to 12 months to rank.** The kit
is how the post earns its first six months of readers while search catches up.
One pillar → four channels: **a LinkedIn post, an Instagram carousel brief, a
Reel script, and an email newsletter draft.** Each is a native piece built from
the pillar's substance — never four copies of the link with different captions.
## Before you start
| Input | Why |
| --- | --- |
| The live pillar URL and its draft source | The kit lifts from substance, not from the summary |
| voice-rules.md | Four channels, one voice |
| The pillar's named framework and its numbers | The framework is the kit's spine; the register's numbers are its proof |
| Which channels the operator actually runs | A kit for channels nobody posts on is homework, not distribution |
## Step 1 — Extract the distributable core
From the pillar: the **named framework** (the thing people cite), the 2–3
sharpest claims *with their register numbers*, the best comparison table, and
the one imperfect truth that makes it human. This core feeds all four pieces —
consistency across channels is what builds the association.
## Step 2 — Build the four pieces natively
| Piece | Shape | The native rule |
| --- | --- | --- |
| **LinkedIn post** | Hook line → the framework compressed → one number → soft CTA to the pillar | Written to be read in-feed; the link earns its click, the post stands alone without it |
| **Instagram carousel brief** | Slide-by-slide: hook card, one framework step per card, CTA card | A brief the designer executes: per-card text + visual note (see carousel craft rules) |
| **Reel script** | The five-beat short-video spine on the pillar's sharpest claim | Hook in 3 seconds, works on mute, under 15s ideal |
| **Email draft** | Subject + a personal note on why this was written → the framework's one best insight → the link | Written as a note from the operator, not a broadcast announcement |
Every piece carries only register numbers, in the operator's voice, no em
dashes — the content rules do not relax off-site.
## Step 3 — Sequence the day
Same-day order that respects each channel: email to the list (owned audience
first), LinkedIn post, carousel handed to design (or posted if ready), Reel
scheduled per the operator's video cadence. The kit ships as one package; the
operator decides timing within the day.
## Step 4 — Log it
The registry row gains a distribution field: which pieces shipped, where, when.
The audit's traffic questions later ("did distribution run?") get answered from
the registry, not memory.
## Output
```
# Distribution kit: <pillar title> · same-day
## LinkedIn post [ready to paste]
<the post>
## Carousel brief [ready for design]
| Card | Text | Visual note |
## Reel script [five beats, ≤15s]
| Beat | Sec | Line | Overlay |
## Email draft [subject + body]
<the draft>
Core used: framework "<name>" · numbers: <register refs> · voice ✓
Channels skipped: <any the operator doesn't run — stated, not silently dropped>
Registry: distribution field updated
```
## When it breaks
| What you see | What it means | The fix |
| --- | --- | --- |
| Four channels, same caption + link | The kit was a link blast, not native pieces | Each piece rebuilt from the core, native to its channel |
| LinkedIn post is just "New blog! Link below" | The post doesn't stand alone | The framework compressed IS the post; the link is the depth offer |
| Kit ships a week after the pillar | Same-day rule slipped | The kit is part of the publish run, not a follow-up task |
| Carousel brief is one line per card | Not executable by a designer | Per-card text plus visual notes — a brief, not a wish |
| Numbers differ across the four pieces | Register discipline lost in compression | One core, one set of numbers, four shapes |
| Kit built for channels nobody posts on | Channel list assumed | Ask which channels actually run; skip the rest openly |
| Traffic flat despite the kit | Pieces shipped but not sequenced to owned audience first | Email first — the list is the one channel you control |
Never let the kit substitute for the pillar's quality or the pillar excuse a
lazy kit. The pillar earns the rankings in months; the kit earns the readers
today — both jobs, both standards.
## Rules
- **Same day, always**, because the 6–12 month ranking lag is exactly the gap
the kit exists to fill.
- **Native pieces, never a link blast**, because each channel rewards its own
shape and punishes foreign ones.
- **One core, four shapes**, because consistent frameworks and numbers across
channels are what make the association stick.
- **Register numbers only, voice rules on**, because distribution is still
publishing — the claims discipline travels.
- **Skipped channels are stated**, because a silently missing piece looks like
a forgotten one.
## Related skills
- **blog-content-writer** — the pillar this kit distributes.
- **ugc-style-video-script** — the Reel script's five-beat craft, in full.
- **carousel-ad-builder** — card craft rules the brief borrows (organic flavour).
- **publish-workflow** — triggers this kit as part of the growth layer.
Reviews
Sign in to leave a review.
