Agent skill

Linkedin Post Writer

by borghei in borghei/Claude-Skills

Drafts LinkedIn posts from a brief: picks an angle and opening pattern the author's real material supports, structures the body, and gates the draft before it is pasted.

MITAuto-check passedWriting & Content

Install Linkedin Post Writer

skills CLI
$ npx skills add borghei/Claude-Skills --skill linkedin-post-writer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install borghei/Claude-Skills linkedin-post-writer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/tools/linkedin/linkedin-post-writer .claude/skills/linkedin-post-writer && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
linkedin-post-writer
GitHub stars
881
Token cost
~3.8k tokens
SKILL.md length
2,179 words
Files
10 (incl. scripts, references, assets)
Skills in repo
349
Repo updated
First seen
Licence
MIT

At a glance

Drafts LinkedIn posts from a brief: picks an angle and opening pattern the author's real material supports, structures the body, and gates the draft before it is pasted.

  • Works in 4 steps: Fill in assets/post_brief_template.md… → Run the picker. It ranks only the… → Read any caution lines. A… → …
  • Choosing a hook
  • SKILL.md covers When to use this skill, Inputs the skill expects, Clarify First and Workflows, plus 3 more sections
  • Runs Python scripts from its folder; calls python3

What it does

Linkedin Post Writer is an agent skill from borghei/Claude-Skills. Drafts LinkedIn posts from a brief: picks an angle and opening pattern the author's real material supports, structures the body, and gates the draft before it is pasted. Use when writing a post, choosing a hook, or checking a draft before publishing.

Its SKILL.md is about 3.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 12 other files, including scripts, reference files and assets (for example `assets/post_brief_template.md`, `assets/sample_brief.json` and `references/opening-patterns.md`).

It sits in Writing & Content, covering Social media posts. It works with LinkedIn. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.

When your agent uses it

  • Choosing a hook
  • Checking a draft before publishing

Example prompts

  • “Use the linkedin-post-writer skill to draft LinkedIn posts from a brief: picks an angle and opening pattern the author's real material supports…”
  • “/linkedin-post-writer”

Requirements

  • Python 3

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Fill in assets/post_brief_template.md with the author, or convert their
  2. Run the picker. It ranks only the patterns the material supports and lists
  3. Read any caution lines. A counter-position or a prediction with no
  4. Offer the author the top two or three options in one line each. Let them

What it can do on your machine

Read from SKILL.md and the folder at commit 4a698e8. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 2 files in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python3

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Linkedin Post Writer loads about 3.8k tokens when it runs, and up to ~13k if it reads all its reference files. Until then it costs about 68 tokens; SKILL.md has 2,179 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~68
When it runs · the whole SKILL.md, loaded when a task matches
~3.8k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~13k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from borghei/Claude-Skills at commit 4a698e8, republished under its MIT licence (© borghei). 2,179 words, ~3,784 tokens.

Download SKILL.mdSave it as .claude/skills/linkedin-post-writer/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.
name
linkedin-post-writer
description
Drafts LinkedIn posts from a brief: picks an angle and opening pattern the author's real material supports, structures the body, and gates the draft before it is pasted. Use when writing a post, choosing a hook, or checking a draft before publishing.
license
MIT + Commons Clause
metadata.version
1.0.0
metadata.author
borghei
metadata.category
tools
metadata.domain
linkedin
metadata.updated
2026-10-07
metadata.tags
linkedin, copywriting, hooks, content-drafting, pre-publish

LinkedIn Post Writer

Most weak posts are decided before the first word is written. The author starts from a topic ("something about onboarding") instead of from material (a number, a date, a thing a customer said), so the draft has to be built from generalities, and generalities all sound alike. The opening is then chosen for how it sounds, a format is borrowed from a post that did well for someone else, and the result is a confident paragraph about nothing in particular with a question bolted to the end.

This skill reverses the order. It starts with an inventory of what the author really has, lets that inventory decide which of fourteen opening patterns are available, builds the body from beats that each need a fact, and runs a mechanical gate before the text leaves the editor. Patterns the author lacks the material for are not offered; instead the skill says which single question would unlock them.

Scope boundary. This skill drafts a single feed post and checks it. It does not run the full machine-tell audit, score emoji, or build a voice fingerprint; hand the draft to linkedin-humanizer for that. It does not study other people's posts to extract their openings; that is linkedin-hook-analyzer. Drawing a story out of an author who "has nothing to say" is linkedin-story-interviewer; turning an article, talk or thread into posts is linkedin-content-repurposer; deciding what to post this month is linkedin-content-planner. Comments and replies (linkedin-comment-writer, linkedin-reply-manager, linkedin-thread-tracker), profile copy (linkedin-profile-optimizer), team programmes (linkedin-employee-advocacy) and performance review (linkedin-engagement-analytics) are separate skills. Everything here is offline: the skill produces text for the user to paste into LinkedIn themselves. It does not post, schedule, fetch, or call any service.

When to use this skill

  • Someone asks for a LinkedIn post and has a topic but no angle
  • A draft exists and the opening is not working
  • An author has one good fact (a result, a mistake, a quote) and wants the post built around it
  • A ghostwriter needs a repeatable way to brief, draft and check posts for several authors
  • A draft is finished and needs a last mechanical check before it is pasted
  • The same author keeps producing the same shape of post and wants a different one

Inputs the skill expects

  • A brief: topic, one goal, the audience in a sentence (assets/post_brief_template.md)
  • The author's material: any of a figure, a dated event, a scene, a changed belief, an opposing view, a before-and-after, a quote, a rule, a sample count, a question they were asked, a person to credit, a term to explain, a prediction, a list of steps
  • Constraints: what must be included, what must not be named, preferred length
  • Optional: a voice profile or two past posts, so the draft is in the author's register

Clarify First

Before drafting, confirm these inputs. If any is unknown or vague, ASK — do not assume:

  • The one goal (conversation, saves, reshares, or inbound interest) — it changes which pattern ranks first and what the last line asks for; a post that tries for all four gets none
  • What the author actually has — at least one concrete item of material; without it every pattern is locked and the only honest output is a question back to the author
  • Who it is for — the same fact is written differently for peers, buyers and candidates; "everyone" produces a post for no one
  • What cannot be said — client names, unreleased figures, people who have not agreed to be named; these decide whether a quote or a number can be used at all

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," use the material in the request as given, pick the top-ranked pattern, and list the assumed goal and audience at the top of the reply. If there is no material at all, ask the single unlock question for the pattern that best fits the topic; do not invent a figure to get started.

Workflows

Quick start: fill in the brief, run the picker, draft from the first option, run the gate.

Workflow 1 — From brief to angle
  1. Fill in assets/post_brief_template.md with the author, or convert their notes into the JSON shape in assets/sample_brief.json. Leave a material field empty if the author does not have it.
  2. Run the picker. It ranks only the patterns the material supports and lists the rest as locked, each with the question that would unlock it.
  3. Read any caution lines. A counter-position or a prediction with no evidence behind it is an opinion; get the evidence or choose another pattern.
  4. Offer the author the top two or three options in one line each. Let them choose; they know which one they are comfortable publishing.
bash
python3 tools/linkedin/linkedin-post-writer/scripts/angle_picker.py \
  --input tools/linkedin/linkedin-post-writer/assets/sample_brief.json --top 3
Workflow 2 — Draft the post
  1. Write the opening from the chosen pattern in references/opening-patterns.md. The agent writes it from the author's material and nothing else; the point of the line must land inside the first clause.
  2. Write the second line so it works if the first is all the reader sees before expanding: add the stake, do not restate.
  3. Build the body from the pattern's beats (references/post-structures.md). One beat per paragraph, each anchored to a fact. Cut any beat the author has no fact for.
  4. Include the part that did not work. A post with no cost, exception or open question reads as an advertisement.
  5. Close according to the goal: a question only a practitioner could answer, the last fact, or nothing. Never a stock ask.
  6. Draft two alternative openings from the second-ranked pattern so the author has a real choice.
bash
python3 tools/linkedin/linkedin-post-writer/scripts/angle_picker.py \
  --input tools/linkedin/linkedin-post-writer/assets/sample_brief.json \
  --top 5 --format json
Workflow 3 — Gate the draft before it is pasted
  1. Save the draft as plain text with the line breaks it will have in the feed.
  2. Run the gate. Blockers fail it outright; more than three warnings fail it.
  3. Fix blockers first: a leftover placeholder or a stock closing line is never acceptable. Then work the warnings in the order shown.
  4. Verify that every figure, name and quote in the draft appears in the brief, using the manual checklist in references/pre-publish-gate.md §4. The tool cannot do this part.
  5. Re-run until the exit code is 0, then hand over the text with its character count. For a full style audit, pass the result to linkedin-humanizer.
bash
python3 tools/linkedin/linkedin-post-writer/scripts/post_gate.py \
  --input tools/linkedin/linkedin-post-writer/assets/sample_draft.txt

python3 tools/linkedin/linkedin-post-writer/scripts/post_gate.py \
  --input tools/linkedin/linkedin-post-writer/assets/sample_draft_revised.txt

The first sample fails with two blockers and three warnings. The revised version of the same post passes clean.

Decision frameworks

Pattern by material

The pattern is chosen by what the author has, then ranked by goal. Goal-fit scores are editorial heuristics, not measurements.

The author has…PatternStrongest for
One precise figureReceipt lineSaves, inbound
A date and something that went wrongDated mistakeConversation
A moment they were present forCold sceneConversation, reshares
A belief they droppedChanged mindConversation
A disagreement with common practice, plus evidenceCounter-positionConversation, reshares
A before and an afterMeasured gapSaves, inbound
Someone's exact wordsBorrowed lineConversation
A rule they keepHouse ruleSaves
A count of things examinedField countSaves, reshares, inbound
A question they keep being askedReported questionConversation
A person who did a specific thingNamed creditReshares
A term their audience misusesPlain definitionSaves
An expectation with a date on itDated betConversation, reshares
Three or more real stepsCounted listSaves
Show full SKILL.md (951 more words)Show less
Choices that come up in every draft
DecisionRecommendationWhy
Start from topic or from material[PROVEN] Material. If there is none, ask for it before draftingA post is as specific as its least specific input
Opening: statement or question[RECOMMENDED] Statement. Put a real question at the closeA question in line one asks for attention before giving a reason
Where the key fact goes[PROVEN] In the first clause of the first lineThe feed truncates the opening; anything after the cut is seen only by people already interested
How many ideas[PROVEN] One. Park the second in a note for the next postTwo ideas halve the space for evidence on each
Length[RECOMMENDED] As long as the facts last: usually 600 to 1,400 charactersPast the facts, length is restatement
Include what failed[RECOMMENDED] Yes, with the same precision as what workedIt is what separates a report from a promotion
Hashtags[RECOMMENDED] None to three, on the last lineThey are labels, not content
A link in the body[EXPERIMENTAL] Put it in the first comment unless the link is the pointWidely practised, effect unverified; the gate warns and --allow-links overrides
Mentioning the author's product[RECOMMENDED] Once, where the story reaches itEarlier, the post becomes an advert
Platform mechanics the gate assumes
SettingDefaultStatus
Post character limit3,000Current as of writing; verify in the product
Characters visible before truncation140Conservative mobile estimate as of writing; desktop shows more. Override with --fold-chars
Markdown renderingNoneAs of writing, asterisks and pound signs display literally

These change without notice. Treat them as configuration, not knowledge.

Anti-Patterns

Writing the opening first and looking for a post to fit it

Mistake: The author has a line they like ("Nobody talks about the real cost of meetings") and builds four paragraphs to justify it. Why it happens: A good-sounding line arrives easily and feels like progress. The material that would support it takes effort to dig out. Instead: Fill in the brief first. angle_picker.py will show that the line is a teaser with nothing behind it, and that the author's real asset is, say, "62 person-hours every Monday", which opens the post on its own.

Borrowing a format without the material it needs

Mistake: A measured-gap post did well for someone else, so the author writes "We went from struggling to thriving in six months" with no figures. Why it happens: The format is visible and the measurements behind it are not. Instead: Treat every pattern's needs as a hard requirement. A gap needs two numbers measured the same way and a time span. If the author has one number, it is a receipt line; if none, the pattern is locked and the picker says what to ask.

Trying for every goal at once

Mistake: The post tells a story, lists seven tips, thanks the team, and ends by inviting people to book a call. Why it happens: Each addition seems free, and each stakeholder has a request. Instead: One goal per post, chosen in the brief. The goal sets the pattern ranking and the close. Everything else goes in a note for the next post; linkedin-content-planner is the place to schedule them.

Leaving out what went wrong

Mistake: Every paragraph reports success. The fortnight where two teams shipped conflicting changes is cut "to keep it positive". Why it happens: The author is writing under their employer's name and caution feels safe. Instead: Keep one cost, exception or unsolved part, stated as precisely as the wins. Compare the two sample drafts: the revised one opens on the mistake, and it is the more credible post.

Closing with a generic ask

Mistake: "What do you think?" or "Agree?" as the last line. Why it happens: The author has been told to end on a question and has no specific one. Instead: Ask something that can only be answered from experience ("what broke in the first two weeks?") or end on the last fact. post_gate.py blocks the stock wordings outright.

Passing the gate and skipping the read-through

Mistake: Exit code 0, so the draft is pasted. Why it happens: A green check feels like approval. Instead: The gate checks mechanics. It cannot tell whether the figure is right, whether Ines agreed to be quoted, or whether the post is interesting. Check every fact against the brief and have the author read the text aloud once.

Files

Tools overview and reference documentation for this skill:

FilePurpose
scripts/angle_picker.pyRanks the fourteen opening patterns by the material in a brief and the stated goal; prints the opening skeleton, body beats and close for each, and the unlock question for every pattern the brief cannot support
scripts/post_gate.pyPre-paste gate with fifteen checks: opening fit and phrasing, length, placeholders and markup, paragraph density, hashtags, links, specificity, habit spot-check, closing line; exits 1 on any blocker or excess warnings
references/opening-patterns.mdThe fourteen patterns: what each needs, how to build it, an original example, the usual way it goes wrong, and four opening types to avoid
references/post-structures.mdBody beats per pattern, the second line, closes by goal, length bands, layout, and a full worked draft from the sample brief
references/pre-publish-gate.mdEvery gate check with its level and rationale, platform mechanics and their caveats, the manual checks the tool cannot do, and how to tune thresholds
assets/sample_brief.jsonA filled brief for a fictional COO writing about cancelling a weekly all-hands
assets/sample_draft.txtFirst draft from that brief; fails the gate on a placeholder, a stock closer, a long opening, a dense paragraph and six hashtags
assets/sample_draft_revised.txtThe same post after revision; passes the gate
assets/post_brief_template.mdFill-in brief covering goal, audience, material inventory, constraints and sign-off

© borghei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 9 other files (scripts, references, assets) in tools/linkedin/linkedin-post-writer of borghei/Claude-Skills.

  • SKILL.md
  • assets/post_brief_template.md
  • assets/sample_brief.json
  • assets/sample_draft.txt
  • assets/sample_draft_revised.txt
  • references/opening-patterns.md
  • references/post-structures.md
  • references/pre-publish-gate.md
  • scripts/angle_picker.py
  • scripts/post_gate.py

Open the folder on GitHubat commit 4a698e8

Compare with similar skills

Linkedin Post Writer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Linkedin Post Writer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Linkedin Post Writer this skillborghei/Claude-Skills881—~3.8kAutomated safety check: PassMIT
Socialcoreyhaines31/marketingskills54k4 repos~4.5kAutomated safety check: PassMIT
Social Contentfreekmurze/dotfiles1k23 repos~2.1kAutomated safety check: PassNone
Linkedin Marketingsergebulaev/linkedin-skills4.3k1 repos~3.2kAutomated safety check: NotesMIT
Typefullyfreekmurze/dotfiles1k2 repos~3.4kAutomated safety check: NotesNone
Linkedin Content Plannersergebulaev/linkedin-skills4.3k1 repos~2.1kAutomated safety check: PassMIT

Similar skills

  • Social

    coreyhaines31/marketingskills

    When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, or Facebook, or wants to do social listening and engagement triage.

    54k GitHub starsUsed in 4 repos~4.5k tokens
    Writing & ContentAuto-check passed
  • Social Content

    freekmurze/dotfiles

    When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms.

    1k GitHub starsUsed in 23 repos~2.1k tokens
    Writing & ContentAuto-check passed
  • Linkedin Marketing

    sergebulaev/linkedin-skills

    Plan, draft, audit, and publish LinkedIn posts and comments.

    4.3k GitHub starsUsed in 1 repo~3.2k tokens
    Writing & ContentAuto-check: notes
  • Typefully

    freekmurze/dotfiles

    Create, schedule, and manage social media posts via Typefully.

    1k GitHub starsUsed in 2 repos~3.4k tokens
    Writing & ContentAuto-check: notes
  • Linkedin Content Planner

    sergebulaev/linkedin-skills

    Generate a 7-day LinkedIn content plan from a theme, audience, and pillars.

    4.3k GitHub starsUsed in 1 repo~2.1k tokens
    Writing & ContentAuto-check passed
  • Changelog Social Recap

    FlorianBruniaux/claude-code-ultimate-guide

    Turns CHANGELOG.md entries for a release or a week into LinkedIn, Twitter/X, newsletter and Slack posts in French and English.

    6.1k GitHub stars~1.8k tokensUpdated today
    Writing & ContentAuto-check: notes

More from borghei/Claude-Skills

All 349 skills in this repo
  • Agents In The Team

    borghei/Claude-Skills

    Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.

    881 GitHub stars~4.2k tokensUpdated today
    Auto-check passed
  • AI Content Disclosure

    borghei/Claude-Skills

    Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.

    881 GitHub stars~3.4k tokensUpdated today
    Auto-check passed
  • AI Prototyping

    borghei/Claude-Skills

    Idea to AI-generated prototype to customer validation to engineering handoff.

    881 GitHub stars~3.6k tokensUpdated today
    Auto-check passed
  • Analytics Engineer

    borghei/Claude-Skills

    Analytics engineering across data modeling, dbt, transformation, and semantic layers.

    881 GitHub stars~3.4k tokensUpdated today
    Auto-check passed
  • Ansoff Matrix

    borghei/Claude-Skills

    Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.

    881 GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • Brainstorm Okrs

    borghei/Claude-Skills

    OKR brainstorming and validation using the Radical Focus framework — outcome objectives, measurable key results, counter-metrics.

    881 GitHub stars~1.4k tokensUpdated today
    Auto-check passed

Works with

Questions about Linkedin Post Writer

What does Linkedin Post Writer do?

Drafts LinkedIn posts from a brief: picks an angle and opening pattern the author's real material supports, structures the body, and gates the draft before it is pasted. Linkedin Post Writer is an agent skill from borghei/Claude-Skills. Drafts LinkedIn posts from a brief: picks an angle and opening pattern the author's real material supports, structures the body, and gates the draft before it is pasted.

When should I use Linkedin Post Writer?

Linkedin Post Writer fits situations like: choosing a hook; checking a draft before publishing.

How do I install Linkedin Post Writer in Claude Code?

Run `npx skills add borghei/Claude-Skills --skill linkedin-post-writer -a claude-code`. Or copy the skill folder (tools/linkedin/linkedin-post-writer in borghei/Claude-Skills) into .claude/skills/linkedin-post-writer in your project. Claude Code loads it when a task matches its description.

How do I install Linkedin Post Writer in Codex?

Run `npx skills add borghei/Claude-Skills --skill linkedin-post-writer -a codex`. Or copy the skill folder (tools/linkedin/linkedin-post-writer in borghei/Claude-Skills) into .agents/skills/linkedin-post-writer in your project. Codex loads it when a task matches its description.

Can I use Linkedin Post Writer in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add borghei/Claude-Skills --skill linkedin-post-writer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/linkedin-post-writer, .gemini/skills/linkedin-post-writer, .github/skills/linkedin-post-writer and .opencode/skills/linkedin-post-writer in your project.

What does Linkedin Post Writer need to run?

Going by SKILL.md and its folder, Linkedin Post Writer needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3.

Does Linkedin Post Writer access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Linkedin Post Writer safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Linkedin Post Writer use?

Linkedin Post Writer is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Linkedin Post Writer use?

About 3.8k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 8.8k tokens, read only when the agent opens those files.

What are the alternatives to Linkedin Post Writer?

Skills that share tags, products or a category with Linkedin Post Writer: Social (coreyhaines31/marketingskills, 54k stars), Social Content (freekmurze/dotfiles, 1k stars), Linkedin Marketing (sergebulaev/linkedin-skills, 4.3k stars) and Typefully (freekmurze/dotfiles, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Linkedin Post Writer?

borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 881 GitHub stars. The repository holds 349 skills in this directory. The repository was last updated on October 7, 2026.

Source: borghei/Claude-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.