borghei/Claude-Skills / tools/linkedin/linkedin-content-repurposer
linkedin-content-repurposer
VerifiedTurns 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 15.8 KB |
| assets/repurposing_brief_template.md | markdown | 4.0 KB |
| assets/sample_article.md | markdown | 3.0 KB |
| assets/sample_draft.txt | markdown | 928 B |
| assets/sample_draft_clean.txt | markdown | 1.1 KB |
| assets/sample_talk_transcript.txt | markdown | 1.7 KB |
| assets/sample_thread.txt | markdown | 1.3 KB |
| references/fidelity-rules.md | markdown | 11.3 KB |
| references/native-fit-guide.md | markdown | 10.4 KB |
| references/source-format-playbooks.md | markdown | 10.3 KB |
| scripts/draft_fidelity_check.py | script | 12.0 KB |
| scripts/repurpose_analyzer.py | script | 12.6 KB |
| scripts/repurpose_rules.py | script | 12.5 KB |
assets/sample_thread.txt
View on GitHub1/ A thread 🧵 on the dullest change I ever made to a bus depot, and why it beat every piece of software we bought that year.
2/ I plan maintenance for 86 buses at Fenwater Transit. In 2024 we had 31 roadside breakdowns in the first six months. Management wanted a predictive maintenance platform. cc @fenwater_ops
3/ Before anyone signed anything I read every breakdown report by hand. It took two evenings. 19 of the 31 were things a driver had already written on a defect card.
4/ So the information existed. It was just sitting in a tray. The cards were collected at 6am and typed up at 2pm, after the buses had already gone back out.
5/ We changed one thing: the night fitter reads the defect cards at 10pm, before the morning run-out, instead of the office reading them the next afternoon.
6/ Second half of 2024: 12 roadside breakdowns. Same fleet, same routes, same budget. No new system.
7/ I used to think our problem was that we did not have enough data. We had the data. We had it sixteen hours too late.
8/ What I'd tell any ops team: before you buy something that predicts failures, time how long a known defect takes to reach someone who can fix it.
9/ Full write-up with the card template here: https://example.com/fenwater-defect-cards RT if this was useful, and follow for more depot stories. #maintenance #fleet #transit #operations
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: 198k | 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 |