agentleFS
kelgirechandrakant-cpukelgirechandrakant-cpu/vibe-coding-playbook/skills/linkedin-post/SKILL.md

linkedin-post

Skill4 starsChanged 3 months agoMITView on GitHub

Craft human-sounding, high-engagement LinkedIn posts for software projects, AI tools, and technical playbooks. Uses proven hook formulas, strips AI tells, and formats links in comments.

41 other projects use a version of this.

Adopted by

Most recently taken up by

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

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

  • ncklrsSkill

    proposal-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 AzureSkill

    lint

    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

  • OpenAISkill

    brainstorming

    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

  • GoogleSkill

    grill-me

    A relentless interview to sharpen a plan or design.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 36 edited versions we read keep these.

  • 2

    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
  1. Distinctive:

    Banned AI Vocabulary: Never use *delve, game-changer, unlock, leverage, landscape, realm, transformative, spearhead, in today's fast-paced …

    line 16
  2. Distinctive:

    Line Length: Keep sentences under 15 words.

    line 17

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

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

LinkedIn Post Generator — Developer & Founder Marketing Skill

This skill crafts human-sounding, high-converting LinkedIn posts for developer tools, SaaS applications, and AI coding playbooks.

Whenever asked to "write a linkedin post", "make a linkedin post about X", or "generate a post for linkedin", follow this protocol strictly.


1. Golden Rules of LinkedIn Voice (Strict Anti-Slop)

  • Banned AI Vocabulary: Never use delve, game-changer, unlock, leverage, landscape, realm, transformative, spearhead, in today's fast-paced world, testament to, foster, crucial role, exciting news, thrilled to announce.
  • Line Length: Keep sentences under 15 words. Keep paragraphs to 1–2 lines maximum. White space drives readability.
  • Tone: Builder talking to builders, founders, or engineers. Direct, technical, authentic, slightly opinionated.
  • Hook Rules: The first 2 lines must stop the scroll before the "...see more" fold. Never start with generic greetings ("Hey connection network!" or "I am excited to share...").
  • Link Placement Rule: Never put URLs in the main post text. LinkedIn penalizes reach for outbound links in post bodies. Always place the link in the "💬 Link in first comment" section.

2. Structural Hook Formulas

Formula 1: The False Binary Dissolve

"Everyone thinks you have to choose between [Option A] and [Option B].
After [building X / handling 10k users], we realized both approaches are broken.
Here is the 3rd way we built [Feature/Project]:"

Formula 2: The Scarce-Shots Math

"90% of [Target Audience] make the same critical mistake with [Topic].
It cost us [X hours / 504 timeouts] before we figured out the fix.
Here is the exact breakdown:"

Formula 3: Controlled A/B Anecdote

"We let AI write [Feature A] without constraints. It broke in 3 days.
Then we forced the AI to follow [Architectural Pattern B].
The result? Zero export bugs across 25+ themes."


3. Post Output Template Format

### 📱 LinkedIn Post Draft

[HOOK - First 2 lines]

[BODY - Short 1-2 line paragraphs with whitespace]

[CORE TAKEAWAY / BULLET POINTS]
- Point 1
- Point 2
- Point 3

[CALL TO ACTION - Directing to first comment]

---
### 💬 First Comment (Put the Link Here)
[Link + short comment callout]

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.