Podcast Pipeline
ericosiu/ai-marketing-skills
Podcast-to-Everything content pipeline. An agent skill from ericosiu/ai-marketing-skills.
A skill your agent uses when someone needs a LinkedIn plan rather than a post — content pillars, positioning for a career change or consulting or thought leadership, a sustainable posting cadence…
Install Linkedin Strategy
$ npx skills add alirezarezvani/claude-skills --skill linkedin-strategy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install alirezarezvani/claude-skills linkedin-strategy --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-strategy .claude/skills/linkedin-strategy && 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-strategy" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/marketing/linkedin/skills/linkedin-strategy into .claude/skills/linkedin-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-strategy", 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-strategyType 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-strategy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install alirezarezvani/claude-skills linkedin-strategy --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-strategy .agents/skills/linkedin-strategy && 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-strategy" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/marketing/linkedin/skills/linkedin-strategy into .agents/skills/linkedin-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-strategy", 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-strategy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install alirezarezvani/claude-skills linkedin-strategy --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-strategy .cursor/skills/linkedin-strategy && 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-strategy" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/marketing/linkedin/skills/linkedin-strategy into .cursor/skills/linkedin-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-strategy", 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-strategy--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-strategy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install alirezarezvani/claude-skills linkedin-strategy --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-strategy .gemini/skills/linkedin-strategy && 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-strategy" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/marketing/linkedin/skills/linkedin-strategy into .gemini/skills/linkedin-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-strategy", 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-strategyInstalls 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-strategy -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-strategy .github/skills/linkedin-strategy && 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-strategy" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/marketing/linkedin/skills/linkedin-strategy into .github/skills/linkedin-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-strategy", 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-strategy -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-strategy --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-strategy .opencode/skills/linkedin-strategy && 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-strategy" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/marketing/linkedin/skills/linkedin-strategy into .opencode/skills/linkedin-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-strategy", 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-strategy- GitHub stars
- 28k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 531 words
- Files
- 9 (incl. scripts, references, assets)
- Skills in repo
- 342
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when someone needs a LinkedIn plan rather than a post — content pillars, positioning for a career change or consulting or thought leadership, a sustainable posting cadence…
- Someone needs a LinkedIn plan rather than a post — content pillars
- SKILL.md covers Workflow, Rules, Scripts and References and assets, plus 1 more section
- Runs Python scripts from its folder; calls python3
- Positioning for a career change
What it does
Linkedin Strategy is an agent skill from alirezarezvani/claude-skills. Use when someone needs a LinkedIn plan rather than a post — content pillars, positioning for a career change or consulting or thought leadership, a sustainable posting cadence, or a newsletter decision. Triggers on "what should I post about", "how often should I post", "LinkedIn content strategy", "should I start a LinkedIn newsletter", "grow my following", "90-day plan". Validates the positioning brief, sizes the week against real hours and refuses a plan that will not survive week five, and gates a newsletter…
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files, including scripts, reference files and assets (for example `assets/example_brief.json`, `assets/positioning_brief_template.md` and `references/cadence_and_consistency.md`).
It sits in Writing & Content, covering Content strategy, Newsletters and Positioning and messaging. 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 needs a LinkedIn plan rather than a post — content pillars
- Positioning for a career change
- Thought leadership
- A sustainable posting cadence
Example prompts
- “what should I post about”
- “how often should I post”
- “LinkedIn content strategy”
- “/linkedin-strategy”
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 Strategy loads about 1.3k tokens when it runs, and up to ~5.7k if it reads all its reference files. Until then it costs about 148 tokens; SKILL.md has 531 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). 531 words, ~1,280 tokens.
Download SKILL.mdSave it as
.claude/skills/linkedin-strategy/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.- name
- linkedin-strategy
- description
- Use when someone needs a LinkedIn plan rather than a post — content pillars, positioning for a career change or consulting or thought leadership, a sustainable posting cadence, or a newsletter decision. Triggers on "what should I post about", "how often should I post", "LinkedIn content strategy", "should I start a LinkedIn newsletter", "grow my following", "90-day plan". Validates the positioning brief, sizes the week against real hours and refuses a plan that will not survive week five, and gates a newsletter against eligibility and a six-month cadence commitment.
- license
- MIT
- metadata.version
- 1.0.0
- metadata.author
- Alireza Rezvani
- metadata.category
- marketing
- metadata.updated
- 2026-08-25
LinkedIn Strategy — brief, cadence, newsletter
Three decisions, in this order. Out of order is why most LinkedIn efforts produce a feed of unrelated observations and stop in week five.
Workflow
1. The brief — an editorial constitution, not a wish. Walk the five questions one at a time, each with a recommended answer, then validate:
python3 scripts/positioning_brief.py --input brief.json --output humanIt refuses on the two things that make everything downstream impossible: an objective that
is not one of the six real ones (career-change, consulting, thought-leadership,
hiring, fundraising, community), and an audience too broad to exclude anyone. It also
refuses fewer than two exclusions — a positioning that excludes nothing is availability.
Pillars: two to four, shares summing to 100, at least one backed by proof that already exists, at least one at 10-20% as the experimental slot. Every pillar needs a "why you"; if anyone could post it, cut it.
The script emits observable 90-day criteria. Follower count is deliberately absent — it moves for reasons unrelated to whether the objective is being met.
2. The cadence — priced against a bad week.
python3 scripts/cadence_planner.py --minutes 240 --stage starting --target-posts 3 --output humanExit 0 fits / 2 below the 90-minute floor / 3 over budget with the overage named. Every activity is priced in minutes including the reply window, which is part of the post and not an extra. Allocation shifts with stage: from a standing start 60% of the budget belongs in other people's comment sections, because a post published to nobody reaches nobody.
Below 90 minutes a week it refuses to plan a posting schedule and returns a comment-only week: a cadence abandoned in week five is worse than one never started, because the abandonment is visible on the profile. Every plan ships with a minimum viable week.
3. The newsletter — only if the promise can be paid.
python3 scripts/newsletter_planner.py --followers 1800 --cadence biweekly \
--minutes-per-month 420 --pillar "..." --output humanRefuses below LinkedIn's published 150-follower evaluation floor, and refuses a cadence whose six-month cost exceeds the budget. Emits a 12-issue arc rotating issue types across pillars, and a stop rule written before issue one.
Show full SKILL.md (207 more words)Show less
Rules
- One objective. Two objectives serve neither; the audiences overlap less than they look.
- The exclusion list is the positioning. Refuse to skip it.
- Price the week from a bad week, not a good one.
- Consistency over volume. A skipped week is fine; a skipped month resets you.
- Review the brief quarterly, not weekly. A brief revised monthly is a mood.
Scripts
| Script | Role |
|---|---|
scripts/positioning_brief.py | Validates objective, audience, 2-4 proof-backed pillars, and the exclusion list; emits observable 90-day criteria. |
scripts/cadence_planner.py | Prices the week in minutes, allocates by stage, refuses over-budget targets, emits the minimum viable week. |
scripts/newsletter_planner.py | Eligibility + six-month sustainability gate, 12-issue arc across pillars, stop rule. |
References and assets
references/objective_to_pillars.md— the six objectives and the pillar arithmetic (7 sources)references/cadence_and_consistency.md— what a post really costs and why the floor exists (7 sources)references/newsletter_playbook.md— eligibility, cadence as a promise, the stop rule (7 sources)assets/positioning_brief_template.md— fillable briefassets/example_brief.json— a passing brief, for the validator
Distinct from
linkedin-content— drafts and lints individual posts. This decides what they are about and how many there are. Posts without pillars are noise; offer this first, never chain silently.linkedin-analytics— tells you what happened. This decides what to do next.marketing-skill/content-strategy— company-level content marketing. This is one person's own presence.
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 8 other files (scripts, references, assets) in marketing/linkedin/skills/linkedin-strategy of alirezarezvani/claude-skills.
- SKILL.md
- assets/example_brief.json
- assets/positioning_brief_template.md
- references/cadence_and_consistency.md
- references/newsletter_playbook.md
- references/objective_to_pillars.md
- scripts/cadence_planner.py
- scripts/newsletter_planner.py
- scripts/positioning_brief.py
Open the folder on GitHubat commit 19392f7
Compare with similar skills
Linkedin Strategy 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 Strategy this skillalirezarezvani/claude-skills | 28k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Podcast Pipelineericosiu/ai-marketing-skills | 3.6k | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Content Enginec0x12c/ai-toolkit | 106 | — | ~986 | Automated safety check: Pass | None | |
| Content Enginecohen-liel/hivemind | 110 | 6 repos | ~643 | Automated safety check: Pass | Apache-2.0 | |
| Social Contentshawnpang/startup-founder-skills | 341 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Linkedin Strategyericrisco/rsc-harness | 167 | — | ~3.3k | Automated safety check: Pass | MIT |
Similar skills
Content Engine
c0x12c/ai-toolkit
Turn one idea into platform-native content for X, LinkedIn, TikTok, YouTube, newsletters.
Content Engine
cohen-liel/hivemind
Create platform-native content systems for X, LinkedIn, TikTok, YouTube, newsletters, and repurposed multi-platform campaigns.
Social Content
shawnpang/startup-founder-skills
When the user needs to build a LinkedIn authority system, create social content strategy, define content pillars, write posts, or establish thought leadership positioning.
Linkedin Strategy
ericrisco/rsc-harness
A skill your agent uses when a LinkedIn presence — personal brand or company page — needs an account-level decision spanning months: positioning and point of view, three to five content pillars…
Social Media Pro Max
criptogus/agent-evolve-network
State-of-the-art viral content + social design intelligence.
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
Categories
Questions about Linkedin Strategy
What does Linkedin Strategy do?
A skill your agent uses when someone needs a LinkedIn plan rather than a post — content pillars, positioning for a career change or consulting or thought leadership, a sustainable posting cadence…. Linkedin Strategy is an agent skill from alirezarezvani/claude-skills. Use when someone needs a LinkedIn plan rather than a post — content pillars, positioning for a career change or consulting or thought leadership, a sustainable posting cadence, or a newsletter decision.
When should I use Linkedin Strategy?
Linkedin Strategy fits situations like: someone needs a LinkedIn plan rather than a post — content pillars; positioning for a career change; thought leadership; A sustainable posting cadence.
How do I install Linkedin Strategy in Claude Code?
Run `npx skills add alirezarezvani/claude-skills --skill linkedin-strategy -a claude-code`. Or copy the skill folder (marketing/linkedin/skills/linkedin-strategy in alirezarezvani/claude-skills) into .claude/skills/linkedin-strategy in your project. Claude Code loads it when a task matches its description.
How do I install Linkedin Strategy in Codex?
Run `npx skills add alirezarezvani/claude-skills --skill linkedin-strategy -a codex`. Or copy the skill folder (marketing/linkedin/skills/linkedin-strategy in alirezarezvani/claude-skills) into .agents/skills/linkedin-strategy in your project. Codex loads it when a task matches its description.
Can I use Linkedin Strategy 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-strategy -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-strategy, .gemini/skills/linkedin-strategy, .github/skills/linkedin-strategy and .opencode/skills/linkedin-strategy in your project.
What does Linkedin Strategy need to run?
Going by SKILL.md and its folder, Linkedin Strategy needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3.
Does Linkedin Strategy 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 Strategy 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 Strategy use?
Linkedin Strategy 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 Strategy use?
About 1.3k tokens (SKILL.md is roughly 5.1k 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 4.4k tokens, read only when the agent opens those files.
What are the alternatives to Linkedin Strategy?
Skills that share tags, products or a category with Linkedin Strategy: Podcast Pipeline (ericosiu/ai-marketing-skills, 3.6k stars), Content Engine (c0x12c/ai-toolkit, 106 stars), Content Engine (cohen-liel/hivemind, 110 stars) and Social Content (shawnpang/startup-founder-skills, 341 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Linkedin Strategy?
alirezarezvani (a GitHub user) maintains it in alirezarezvani/claude-skills, which has 27,829 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.