Skip to content

borghei/Claude-Skills / tools/linkedin/linkedin-content-repurposer

linkedin-content-repurposer

Verified

Turns something made for another channel (a thread, a video or talk transcript, a blog post, a newsletter) into a post that reads as native to LinkedIn, without changing what the source says. Use when existing material should become a LinkedIn post rather than writing one from a blank page.

assets/repurposing_brief_template.md

View on GitHub
# Repurposing Brief

Agree this with the author before drafting. It is one page on purpose: if the
point, the reader and the carry-over list cannot be written down briefly, the
post is not ready to be written.

## Source

| Field | Value |
|-------|-------|
| Source title or description | |
| Channel it was made for | thread / talk transcript / article / newsletter / interview / note |
| File path | |
| Date of the source | |
| Whose words | author's own / includes other speakers / employer or client material |
| Permission to adapt | yes / needs checking with: |
| Post will go out under | |

Assumptions made because an input was not confirmed:

-

## Analyser result

Paste from `repurpose_analyzer.py`.

| Field | Value |
|-------|-------|
| Source type detected | |
| Size (characters / words) | |
| Move | rebuild in place / compress / split / expand |
| Posts in this source | |
| Rework findings (ids) | |
| Blockers | |

## This post

| Field | Value |
|-------|-------|
| Which post of how many from this source | of |
| The single point, in one sentence the author would defend | |
| Spine candidate chosen (number and text) | |
| Shape | finding first / reversal / case |
| The one reader | |
| The one ask (or none) | |
| Pillar, if a plan is in use | |

## Carry-over list

Facts that must arrive intact. Copy them exactly from the source.

| # | Fact | Figure | Unit and period | What it counts | Source line |
|---|------|--------|-----------------|----------------|-------------|
| 1 | | | | | |
| 2 | | | | | |
| 3 | | | | | |
| 4 | | | | | |

One phrase to keep verbatim in the author's words:

>

## Cut list

| Item | Why it goes |
|------|-------------|
| | channel artefact / second point / repeats context / other speaker / not cleared |
| | |
| | |

Points set aside for other posts:

-

## New material

Anything not in the source that the rebuild will add. Each line needs a source
of its own.

| Addition | Comes from | Author confirmed |
|----------|------------|------------------|
| | author in conversation / story bank entry id | yes / no |
| | | |

Derived figures the author has approved (show the arithmetic):

-

## Decisions

| Question | Decision |
|----------|----------|
| Link to the source in the post? | no / in the body / in a comment by the author |
| Other people named? | none / named with consent: / anonymised |
| Length band, if not the default | |
| Opening window, if not the default | |

## Checks

- [ ] Transcript figures confirmed against slides or the speaker
- [ ] Draft written from the spine and this brief with the source closed
- [ ] `draft_fidelity_check.py --fail-on blocker` exits 0
- [ ] Every carry-over row compared with the draft by eye
- [ ] No rework findings left, or each one accepted with a reason below
- [ ] Author has read the draft against the source

Findings accepted on purpose, and why:

-

## Example (fictional), filled in for the sample thread

| Field | Value |
|-------|-------|
| Source | Nine-part thread on defect cards, Fenwater Transit |
| Move | rebuild in place |
| The single point | We did not lack data on bus faults; known faults reached a fitter sixteen hours too late |
| Spine candidate | 1: "We changed one thing: the night fitter reads the defect cards at 10pm..." |
| Shape | finding first |
| The one reader | An operations lead about to buy a predictive tool |
| The one ask | "How long is that gap where you work?" |

| # | Fact | Figure | Unit and period | What it counts |
|---|------|--------|-----------------|----------------|
| 1 | Fleet size | 86 | buses | Fleet the author plans maintenance for |
| 2 | Breakdowns before | 31 | first six months of 2024 | Roadside breakdowns |
| 3 | Already reported | 19 of the 31 | same period | Breakdowns preceded by a driver's defect card |
| 4 | Breakdowns after | 12 | second half of 2024 | Roadside breakdowns |
| 5 | New reading time | 10pm | daily | When the night fitter reads the cards |

Cut: numbering, the handle, the hashtag cluster, the repost ask, the opening
segment. Link: left out of the body. New material: none.
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
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: 194kUpdated Claude CodeCodexVerifiedInstall