Individual skill
linkedin-content
Use when someone wants to write, edit, or lint a LinkedIn post — a story, how-to, opinion piece, carousel script, video script, or poll — or wants an article, talk, or transcript repurposed into posts. Triggers on "write a LinkedIn post", "is this hook any good", "review my post", "turn this into LinkedIn posts", "carousel", "what format should this be". Lints posts 0-100 on mechanics, hook, integrity, and accessibility; picks the format the material actually supports; and splits long sources into standalone units with a reuse ledger.
skills-imported/linkedin-content/SKILL.md
Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 8, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 54
- Repository last updated
- Oct 10, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- ai-agents-automation Repository topic
- ai-skills Repository topic
- awesome Repository topic
- awesome-list Repository topic
- chatgpt Repository topic
- claude-skills Repository topic
- meta-ai Repository topic
- muse-ai Repository topic
- writing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 5,527 bytesSKILL.mdcore · 5,527 bytesSKILL.mdcore · 5,527 bytesSKILL.mdcore · 5,527 bytesSKILL.mdcore · 5,527 bytesSKILL.mdcore · 5,527 bytesSKILL.mdcore · 5,527 bytesSKILL.mdcore · 5,527 bytesreferences/accessibility_and_inclusion.mddoc · 5,914 bytesreferences/hook_and_fold_mechanics.mddoc · 6,191 bytesreferences/post_formats_canon.mddoc · 6,122 bytesreferences/repurposing_discipline.mddoc · 5,963 bytesscripts/format_picker.pyruns · 12,046 bytesscripts/post_linter.pyruns · 15,831 bytesscripts/repurpose_splitter.pyruns · 12,165 bytes
Read excerpt
# LinkedIn Content — format, draft, lint
The post is not the deliverable; the specific thing only this person can say is. The scripts
handle format choice, mechanical faults, and de-duplication. The interesting part — what
actually happened and what it cost — comes from the user, and cannot be generated.
## Workflow
**1. Check the brief exists.** If there is no positioning brief, offer `linkedin-strategy`
first as a question. Posts without pillars are noise. Never chain silently.
**2. Pick the format from the material, not from fashion.**
```bash