agentleFS
AbdulSamad94AbdulSamad94/Personal-AI-Employee/.agents/skills/linkedin-skill/SKILL.md

linkedin-skill

Skill8 starsChanged 4 months agoMITView on GitHub

Draft and schedule LinkedIn posts to generate business leads and build professional presence. Use when the user says "write a LinkedIn post", "post on LinkedIn", "create content", "share on LinkedIn", or when a completed project or milestone should be announced. Also triggers on weekly scheduled post days.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create compelling, value-driven LinkedIn posts that build the business owner's professional brand and generate inbound leads.

    line 12
  2. Distinctive:

    NEVER post directly — always create an approval file first.

    line 14
  3. Distinctive:

    Use numbers when possible ("3 lessons", "saved 18 hours", "$2,450 revenue")

    line 71
  4. Distinctive:

    Write like a human, not a press release

    line 74
  5. Distinctive:

    Always add 3-5 hashtags at the end

    line 75
  6. Very specific:

    Create file at vault/Pending_Approval/LINKEDIN_[YYYYMMDD_HHMMSS].md:

    line 80
  7. Distinctive:

    If no specific trigger exists, check these sources for post ideas:

    line 129

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Skill: LinkedIn Content Creation

Purpose

Create compelling, value-driven LinkedIn posts that build the business owner's professional brand and generate inbound leads. NEVER post directly — always create an approval file first.

Step 1 — Gather Context

Before writing, read:

  • vault/Business_Goals.md — what the business is about and current goals
  • vault/Done/ — recent completed tasks (last 7 days) for post ideas
  • vault/Briefings/ — latest CEO briefing for business highlights
  • vault/Company_Handbook.md — brand voice and communication rules

Step 2 — Determine Post Type

Post TypeWhen to UseEngagement Style
AchievementProject completed, milestone hit"We just did X — here's how"
InsightLesson learned from recent work"After doing X, I learned Y"
ValueTip or advice for target audience"3 things I wish I knew about X"
QuestionStart a conversation"What's your biggest challenge with X?"
Behind the scenesShow your process"Here's what my typical week looks like"

Step 3 — Write the Post

LinkedIn Post Formula (High Engagement):

[HOOK — first line that stops the scroll]

[BLANK LINE — always leave this]

[Context or story setup — 1-2 lines]

[Main value/insight/achievement — 3-5 lines]

[Specific detail or example — makes it credible]

[Takeaway or lesson — what readers can apply]

[Call to action or question — drives comments]

[BLANK LINE]

[3-5 relevant hashtags]

Hook Examples (Use as inspiration, not copy):

  • "I built an AI employee that manages my Gmail and LinkedIn. Here's what happened."
  • "Most developers are building chatbots. I built something different."
  • "We completed Project Alpha 2 weeks early. Here's the one thing that made the difference."

Writing Rules:

  • Maximum 1300 characters total
  • First line must work as a standalone hook — no context needed
  • Short sentences. Easy to scan.
  • One main idea per post — don't try to say everything
  • Use numbers when possible ("3 lessons", "saved 18 hours", "$2,450 revenue")
  • Be specific — vague posts get ignored
  • No corporate jargon
  • Write like a human, not a press release
  • Always add 3-5 hashtags at the end
  • Emoji are optional — use max 3 if you use them

Step 4 — Create Approval File

Create file at vault/Pending_Approval/LINKEDIN_[YYYYMMDD_HHMMSS].md:


type: approval_request action: linkedin_post created: [ISO timestamp] expires: [ISO timestamp + 48 hours] post_type: [achievement/insight/value/question/behind_the_scenes] status: pending


Post Content

[Full LinkedIn post text exactly as it should be published]

Why This Post

[1-2 sentences explaining what business goal this serves]

Best Time to Post

Weekdays 8-10am or 5-6pm for highest engagement. Current time: [current time] — [recommend posting now or scheduling]

To Approve

Move this file to vault/Approved/ folder. The LinkedIn watcher will publish it automatically.

To Edit

Edit the text under "## Post Content" above, then move to vault/Approved/.

To Reject

Move this file to vault/Rejected/ folder.

Step 5 — Log

Append to vault/Logs/[YYYY-MM-DD].md:

[timestamp] | linkedin_draft | [post_type] | approval_requested

Content Ideas Bank

If no specific trigger exists, check these sources for post ideas:

  • Recent completed tasks in vault/Done/ from past 7 days
  • Any achievements mentioned in vault/Briefings/
  • Business goals progress from vault/Business_Goals.md
  • Problems solved recently that others in your industry face
  • Tools or techniques discovered while building this AI Employee project

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.