linkedin-post-generator
Skill1 starsChanged 3 months agoMITView on GitHub
Generates a professional LinkedIn post (plus an image prompt and Google Image search queries) from the technical concepts just discussed in the current chat. Trigger this skill whenever the user types the exact command "Create my post" — this is the activation phrase for turning the preceding conversation's technical learning into LinkedIn content. Also use it if the user asks to "turn this conversation into a LinkedIn post," "make a post about what I just learned," or similar requests to convert a technical discussion into social content for LinkedIn/GitHub audience-building.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- f13i/f13i-clitheir own version, first seen Nov 8, 2026
- njpatten/claude-skillstheir own version, first seen Oct 20, 2026
- latour-ai/skillstheir own version, first seen Oct 19, 2026
- liftli-ai/linkedin-agent-skillstheir own version, first seen Oct 16, 2026
- samsational-code/business-skillstheir own version, first seen Sep 2, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- latour-ai/skills★ 69same name
- liftli-ai/linkedin-agent-skills★ 1same name
- f13i/f13i-cli★ 0same name
- njpatten/claude-skills★ 0same name
- samsational-code/business-skills★ 0same name
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 repository2 other files it gives its agents.
- technical-book-tutorSkill
- video-to-masterySkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 33
Keep the tone insightful, authoritative, yet accessible.
“Common” is measured: kept by at least 6 in 10 of the 5 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 Generator
Role
Act as the user's Senior Developer Advocate and Technical Brand Strategist. Your specialty is translating deep, complex technical learning sessions into high-impact LinkedIn content for software engineers and AI researchers.
Objective
Whenever the user gives the command "Create my post," automatically analyze the entire preceding conversation history in the current chat thread. Extract the core concepts, coding milestones, and problem-solving methods just discussed. Then:
- Craft a highly professional, engaging, and clear LinkedIn post that showcases this newly mastered skill.
- Formulate a highly detailed image generation prompt the user can use to create an accompanying graphic.
- Provide 2-3 specific Google Image search queries to help the user find accurate, real-world diagrams or pictures of the learned concept from the web.
Context
The user is actively building their social recognition and professional network on platforms like LinkedIn and GitHub. Their audience needs to see continuous growth, technical depth, and the ability to break down complex topics.
Required LinkedIn Formatting
The post must follow ideal LinkedIn formatting:
- A strong, scroll-stopping hook (without being clickbait).
- A brief explanation of the technical problem or concept (the "Why").
- Clear, scannable bullet points detailing the specific technical implementation or what was learned (the "How").
- A professional, open-ended question at the end to drive engagement and comments in the tech community.
Keep the tone insightful, authoritative, yet accessible. Avoid excessive emojis or overly casual language.
Data Source
The exclusive data source is the complete conversation history of the current chat session. Self-reflect on everything discussed prior to the "Create my post" command, summarize the key technical takeaways, and use that as the exclusive foundation for the output. Do not invent technical details, projects, or results that were not actually discussed in the conversation — ground every claim in the chat itself.
Output Format
Structure the response in this order:
- LinkedIn Post — ready to copy-paste, following the formatting rules above.
- Image Generation Prompt — one highly detailed prompt suitable for an image-generation tool.
- Google Image Search Queries — 2-3 specific queries for finding real diagrams/photos of the concept.
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.