linkedin-post
Skill2 starsChanged 58 days agoMITView on GitHub
Use when the user wants to write a LinkedIn post from an idea, a link, a project win, or a lesson. Produces three variants in the user's voice with hooks that don't sound like every other post.
41 other projects use a version of this.
Adopted by
Most recently taken up by
- dmccreary/claude-skillstheir own version, first seen Nov 9, 2026
- dmccreary/ibook-skillstheir own version, first seen Nov 8, 2026
- kristian-presso/claude-marketing-skillstheir own version, first seen Nov 8, 2026
- olivMertens/copilot-skillstheir own version, first seen Nov 8, 2026
- markbaindesign/bain-studiotheir own version, first seen Nov 1, 2026
- sophonfinance-wq/finance-automation-portfoliotheir own version, first seen Nov 1, 2026
Used with
Projects with it also use youtube-upload, proposal-writer and 3 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
BlackLotus1974Skillyoutube-upload
Upload videos to Atchalta's YouTube channel (office@atchalta.com). Use when the user asks to upload a video to YouTube, list YouTube videos, manage playlists, or update video metadata. Trigger phrases: 'upload to youtube', 'youtube video', 'publish video', 'post to youtube', 'list my videos', 'youtube playlists'.
Also in 3 projects that use this
ncklrsSkillproposal-writer
Expert sales proposal and pricing presentation strategist. Use when writing proposals, executive summaries, ROI business cases, pricing presentations, SOWs (Statement of Work), RFP responses, or competitive positioning documents. Covers proposal structure, terms positioning, design formatting, follow-up strategy, and win-rate optimization.
Also in 3 projects that use this
Microsoft AzureSkilllint
Run all linting and spell checking for TypeScript and Rust code. Run this before committing to catch style issues, clippy warnings, and misspellings.
Also in 3 projects that use this
OpenAISkillbrainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Also in 3 projects that use this
GoogleSkillgrill-me
A relentless interview to sharpen a plan or design.
Also in 3 projects that use this
Other versions41 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 41
- langchain-ai/langgraph-101★ 708same name
- hamzafarooq/claude-code-starter★ 145same name
- dmccreary/claude-skills★ 110same name
- dmccreary/ibook-skills★ 110same name
- kevinbadi/ai-os-skills★ 69same name
- publora/skills★ 68same name
- az9713/ai-co-writing-claude-skills★ 61same name
- JamsusMaximus/growth-agents★ 21same name
- langchain-ai/langgraph-101-ts★ 19same name
- duncan-buildroom/profit-room-skills★ 18same name
31 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- invoice-generatorSkill
- meeting-notes-to-actionsSkill
- setup-businessSkill
- weekly-reviewSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 7 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 36 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Write posts that sound like the user, not like LinkedIn.
- Very specific: line 11
Read .solo/business.md for tone, services, and who the audience is (ideal clients — posts should be useful to *them*, not to peers).
- Very specific: line 28
After the three, add a ## Notes line: which variant you'd post and why, in one sentence.
- Distinctive: line 32
Write like a person talking to one reader.
- Distinctive: line 33
No emojis unless the tone section says so.
- Distinctive: line 34
No fake vulnerability, no "I failed 100 times" unless it's true and specific.
- Distinctive: line 37
Do not write engagement-bait (polls, "comment YES", "repost if you agree").
- Distinctive: line 38
Do not exceed 200 words per variant.
- Distinctive: line 39
Do not fabricate results or client stories.
“Common” is measured: kept by at least 6 in 10 of the 36 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
LinkedIn Post
Write posts that sound like the user, not like LinkedIn. Three variants so they can pick, not edit.
Step 1 — Load context
Read .solo/business.md for tone, services, and who the audience is (ideal clients — posts should be useful to them, not to peers).
Step 2 — Get the seed
One of: an idea, a link/article (fetch and read it), a project outcome, a mistake and lesson, a question the user keeps getting asked. If the seed is vague ("post about AI"), ask for the one specific thing they believe that others might not.
Step 3 — Write three variants
Save to content/linkedin/<YYYY-MM-DD>-<slug>.md. Each variant:
- Hook (first line, before "see more"): a specific claim, number, or moment. Under 12 words. No questions like "Ever wondered…?", no "Unpopular opinion:", no "I've been thinking a lot about…".
- Body: 80–180 words. Short paragraphs (1–2 lines). One idea. Concrete example from the user's work if the seed allows.
- Close: either a plain takeaway or a real question the user wants answered. No "Agree?" No "Thoughts?"
- No hashtags unless business.md says to use them. Max 3 if so.
Variant angles:
- A — Story: what happened, what it taught. Past tense, first person.
- B — Contrarian/insight: the thing most people get wrong, and the better way.
- C — Practical: a numbered mini-how-to (3–5 steps) the audience can use today.
After the three, add a ## Notes line: which variant you'd post and why, in one sentence.
Tone rules
- Match business.md tone. If it says "no buzzwords", remove: game-changer, leverage, unlock, journey, thrilled, humbled, delve.
- Write like a person talking to one reader.
- No emojis unless the tone section says so.
- No fake vulnerability, no "I failed 100 times" unless it's true and specific.
Do not
- Do not write engagement-bait (polls, "comment YES", "repost if you agree").
- Do not exceed 200 words per variant.
- Do not fabricate results or client stories.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.