alirezarezvani/claude-skills / marketing/linkedin/skills/linkedin-content
linkedin-content
VerifiedWrite, edit or review a LinkedIn post: story, how-to, carousel, video script or poll. Use whenever the user wants a LinkedIn post, asks if their draft is good, or wants a blog or talk turned into posts.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.1 KB |
| assets/example_post.md | markdown | 2.3 KB |
| assets/post_templates.md | markdown | 3.8 KB |
| references/accessibility_and_inclusion.md | markdown | 5.8 KB |
| references/hook_and_fold_mechanics.md | markdown | 6.0 KB |
| references/post_formats_canon.md | markdown | 6.0 KB |
| references/repurposing_discipline.md | markdown | 5.8 KB |
| scripts/format_picker.py | script | 11.8 KB |
| scripts/post_linter.py | script | 16.2 KB |
| scripts/repurpose_splitter.py | script | 12.6 KB |
assets/example_post.md
View on GitHub# Worked Example — a post that passes the linter
The post below scores 98/100 in `post_linter.py` with one INFO finding (it sits below the
1,300-2,500 character band, which is not a defect). Annotations follow.
---
Our onboarding took 6 weeks. We got it to 4 days without hiring anyone.
The bottleneck was not the product. It was that three different teams each owned
one step and none of them owned the handoff.
What we changed:
1. One named owner for the whole path, not per step. Every stall now has someone
whose week it ruins.
2. We deleted the "kickoff call" and replaced it with a 4-question form. 80% of
accounts never needed the call.
3. We stopped treating the CRM stage as the source of truth and started measuring
the customer's first real use.
The part I got wrong: I assumed the delay was engineering capacity. It was
handoffs. We spent five weeks building automation for the wrong step before
anyone measured where the time actually went.
If you are staring at a slow onboarding number, measure the wait between steps
before you optimise any single step. That is where ours was hiding.
What did the handoff cost you the last time you measured it?
---
## Why it passes
**Hook (first 140 characters).** Two complete sentences land inside the mobile fold, both
carrying numbers, and the second names a constraint people assume is binding — "without
hiring anyone". A reader decides on those two sentences alone.
**Specificity throughout.** 6 weeks, 4 days, 80%, five wasted weeks. Every number is one the
author could be challenged on, which is exactly why they carry weight.
**The admission.** "The part I got wrong" is the load-bearing paragraph. It is expensive to
write, which is why it reads as true, and it is the paragraph practitioners reply to.
**Structure.** Seven blocks, none longer than four lines. Numbered list where the content is
a sequence. No Unicode pseudo-bold, no emoji, no hashtags — none of which are required.
**The close.** A real question with a specific answer available only to someone who has
measured the same thing. Not "thoughts?".
**No link in the body.** If there were a write-up, it goes in the first comment with "link
in the comments" in the post.
## Run it yourself
```bash
python3 ../scripts/post_linter.py --sample --output human
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |