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.
A skill your agent uses when someone wants to grow reach through comments, replies, groups, or outreach on LinkedIn — a commenting roster, a connection request note, a DM or InMail, a networking…
MITAuto-check passed
Install Linkedin Engagement
$ npx skills add alirezarezvani/claude-skills --skill linkedin-engagement -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install alirezarezvani/claude-skills linkedin-engagement --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/alirezarezvani/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/marketing/linkedin/skills/linkedin-engagement .claude/skills/linkedin-engagement && 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-engagement" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/marketing/linkedin/skills/linkedin-engagement into .claude/skills/linkedin-engagement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-engagement", 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/alirezarezvani/claude-skills/tree/main/marketing/linkedin/skills/linkedin-engagementType 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 alirezarezvani/claude-skills --skill linkedin-engagement -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install alirezarezvani/claude-skills linkedin-engagement --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/marketing/linkedin/skills/linkedin-engagement .agents/skills/linkedin-engagement && 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-engagement" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/marketing/linkedin/skills/linkedin-engagement into .agents/skills/linkedin-engagement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-engagement", 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 alirezarezvani/claude-skills --skill linkedin-engagement -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install alirezarezvani/claude-skills linkedin-engagement --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/marketing/linkedin/skills/linkedin-engagement .cursor/skills/linkedin-engagement && 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-engagement" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/marketing/linkedin/skills/linkedin-engagement into .cursor/skills/linkedin-engagement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-engagement", 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/alirezarezvani/claude-skills.git --path marketing/linkedin/skills/linkedin-engagement--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 alirezarezvani/claude-skills --skill linkedin-engagement -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install alirezarezvani/claude-skills linkedin-engagement --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/marketing/linkedin/skills/linkedin-engagement .gemini/skills/linkedin-engagement && 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-engagement" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/marketing/linkedin/skills/linkedin-engagement into .gemini/skills/linkedin-engagement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-engagement", 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 alirezarezvani/claude-skills linkedin-engagementInstalls 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 alirezarezvani/claude-skills --skill linkedin-engagement -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/marketing/linkedin/skills/linkedin-engagement .github/skills/linkedin-engagement && 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-engagement" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/marketing/linkedin/skills/linkedin-engagement into .github/skills/linkedin-engagement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-engagement", 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 alirezarezvani/claude-skills --skill linkedin-engagement -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install alirezarezvani/claude-skills linkedin-engagement --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/marketing/linkedin/skills/linkedin-engagement .opencode/skills/linkedin-engagement && 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-engagement" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/marketing/linkedin/skills/linkedin-engagement into .opencode/skills/linkedin-engagement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-engagement", 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.
Facts
- Skill name
linkedin-engagement- GitHub stars
- 28k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 553 words
- Files
- 8 (incl. scripts, references, assets)
- Skills in repo
- 342
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when someone wants to grow reach through comments, replies, groups, or outreach on LinkedIn — a commenting roster, a connection request note, a DM or InMail, a networking…
- Someone wants to grow reach through comments
- SKILL.md covers Workflow, Rules, Scripts and References and assets, plus 1 more section
- Runs Python scripts from its folder; calls python3
- Outreach on LinkedIn — a commenting roster
What it does
Linkedin Engagement is an agent skill from alirezarezvani/claude-skills. Use when someone wants to grow reach through comments, replies, groups, or outreach on LinkedIn — a commenting roster, a connection request note, a DM or InMail, a networking plan, or a check on whether their outreach volume is safe. Triggers on "who should I engage with", "write a connection request", "cold DM", "LinkedIn outreach", "networking strategy", "how many invites can I send". Builds a weekly comment roster inside a real time budget, assembles one message at a time and refuses templates, and caps volume…
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including scripts, reference files and assets (for example `assets/example_outreach.json`, `assets/outreach_worksheet.md` and `references/comment_strategy.md`).
It works with LinkedIn. The repository describes itself as: 380 Claude Code skills & agent skills & plugins (30+ Agents, 70+ custom commands, 380+ skills, customizable references, scripts)for Claude Code, Codex, Gemini CLI, Cursor, and 8… The licence is MIT.
When your agent uses it
- Someone wants to grow reach through comments
- Outreach on LinkedIn — a commenting roster
- A connection request note
- A networking plan
Example prompts
- “who should I engage with”
- “write a connection request”
- “cold DM”
- “/linkedin-engagement”
Requirements
- Python 3
What it can do on your machine
Read from SKILL.md and the folder at commit 19392f7. 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 3 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 Engagement loads about 1.3k tokens when it runs, and up to ~4.7k if it reads all its reference files. Until then it costs about 147 tokens; SKILL.md has 553 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.
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 alirezarezvani/claude-skills at commit 19392f7, republished under its MIT licence (© alirezarezvani). 553 words, ~1,347 tokens.
Download SKILL.mdSave it as
.claude/skills/linkedin-engagement/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.- name
- linkedin-engagement
- description
- Use when someone wants to grow reach through comments, replies, groups, or outreach on LinkedIn — a commenting roster, a connection request note, a DM or InMail, a networking plan, or a check on whether their outreach volume is safe. Triggers on "who should I engage with", "write a connection request", "cold DM", "LinkedIn outreach", "networking strategy", "how many invites can I send". Builds a weekly comment roster inside a real time budget, assembles one message at a time and refuses templates, and caps volume against LinkedIn's limits. Nothing is ever sent.
- license
- MIT
- metadata.version
- 1.0.0
- metadata.author
- Alireza Rezvani
- metadata.category
- marketing
- metadata.updated
- 2026-08-25
LinkedIn Engagement — comments first, outreach second
From a standing start your posts reach almost nobody, and publishing harder does not fix it. A substantive comment on a post that already has an audience puts your name, headline, and a paragraph of thinking in front of people already reading about your subject, for six minutes of work — the cheapest distribution on the platform, and the most badly used.
Nothing here sends anything — no credentials, no API calls. Automated connecting, messaging, commenting, liking, and sharing are prohibited by User Agreement §8.2.
Workflow
1. Build the comment roster. Name 8-12 accounts they would read anyway, with audience overlap and rough size tier, then:
python3 scripts/comment_target_planner.py --account "Priya Raman:5:4:larger" \
--account "Tomas Lind:5:3:peer" --minutes-per-day 18 --output humanTiers are huge (10x+, crowded), larger (2-10x, the best ratio), peer (~1x, where
reciprocity compounds), smaller (goodwill). The roster caps any account at twice a week —
commenting daily on one person reads as following them around — and keeps the huge tier under
half of any day. It builds the roster, never the comments: a generated comment is exactly
what §8.2 names, and it is recognisable anyway.
2. Outreach — check the volume before writing anything.
python3 scripts/outreach_volume_guard.py --invites 20 --pending 5 --minutes 120 \
--acceptance 0.42 --output humanExit 0 safe / 2 tight / 3 over a cap or the time budget / 4 refused above 40 invitations a day, because nobody reads that many profiles and writes that many specific lines. Pending invitations count against the weekly limit (observed around 100), and acceptance below 20% is a stop signal — it is the pattern LinkedIn reviews, and the targeting is wrong.
3. Write one message, for one person.
python3 scripts/outreach_message_builder.py --type connection \
--recipient "Priya" --specific-line "..." --reason "..." --output humanIt refuses without a person-specific line, refuses an ask in a first-touch connection note,
and enforces the 200-character cap (300 with --premium). In large third-party samples a
note barely moves acceptance (~26.4% either way) but roughly doubles the post-accept reply
rate: the note earns the conversation, not the meeting.
4. The order that works. Comment on their work for two weeks. Then invite, referencing something specific from that reading. Then, after acceptance and a pause, ask once, small.
Show full SKILL.md (223 more words)Show less
Rules
- Nothing is auto-sent. Ever. The user pastes and sends, one person at a time.
- No engagement pods. Coordinated reciprocal commenting is inauthentic engagement under §8.2 regardless of who pressed the key. Build a real reciprocity list instead.
- Every message carries a line that could only have been written for that person.
- Never paste the same comment twice. Identical comments at volume are the definition of the thing §8.2 prohibits.
- One follow-up, a week later, only with something new to say.
- Agreement is not a comment. Add the counter-example, the number, or the case where it breaks — or skip the slot.
Scripts
| Script | Role |
|---|---|
scripts/comment_target_planner.py | Weekly roster from scored accounts, inside a time budget, with per-account and per-tier caps. |
scripts/outreach_message_builder.py | Assembles one message; refuses templates, premature asks, and 14 dead phrases. |
scripts/outreach_volume_guard.py | Caps invitations against the observed weekly limit, pending backlog, acceptance floor, and the hours available. |
References and assets
references/comment_strategy.md— tiers, what a comment competes on, pods, replying to your own posts (7 sources)references/outreach_ethics_and_benchmarks.md— the benchmark numbers with their provenance, and the personalisation claim corrected (7 sources)assets/outreach_worksheet.md— fillable per-person prep sheetassets/example_outreach.json— input shape for the builder
Distinct from
linkedin-content— writes posts. A comment is a different craft on a different budget.marketing-skill/cold-email— email. Different channel, law, and caps.business-growth/,commercial/— sales process and deal economics, not networking.
Version: 1.0.0
© alirezarezvani, 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 7 other files (scripts, references, assets) in marketing/linkedin/skills/linkedin-engagement of alirezarezvani/claude-skills.
- SKILL.md
- assets/example_outreach.json
- assets/outreach_worksheet.md
- references/comment_strategy.md
- references/outreach_ethics_and_benchmarks.md
- scripts/comment_target_planner.py
- scripts/outreach_message_builder.py
- scripts/outreach_volume_guard.py
Open the folder on GitHubat commit 19392f7
Compare with similar skills
Linkedin Engagement 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 Engagement this skillalirezarezvani/claude-skills | 28k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Socialcoreyhaines31/marketingskills | 54k | 4 repos | ~4.5k | Automated safety check: Pass | MIT | |
| Banner Design Systemnextlevelbuilder/ui-ux-pro-max-skill | 134k | 1 repos | ~1.8k | Automated safety check: Pass | MIT | |
| Agent ReachPanniantong/Agent-Reach | 94k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Ad CreativeLeoYeAI/openclaw-marketing-skills | 1k | 8 repos | ~3.4k | Automated safety check: Pass | Custom licence | |
| Social Contentfreekmurze/dotfiles | 1k | 23 repos | ~2.1k | Automated safety check: Pass | None |
Similar skills
Banner Design System
nextlevelbuilder/ui-ux-pro-max-skill
Walks through designing a banner for social media, ads, a website hero or print, from gathering requirements to building 2 or 3 art-direction options in HTML and CSS.
Agent Reach
Panniantong/Agent-Reach
Routes web research and platform lookups across 16 sites, including Twitter, Reddit, YouTube, Bilibili, Xiaohongshu and GitHub, through one command-line tool.
Ad Creative
LeoYeAI/openclaw-marketing-skills
When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform.
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.
Linkedin Marketing
sergebulaev/linkedin-skills
Plan, draft, audit, and publish LinkedIn posts and comments.
More from alirezarezvani/claude-skills
All 342 skills in this repoAgile Product Owner
alirezarezvani/claude-skills
Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.
Product Strategist
alirezarezvani/claude-skills
OKR cascade toolkit for product leaders: generates aligned company-to-team OKRs from five strategy types and scores how well they line up.
App Store Optimization
alirezarezvani/claude-skills
App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store.
AWS Solution Architect
alirezarezvani/claude-skills
Design AWS architectures for startups using serverless patterns and IaC templates.
Campaign Analytics
alirezarezvani/claude-skills
Calculates attribution, funnel and ROI figures for marketing campaigns with three Python scripts that need only the standard library.
Code to PRD
alirezarezvani/claude-skills
Reverse-engineers a frontend, backend or fullstack codebase into a product requirements document with per-page docs, an enum dictionary and an API inventory.
Related
Works with
Questions about Linkedin Engagement
What does Linkedin Engagement do?
A skill your agent uses when someone wants to grow reach through comments, replies, groups, or outreach on LinkedIn — a commenting roster, a connection request note, a DM or InMail, a networking…. Linkedin Engagement is an agent skill from alirezarezvani/claude-skills. Use when someone wants to grow reach through comments, replies, groups, or outreach on LinkedIn — a commenting roster, a connection request note, a DM or InMail, a networking plan, or a check on whether their outreach volume is safe.
When should I use Linkedin Engagement?
Linkedin Engagement fits situations like: someone wants to grow reach through comments; outreach on LinkedIn — a commenting roster; A connection request note; A networking plan.
How do I install Linkedin Engagement in Claude Code?
Run `npx skills add alirezarezvani/claude-skills --skill linkedin-engagement -a claude-code`. Or copy the skill folder (marketing/linkedin/skills/linkedin-engagement in alirezarezvani/claude-skills) into .claude/skills/linkedin-engagement in your project. Claude Code loads it when a task matches its description.
How do I install Linkedin Engagement in Codex?
Run `npx skills add alirezarezvani/claude-skills --skill linkedin-engagement -a codex`. Or copy the skill folder (marketing/linkedin/skills/linkedin-engagement in alirezarezvani/claude-skills) into .agents/skills/linkedin-engagement in your project. Codex loads it when a task matches its description.
Can I use Linkedin Engagement 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 alirezarezvani/claude-skills --skill linkedin-engagement -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-engagement, .gemini/skills/linkedin-engagement, .github/skills/linkedin-engagement and .opencode/skills/linkedin-engagement in your project.
What does Linkedin Engagement need to run?
Going by SKILL.md and its folder, Linkedin Engagement needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3.
Does Linkedin Engagement 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 Engagement 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 Engagement use?
Linkedin Engagement 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 Engagement use?
About 1.3k tokens (SKILL.md is roughly 5.4k 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 3.3k tokens, read only when the agent opens those files.
What are the alternatives to Linkedin Engagement?
Skills that share tags, products or a category with Linkedin Engagement: Social (coreyhaines31/marketingskills, 54k stars), Banner Design System (nextlevelbuilder/ui-ux-pro-max-skill, 134k stars), Agent Reach (Panniantong/Agent-Reach, 94k stars) and Ad Creative (LeoYeAI/openclaw-marketing-skills, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Linkedin Engagement?
alirezarezvani (a GitHub user) maintains it in alirezarezvani/claude-skills, which has 27,891 GitHub stars. The repository holds 342 skills in this directory. The repository was last updated on August 30, 2026.
Source: alirezarezvani/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.