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.
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.
$ npx skills add borghei/Claude-Skills --skill linkedin-post-writer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install borghei/Claude-Skills linkedin-post-writer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "linkedin-post-writer" agent skill from https://github.com/borghei/Claude-Skills/tree/main/tools/linkedin/linkedin-post-writer into .claude/skills/linkedin-post-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-post-writer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/borghei/Claude-Skills/tree/main/tools/linkedin/linkedin-post-writerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add borghei/Claude-Skills --skill linkedin-post-writer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install borghei/Claude-Skills linkedin-post-writer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/tools/linkedin/linkedin-post-writer .agents/skills/linkedin-post-writer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "linkedin-post-writer" agent skill from https://github.com/borghei/Claude-Skills/tree/main/tools/linkedin/linkedin-post-writer into .agents/skills/linkedin-post-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-post-writer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill linkedin-post-writer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install borghei/Claude-Skills linkedin-post-writer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/tools/linkedin/linkedin-post-writer .cursor/skills/linkedin-post-writer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "linkedin-post-writer" agent skill from https://github.com/borghei/Claude-Skills/tree/main/tools/linkedin/linkedin-post-writer into .cursor/skills/linkedin-post-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-post-writer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/borghei/Claude-Skills.git --path tools/linkedin/linkedin-post-writer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add borghei/Claude-Skills --skill linkedin-post-writer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install borghei/Claude-Skills linkedin-post-writer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/tools/linkedin/linkedin-post-writer .gemini/skills/linkedin-post-writer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "linkedin-post-writer" agent skill from https://github.com/borghei/Claude-Skills/tree/main/tools/linkedin/linkedin-post-writer into .gemini/skills/linkedin-post-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-post-writer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install borghei/Claude-Skills linkedin-post-writerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add borghei/Claude-Skills --skill linkedin-post-writer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/tools/linkedin/linkedin-post-writer .github/skills/linkedin-post-writer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "linkedin-post-writer" agent skill from https://github.com/borghei/Claude-Skills/tree/main/tools/linkedin/linkedin-post-writer into .github/skills/linkedin-post-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-post-writer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill linkedin-post-writer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install borghei/Claude-Skills linkedin-post-writer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/tools/linkedin/linkedin-post-writer .opencode/skills/linkedin-post-writer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "linkedin-post-writer" agent skill from https://github.com/borghei/Claude-Skills/tree/main/tools/linkedin/linkedin-post-writer into .opencode/skills/linkedin-post-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-post-writer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
linkedin-post-writerDrafts 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. 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.
4 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 4a698e8. It shows what the files ask for, not the result of running them.
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.
Ships 2 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python3From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
The full file from borghei/Claude-Skills at commit 4a698e8, republished under its MIT licence (© borghei). 2,179 words, ~3,784 tokens.
.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.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.
assets/post_brief_template.md)Before drafting, confirm these inputs. If any is unknown or vague, ASK — do not assume:
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.
Quick start: fill in the brief, run the picker, draft from the first option, run the gate.
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.caution lines. A counter-position or a prediction with no
evidence behind it is an opinion; get the evidence or choose another pattern.python3 tools/linkedin/linkedin-post-writer/scripts/angle_picker.py \
--input tools/linkedin/linkedin-post-writer/assets/sample_brief.json --top 3references/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.references/post-structures.md).
One beat per paragraph, each anchored to a fact. Cut any beat the author has
no fact for.python3 tools/linkedin/linkedin-post-writer/scripts/angle_picker.py \
--input tools/linkedin/linkedin-post-writer/assets/sample_brief.json \
--top 5 --format jsonreferences/pre-publish-gate.md §4. The tool
cannot do this part.linkedin-humanizer.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.txtThe first sample fails with two blockers and three warnings. The revised version of the same post passes clean.
The pattern is chosen by what the author has, then ranked by goal. Goal-fit scores are editorial heuristics, not measurements.
| The author has… | Pattern | Strongest for |
|---|---|---|
| One precise figure | Receipt line | Saves, inbound |
| A date and something that went wrong | Dated mistake | Conversation |
| A moment they were present for | Cold scene | Conversation, reshares |
| A belief they dropped | Changed mind | Conversation |
| A disagreement with common practice, plus evidence | Counter-position | Conversation, reshares |
| A before and an after | Measured gap | Saves, inbound |
| Someone's exact words | Borrowed line | Conversation |
| A rule they keep | House rule | Saves |
| A count of things examined | Field count | Saves, reshares, inbound |
| A question they keep being asked | Reported question | Conversation |
| A person who did a specific thing | Named credit | Reshares |
| A term their audience misuses | Plain definition | Saves |
| An expectation with a date on it | Dated bet | Conversation, reshares |
| Three or more real steps | Counted list | Saves |
| Decision | Recommendation | Why |
|---|---|---|
| Start from topic or from material | [PROVEN] Material. If there is none, ask for it before drafting | A post is as specific as its least specific input |
| Opening: statement or question | [RECOMMENDED] Statement. Put a real question at the close | A question in line one asks for attention before giving a reason |
| Where the key fact goes | [PROVEN] In the first clause of the first line | The 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 post | Two ideas halve the space for evidence on each |
| Length | [RECOMMENDED] As long as the facts last: usually 600 to 1,400 characters | Past the facts, length is restatement |
| Include what failed | [RECOMMENDED] Yes, with the same precision as what worked | It is what separates a report from a promotion |
| Hashtags | [RECOMMENDED] None to three, on the last line | They are labels, not content |
| A link in the body | [EXPERIMENTAL] Put it in the first comment unless the link is the point | Widely practised, effect unverified; the gate warns and --allow-links overrides |
| Mentioning the author's product | [RECOMMENDED] Once, where the story reaches it | Earlier, the post becomes an advert |
| Setting | Default | Status |
|---|---|---|
| Post character limit | 3,000 | Current as of writing; verify in the product |
| Characters visible before truncation | 140 | Conservative mobile estimate as of writing; desktop shows more. Override with --fold-chars |
| Markdown rendering | None | As of writing, asterisks and pound signs display literally |
These change without notice. Treat them as configuration, not knowledge.
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.
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.
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.
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.
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.
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.
Tools overview and reference documentation for this skill:
| File | Purpose |
|---|---|
scripts/angle_picker.py | Ranks 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.py | Pre-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.md | The 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.md | Body 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.md | Every 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.json | A filled brief for a fictional COO writing about cancelling a weekly all-hands |
assets/sample_draft.txt | First 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.txt | The same post after revision; passes the gate |
assets/post_brief_template.md | Fill-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
SKILL.md and 9 other files (scripts, references, assets) in tools/linkedin/linkedin-post-writer of borghei/Claude-Skills.
Open the folder on GitHubat commit 4a698e8
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Linkedin Post Writer this skillborghei/Claude-Skills | 881 | — | ~3.8k | Automated safety check: Pass | MIT | |
| Socialcoreyhaines31/marketingskills | 54k | 4 repos | ~4.5k | Automated safety check: Pass | MIT | |
| Social Contentfreekmurze/dotfiles | 1k | 23 repos | ~2.1k | Automated safety check: Pass | None | |
| Linkedin Marketingsergebulaev/linkedin-skills | 4.3k | 1 repos | ~3.2k | Automated safety check: Notes | MIT | |
| Typefullyfreekmurze/dotfiles | 1k | 2 repos | ~3.4k | Automated safety check: Notes | None | |
| Linkedin Content Plannersergebulaev/linkedin-skills | 4.3k | 1 repos | ~2.1k | Automated safety check: Pass | MIT |
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.
freekmurze/dotfiles
When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms.
sergebulaev/linkedin-skills
Plan, draft, audit, and publish LinkedIn posts and comments.
freekmurze/dotfiles
Create, schedule, and manage social media posts via Typefully.
sergebulaev/linkedin-skills
Generate a 7-day LinkedIn content plan from a theme, audience, and pillars.
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.
borghei/Claude-Skills
Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.
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.
borghei/Claude-Skills
Idea to AI-generated prototype to customer validation to engineering handoff.
borghei/Claude-Skills
Analytics engineering across data modeling, dbt, transformation, and semantic layers.
borghei/Claude-Skills
Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.
borghei/Claude-Skills
OKR brainstorming and validation using the Radical Focus framework — outcome objectives, measurable key results, counter-metrics.
Works with
Categories
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.
Linkedin Post Writer fits situations like: choosing a hook; checking a draft before publishing.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.