borghei/Claude-Skills / tools/linkedin/linkedin-post-writer
linkedin-post-writer
VerifiedDrafts LinkedIn posts from a brief: picks an angle and opening pattern the author's real material supports, structures the body, and gates the draft before it is pasted. Use when writing a post, choosing a hook, or checking a draft before publishing.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 16.3 KB |
| assets/post_brief_template.md | markdown | 4.2 KB |
| assets/sample_brief.json | config | 1.3 KB |
| assets/sample_draft.txt | markdown | 1.2 KB |
| assets/sample_draft_revised.txt | markdown | 1.1 KB |
| references/opening-patterns.md | markdown | 12.8 KB |
| references/post-structures.md | markdown | 11.4 KB |
| references/pre-publish-gate.md | markdown | 10.2 KB |
| scripts/angle_picker.py | script | 13.1 KB |
| scripts/post_gate.py | script | 12.7 KB |
assets/sample_draft_revised.txt
View on GitHubOn 9 June we cancelled our weekly all-hands with two days' notice and nothing to replace it.
The second half of that sentence was the mistake.
I'd defended that meeting for three years. Sixty-two people, every Monday, 62 person-hours a week. In a typical week about three questions were asked out loud, nearly always by the same four people.
The first fortnight without it was worse. Two teams shipped conflicting changes to the pricing page, and a client noticed before we did.
What we should have started with, and now run:
1. Each team lead posts a written update by 10:00 on Monday.
2. Questions go into one thread and get answered by Wednesday.
3. On the first Monday of the month there's a 20-minute call. Questions only, no slides.
Within a month, questions asked in the open went from about 3 a week to 19.
Ines in finance wrote: "I have never once asked a question in that meeting and I have asked four this week."
I'd assumed the meeting was where alignment happened. It was where four people talked.
If you've replaced a standing meeting with writing, what broke in the first two weeks?
#operations #meetings
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 |