Skill1 starsChanged 2 months agoMITView on GitHub
LinkedIn hub. Routes to the content sub-skills (drafting posts, hooks, carousels, planning, reviewing, repurposing, comments, connection notes, positioning, profile audits) and explains how publishing and engagement stats work. Publishing itself is done by the connected-workspace MCP server, not by this repo.
23 other projects use a version of this.
Adopted by
Most recently taken up by
- AceDataCloud/Skillstheir own version, first seen Nov 8, 2026
- YangsonHung/awesome-agent-skillstheir own version, first seen Nov 8, 2026
- ishandutta2007/Awesome-Agent-Skillstheir own version, first seen Nov 8, 2026
- Astorgato/asistente-cv-linkedintheir own version, first seen Nov 8, 2026
- nurmdrafi/pi-nativetheir own version, first seen Nov 1, 2026
- joevstaas/awesome-claude-skillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use reddit, instagram and 2 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.
ReScienceLabSkillreddit
Search and retrieve content from Reddit. Get posts, comments, subreddit info, and user profiles via the public JSON API. Use when user mentions Reddit, a subreddit, or r/ links.
Also in 6 projects that use this
refly-aiSkillinstagram
Integrate with Instagram for social media. Use when you need to: (1) post content to Instagram, (2) manage media and insights, or (3) automate Instagram publishing workflows.
Also in 4 projects that use this
G-HunterAiSkilltiktok
TikTok platform integration. Manage videos, view analytics, and track engagement.
Also in 3 projects that use this
refly-aiSkillyoutube
Integrate with YouTube for video management. Use when you need to: (1) upload videos to YouTube, (2) manage channel content, or (3) retrieve video analytics and insights.
Also in 3 projects that use this
Other versions23 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 23
- sigcli/sigcli★ 293same name
- getnao/sylph★ 195same name
- hyperfx-ai/marketing-skills★ 112same name
- Linked-API/linkedin-skills★ 110same name
- backpropagation6/claude-linkedin-automation★ 21same name
- ishandutta2007/Awesome-Agent-Skills★ 21same name
- YangsonHung/awesome-agent-skills★ 18same name
- AceDataCloud/Skills★ 17same name
- abhayla/claude-best-practices★ 9same name
- mediause/agent-skills★ 9same name
13 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 repository10 other files it gives its agents.
- .agents/AGENTS.mdAGENTS.md
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- ai-digestSkill
- daily-digestSkill
- humanizeSkill
- meSkill
- newsletterSkill
- pixelSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 19 edited versions we read keep these.
1
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
- Very specific: line 33
Create this checklist first.
- Very specific: line 48
Load your profile: Read config.profile (headline, content pillars, voice, brand) and content.md voice samples so everything sounds like you.
- Distinctive: line 51
Ask if anything is missing: If the request lacks a concrete topic/angle, ask before drafting.
“Common” is measured: kept by at least 6 in 10 of the 19 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
Your LinkedIn branding hub. Content is drafted by the sub-skills here; publishing and
engagement reads are handled by the connected-workspace MCP server.
Role
You are the user's LinkedIn hub. You route requests to the right content sub-skill and explain how publishing works via the connected-workspace MCP.
Context to load
Load and honor these before acting:
config.profile— identity, role, voice, brand, content pillars (personalize everything)content.md— voice samples and prompt guidance (when tone matters)memory.md/notes.md— learned preferences and open follow-ups- Sub-skills live under
linkedin/
Workflow
Step 0: TodoWrite Checklist
Create this checklist first; mark one task in_progress, finish it, then move to the next.
TodoWrite([
{ content: "Gather inputs; load config.profile, content.md, memory.md & notes.md", status: "in_progress" },
{ content: "Ask for any missing inputs — never assume or hallucinate", status: "pending" },
{ content: "Route to the correct sub-skill and follow it", status: "pending" },
{ content: "Validate output; record new facts to memory.md / follow-ups to notes.md", status: "pending" }
])Steps
- Gather inputs. Parse
$ARGUMENTS. The first word selects a sub-skill (see table); the rest is the topic or content. - Load your profile. Read
config.profile(headline, content pillars, voice, brand) andcontent.mdvoice samples so everything sounds like you. Readmemory.md/notes.mdfor learned preferences and open follow-ups. - Ask if anything is missing. If the request lacks a concrete topic/angle, ask before drafting. Never invent achievements, numbers, or quotes.
- Route to the sub-skill and follow its
SKILL.md. - Validate & output, then offer next steps (e.g. review, schedule, publish). Append any
new durable preference to
memory.mdand any follow-up tonotes.md(python .agents/scripts/memory.py remember|note "...").
Sub-skills
| Command | Skill | What it does |
post [topic] | linkedin/post | Draft a LinkedIn post in your voice |
post-planner ... | linkedin/post-planner | Plan a batch/calendar of posts |
hook [topic] | linkedin/hook | Generate scroll-stopping hooks |
carousel [topic] | linkedin/carousel | Draft a multi-slide carousel |
post-review [draft] | linkedin/post-review | Score and improve a draft |
repurpose [content] | linkedin/repurpose | Repurpose content across formats |
positioning | linkedin/positioning | Sharpen positioning and value proposition |
content-pillars | linkedin/content-pillars | Define content pillars |
comment [post] | linkedin/comment | Draft engagement comments |
connect [person] | linkedin/connect | Draft connection-request notes |
collab [target] | linkedin/collab | Draft collaboration outreach |
profile | linkedin/profile | Audit and improve your LinkedIn profile |
newsletter [topic] | linkedin/newsletter | Draft a LinkedIn newsletter edition |
Publishing & stats (via MCP)
Drafting happens here; the live LinkedIn API is exposed by the connected-workspace MCP
server (.agents/mcp/connected-workspace.json). Once a draft is approved:
- Publish text:
linkedin_publish_text - Publish with an image:
linkedin_publish_image - Read your profile / posts:
linkedin_get_profile,linkedin_list_posts,linkedin_get_post - Engagement:
linkedin_get_engagement - Delete a post:
linkedin_delete_post
Publishing and deletion are write actions — confirm with the user before calling them.
Standard LinkedIn APIs cannot edit profile fields (headline, experience, skills); the
profile sub-skill produces recommended copy for you to apply manually.
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.

