Linkedin Writer
stevenflanagan1/social-ai-team
LinkedIn Content Specialist. An agent skill from stevenflanagan1/social-ai-team.
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…
$ npx skills add ericrisco/rsc-harness --skill linkedin-strategy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ericrisco/rsc-harness 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/ericrisco/rsc-harness.git skills-src && mkdir -p .claude/skills && cp -r skills-src/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/ericrisco/rsc-harness/tree/main/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/ericrisco/rsc-harness/tree/main/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 ericrisco/rsc-harness --skill linkedin-strategy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ericrisco/rsc-harness linkedin-strategy --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ericrisco/rsc-harness.git skills-src && mkdir -p .agents/skills && cp -r skills-src/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/ericrisco/rsc-harness/tree/main/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 ericrisco/rsc-harness --skill linkedin-strategy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ericrisco/rsc-harness linkedin-strategy --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ericrisco/rsc-harness.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/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/ericrisco/rsc-harness/tree/main/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/ericrisco/rsc-harness.git --path 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 ericrisco/rsc-harness --skill linkedin-strategy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ericrisco/rsc-harness linkedin-strategy --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ericrisco/rsc-harness.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/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/ericrisco/rsc-harness/tree/main/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 ericrisco/rsc-harness 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 ericrisco/rsc-harness --skill linkedin-strategy -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ericrisco/rsc-harness.git skills-src && mkdir -p .github/skills && cp -r skills-src/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/ericrisco/rsc-harness/tree/main/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 ericrisco/rsc-harness --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 ericrisco/rsc-harness linkedin-strategy --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ericrisco/rsc-harness.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/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/ericrisco/rsc-harness/tree/main/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.
linkedin-strategyA 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…
Linkedin Strategy is an agent skill from ericrisco/rsc-harness. Use 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, posting cadence, whether content lives on the founder's profile or the company page, and the social-selling rhythm, read from and written back to the presence's own learning wiki. NOT writing the post copy or hook (that is linkedin-content), NOT building a carousel deck (that is linkedin-carousels), NOT sending DMs (that is…
Its SKILL.md is about 3.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including scripts and reference files (for example `evals/README.md`, `evals/cases.yaml` and `references/ssi-and-pillars.md`).
It sits in Writing & Content, covering Infographics, Content strategy and Messaging and chat bots. It works with LinkedIn. The repository describes itself as: Your agent invents things because it has no memory, and can't touch your database because it has no arms. rsc is the meta-harness that gives it both, plus the trade to know the… The licence is MIT.
7 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit e3d5b33. 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 1 file in scripts/ (Shell), which the agent can run.
From 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 Strategy loads about 3.3k tokens when it runs, and up to ~5.4k if it reads all its reference files. Until then it costs about 149 tokens; SKILL.md has 1,435 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 ericrisco/rsc-harness at commit e3d5b33, republished under its MIT licence (© ericrisco). 1,435 words, ~3,296 tokens.
.claude/skills/linkedin-strategy/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.You operate at account/presence altitude. You decide the territory (what this presence is known for, who it is for) and the system (pillars, cadence, where content lives, the social-selling rhythm) over months. You never write the post, build the carousel, run the DMs, or hit the API — those are single-asset jobs you route out. Mixing altitudes is the #1 reason LinkedIn advice goes generic: an account-level question answered with a tactic about one post produces noise and regresses to blog-post defaults.
Your spine is a read/write loop with the presence's own history. You read the accumulated learnings before deciding and write the decision back, so the next session compounds instead of restarting from a generic "post 3 times a week" template.
| The ask | Skill | Why it is not you |
|---|---|---|
| Post copy, hook, body for one update | ../linkedin-content/SKILL.md | You set the pillar and POV; content writes inside it. |
| A carousel / document-post deck | ../linkedin-carousels/SKILL.md | A single asset's format craft, not the system. |
| Connection requests, DMs, sequences | ../linkedin-outreach/SKILL.md | You set the social-selling rhythm; outreach runs the individual threads. |
| Raw analytics, OAuth, rate limits | ../linkedin-api/SKILL.md | You consume the numbers; the API fetches them. |
| Cross-platform calendar / scheduling | ../content-engine/SKILL.md, ../social-publisher/SKILL.md | Multi-platform planning/posting, not LinkedIn presence architecture. |
| Abstract tone/voice rules | ../brand-voice/SKILL.md | Voice in the abstract; you decide positioning and pillars. |
You are the only LinkedIn skill that operates at account altitude and persists its decisions to the wiki. Every sibling works on a single asset or a single thread.
Read 02-DOCS/wiki/linkedin/ before you decide anything. Why: a positioning or cadence call made without the account's own dwell-time and SSI history is just generic advice with a name on it. The whole value of this skill is that decisions compound.
Extract, in this order:
If the directory is empty or absent, bootstrap it — create 02-DOCS/wiki/linkedin/ with positioning.md, decisions/, and what-worked.md. Do not skip the read because the dir is missing; an empty wiki is a starting state, not a license to free-associate. When you decide, cite what you grounded in ("based on the two carousels that earned top dwell time…").
Full file layout and templates: references/wiki-records.md.
Niche of authority. Be known for a clear point of view in one domain. The 2026 algorithm cross-references each post's topic against your title, skills, and background — posting purposefully inside a demonstrated domain builds topical authority; posting about whatever trends suppresses it. Thought leaders post inside a POV; creators just post often. 95% of decision-makers say thought leadership influences purchasing — so the POV is the asset, not the post count.
Where the content lives — the distribution decision. Personal profiles out-distribute company pages by a wide margin. Decide with this table, not by habit:
| Goal / stage | Lean | Why |
|---|---|---|
| Build reach, inbound, trust | Founder / exec personal profile | Personal content engages ~8x more than the page; profiles get ~65% of feed allocation. |
| Recruiting, official announcements, ad retargeting base | Company page (secondary) | Pages lost ~60-66% organic reach 2024-2026, now ~5% of feed; useful as a base, not a megaphone. |
| Scale reach without paying | Employee advocacy | Advocacy yields ~561% greater reach and ~7x more lead conversion than the page alone; CEO/founder posts get ~4x the page's engagement. |
Rule: humans are the main event. The page amplifies; it never carries.
Bad: All content posted on the company page; the founder reshares occasionally.
Good: The founder posts the POV from their profile; the page reshares as amplification;
5 employees advocate the same week. Reach compounds across human graphs.Define 3-5 pillars. Fewer than 3 is a single-note feed; more than 5 dilutes topical authority and confuses the cross-reference. Each pillar must align to the professional graph — the title, skills, and background LinkedIn already knows — so the 2026 topic match rewards you instead of flagging you off-domain.
Pillars are the territory. ../linkedin-content/SKILL.md writes the individual posts inside them; you do not.
Bad: "I post about whatever's trending that week."
Good: A B2B data-platform founder runs 4 pillars:
1. Pipeline reliability war stories (graph-aligned: their actual job)
2. Hiring/scaling a data team
3. Build-vs-buy decision frameworks
4. Behind-the-scenes founder lessonsWorked pillar sets for a solo consultant and a company page: references/ssi-and-pillars.md.
Pick the highest rate you can sustain for 8 weeks at quality. The sweet spot is 2-5 posts/week, with 3-4/week the highest-ROI band; consistency beats volume — 8 posts/month for 24 months beats 20/month for 6 months then quitting, because the algorithm rewards a sustained schedule, not a burst. Aim ~20-28h between posts; Tue-Thu is strongest for B2B.
Gate every cadence number through this checklist — answer all YES before you commit:
If any answer is NO, lower the cadence. A held 3/week beats an aspirational 5/week that collapses to 1.
Format weight. Carousels and document posts earn 2-3x more dwell time than text or image — and dwell time is the primary 2026 quality signal, not likes. Weight the calendar toward them.
Tie the number to the wiki, not the blog. If the account's own data shows carousels on one topic earning the best dwell time, the cadence recommendation weights toward that — a number justified by §1's read, never a default.
Engagement outweighs raw posting frequency for inbound. Accounts posting 3x/week with active inbound engagement beat daily-posting-no-engagement accounts by ~4.2x in lead gen. The split that works: roughly ~80% of LinkedIn time engaging (commenting on others' posts, replying in your own threads), ~20% creating. "20 min creating + 40 min engaging" beats "60 min creating + 0 engaging." Set this as the rhythm; the individual threads belong to ../linkedin-outreach/SKILL.md.
SSI as a habit system, not a vanity number. The Social Selling Index is a 0-100 score over four 25-point dimensions, refreshed daily on a trailing 90-day window, free at linkedin.com/sales/ssi:
| Dimension (25 pts each) | Weekly habit |
|---|---|
| Establish a professional brand | Publish inside your pillars; complete profile. |
| Find the right people | Targeted search + connect within your niche. |
| Engage with insights | The ~80% engage block — comment with substance. |
| Build relationships | Convert engagement into 1:1 conversations. |
Targets: 65+ for active B2B sellers, 75+ is thought-leader territory, all-user average ~40-50. SSI is benchmarked relative to your industry (not absolute) and responds within ~90 days to habit changes — which makes it a usable steering metric, not a scoreboard. Deep per-dimension habit breakdown: references/ssi-and-pillars.md.
On a quarterly or monthly review, read §1's what-worked + dwell/SSI trend, then branch:
Engagement rising while cadence held?
RISING -> a pillar/format is working. Double down: more slots to that pillar,
more of that format. Log which one and why.
PLATEAUED -> diagnose, do not just post more. Weak pillar topical fit
(off-graph topic suppressed) OR weak format/dwell (text where a
carousel would earn read time)?
DECLINING -> sunset the dead pillar. Reallocate its calendar slot to a rising
one. Log it KILLED so no future session re-proposes it."Post more" never fixes falling engagement — diagnose pillar fit vs format/dwell first.
Append a dated decision record under 02-DOCS/wiki/linkedin/decisions/. Every record names the single metric it bets on and a review date — a decision without a metric is an opinion, not a checkable bet.
---
type: linkedin-decision
title: Move distribution to founder profile
description: Founder profile carries the POV; the company page amplifies; refine to 4 pillars and hold 3/week.
tags: [linkedin, distribution, positioning, cadence]
timestamp: 2026-06-02T00:00:00Z
topic: linkedin
status: stable
---
# 2026-06-02 — Move distribution to founder profile
Context read: SSI 48 (flat 90d); top-2 dwell-time posts both carousels on
"pipeline reliability"; stated cadence 3/week slipped to ~1; company page reach near zero.
Decision: Founder profile carries the POV; company page amplifies; refine to 4 pillars
weighted toward the reliability carousel topic; hold 3/week with carousels Tue/Thu.
Social-selling rhythm: 80/20 engage/create.
Bets on metric: SSI 48 -> 65 within 90 days (proxy for inbound).
Review date: 2026-09-02.The type: field is required (OKF v0.1); timestamp is ISO 8601. The dated heading and the Decision: / Bets on metric: / Review date: lines are domain signals verify.sh greps for — keep them.
After writing, run scripts/verify.sh 02-DOCS/wiki/linkedin/ to confirm the record is structurally complete. Full templates and the what-worked format: references/wiki-records.md.
| Anti-pattern | Why it fails | Do instead |
|---|---|---|
| Dumping content on the company page | ~5% feed allocation; reach is near dead | Founder/employee profiles carry it; the page amplifies |
| Chasing daily posting | Hits a quality cliff, no bandwidth to engage | 3-4/week held + the engage split |
| Posting outside your pillars / domain | 2026 topic cross-reference suppresses authority | Stay inside graph-aligned 3-5 pillars |
| Optimizing for likes | Misses dwell time, the real 2026 signal | Weight carousels/docs; measure dwell time |
| Treating SSI as a vanity score | Ignores it as a steerable habit system | Run the four dimensions as weekly habits |
| Create-only, no engaging | ~4.2x worse inbound | ~80/20 engage-to-create split |
| Deciding without reading the wiki | Regresses to generic blog advice | READ 02-DOCS/wiki/linkedin/ first |
| Never writing the decision back | No compounding; every session restarts | Append a dated record + metric + review date |
references/wiki-records.md — file layout under 02-DOCS/wiki/linkedin/, decision-record and what-worked templates, and exactly what verify.sh checks.references/ssi-and-pillars.md — the four SSI dimensions as concrete weekly habits with targets, pillar-design worked examples, and the personal-vs-page + employee-advocacy reach mechanics.Route single-asset work out: post copy → ../linkedin-content/SKILL.md; carousels → ../linkedin-carousels/SKILL.md; DMs/sequences → ../linkedin-outreach/SKILL.md; raw metrics → ../linkedin-api/SKILL.md; decision discipline → ../decision-records/SKILL.md.
© ericrisco, 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 5 other files (scripts, references) in skills/linkedin-strategy of ericrisco/rsc-harness.
Open the folder on GitHubat commit e3d5b33
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 skillericrisco/rsc-harness | 167 | — | ~3.3k | Automated safety check: Pass | MIT | |
| Linkedin Writerstevenflanagan1/social-ai-team | 241 | — | ~3k | Automated safety check: Pass | None | |
| Content Idea GeneratorBrianRWagner/ai-marketing-claude-code-skills | 440 | — | ~1.7k | Automated safety check: Pass | None | |
| LinkedIn Authority BuilderBrianRWagner/ai-marketing-claude-code-skills | 440 | — | ~1.9k | Automated safety check: Pass | None | |
| Linkedin Skillsalirezarezvani/claude-skills | 28k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Linkedin Strategyalirezarezvani/claude-skills | 28k | — | ~1.3k | Automated safety check: Pass | MIT |
stevenflanagan1/social-ai-team
LinkedIn Content Specialist. An agent skill from stevenflanagan1/social-ai-team.
BrianRWagner/ai-marketing-claude-code-skills
Produces content ideas for LinkedIn, X, newsletters or short video from your positioning statement, in quick, standard or deep planning modes.
BrianRWagner/ai-marketing-claude-code-skills
Builds a LinkedIn thought-leadership content system, from positioning check and content pillars to formats and posting rhythm, in quick, standard or deep modes.
alirezarezvani/claude-skills
A skill your agent uses when someone wants to grow an organic LinkedIn presence — a content strategy for a career change or consulting or thought leadership, a rewritten profile or headline, post…
alirezarezvani/claude-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…
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.
ericrisco/rsc-harness
A skill your agent uses when designing or analyzing a controlled experiment — falsifiable hypothesis, sample size from an MDE, reading significance/CI/power, CUPED, or rescuing tests that won't go…
ericrisco/rsc-harness
A skill your agent uses when making a web UI conform to WCAG 2.2 Level AA — axe-core or Lighthouse a11y violations, keyboard operability, focus management, ARIA roles/names/live regions, contrast…
ericrisco/rsc-harness
A skill your agent uses when running or fixing paid acquisition on Google or Meta — campaign structure (Performance Max, Demand Gen, Search, Advantage+), platform-fit creative, budget/scaling rules…
ericrisco/rsc-harness
A skill your agent uses when measuring whether an LLM or agent system actually got better and gating merges on it: golden sets, fixing an inflated LLM-as-judge, scoring RAG (faithfulness, contextual…
ericrisco/rsc-harness
A skill your agent uses when a creative goal must become a finished media file: pick and order generative-media models per modality — AI voiceover, image-to-video clips, score — then glue them with…
ericrisco/rsc-harness
A skill your agent uses when instrumenting product or web analytics — GA4/PostHog SDK wiring, event taxonomy, funnels, double-counted events, consent gating, PII scrubbing.
Works with
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…. Linkedin Strategy is an agent skill from ericrisco/rsc-harness. Use 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, posting cadence, whether content lives on the founder's profile or the company page, and the social-selling rhythm, read from and written back to the presence's own learning wiki.
Linkedin Strategy fits situations like: A LinkedIn presence — personal brand; company page — needs an account-level decision spanning months: positioning and point of view; three to five content pillars; posting cadence.
Run `npx skills add ericrisco/rsc-harness --skill linkedin-strategy -a claude-code`. Or copy the skill folder (skills/linkedin-strategy in ericrisco/rsc-harness) into .claude/skills/linkedin-strategy in your project. Claude Code loads it when a task matches its description.
Run `npx skills add ericrisco/rsc-harness --skill linkedin-strategy -a codex`. Or copy the skill folder (skills/linkedin-strategy in ericrisco/rsc-harness) into .agents/skills/linkedin-strategy 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 ericrisco/rsc-harness --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.
Going by SKILL.md and its folder, Linkedin Strategy needs a shell for the scripts in its folder. Our summary lists: A Bash shell.
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 Strategy is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.3k tokens (SKILL.md is roughly 13k 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 2.1k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Linkedin Strategy: Linkedin Writer (stevenflanagan1/social-ai-team, 241 stars), Content Idea Generator (BrianRWagner/ai-marketing-claude-code-skills, 440 stars), LinkedIn Authority Builder (BrianRWagner/ai-marketing-claude-code-skills, 440 stars) and Linkedin Skills (alirezarezvani/claude-skills, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
ericrisco (a GitHub user) maintains it in ericrisco/rsc-harness, which has 167 GitHub stars. The repository holds 227 skills in this directory. The repository was last updated on October 7, 2026.
Source: ericrisco/rsc-harness on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.