agentleFS
deepakkambojdeepakkamboj/personal-assistant-skills/.agents/skills/linkedin/SKILL.md

linkedin

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

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.
  • ReScienceLabSkill

    reddit

    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-aiSkill

    instagram

    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-HunterAiSkill

    tiktok

    TikTok platform integration. Manage videos, view analytics, and track engagement.

    Also in 3 projects that use this

  • refly-aiSkill

    youtube

    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

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
  1. Very specific:

    Create this checklist first.

    line 33
  2. Very specific:

    Load your profile: Read config.profile (headline, content pillars, voice, brand) and content.md voice samples so everything sounds like you.

    line 48
  3. Distinctive:

    Ask if anything is missing: If the request lacks a concrete topic/angle, ask before drafting.

    line 51

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

LinkedIn

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

  1. Gather inputs. Parse $ARGUMENTS. The first word selects a sub-skill (see table); the rest is the topic or content.
  2. Load your profile. Read config.profile (headline, content pillars, voice, brand) and content.md voice samples so everything sounds like you. Read memory.md / notes.md for learned preferences and open follow-ups.
  3. Ask if anything is missing. If the request lacks a concrete topic/angle, ask before drafting. Never invent achievements, numbers, or quotes.
  4. Route to the sub-skill and follow its SKILL.md.
  5. Validate & output, then offer next steps (e.g. review, schedule, publish). Append any new durable preference to memory.md and any follow-up to notes.md (python .agents/scripts/memory.py remember|note "...").

Sub-skills

CommandSkillWhat it does
post [topic]linkedin/postDraft a LinkedIn post in your voice
post-planner ...linkedin/post-plannerPlan a batch/calendar of posts
hook [topic]linkedin/hookGenerate scroll-stopping hooks
carousel [topic]linkedin/carouselDraft a multi-slide carousel
post-review [draft]linkedin/post-reviewScore and improve a draft
repurpose [content]linkedin/repurposeRepurpose content across formats
positioninglinkedin/positioningSharpen positioning and value proposition
content-pillarslinkedin/content-pillarsDefine content pillars
comment [post]linkedin/commentDraft engagement comments
connect [person]linkedin/connectDraft connection-request notes
collab [target]linkedin/collabDraft collaboration outreach
profilelinkedin/profileAudit and improve your LinkedIn profile
newsletter [topic]linkedin/newsletterDraft 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.