Skip to content
AI & Agents
Command

/cs-linkedin-plan

/cs-linkedin-plan — Build the positioning brief (objective, audience, 2-4 proof-backed pillars, exclusion list), size a weekly cadence against the hours that actually exist, and gate a newsletter against eligibility and a six-month commitment.

From plugin
claude-skills
30k173 skills129 agents173 commands2 MCP
$ npx -y skills add alirezarezvani/claude-skills --agent claude-code

Command definition

cs-linkedin-plan.md
disable-model-invocation: true
name: "cs-linkedin-plan"
description: "/cs-linkedin-plan — Build the positioning brief (objective, audience, 2-4 proof-backed pillars, exclusion list), size a weekly cadence against the hours that actually exist, and gate a newsletter against eligibility and a six-month commitment."
argument-hint: "[what you want LinkedIn to do for you in 90 days]"

/cs-linkedin-plan — Brief, cadence, newsletter

**Command:** `/cs-linkedin-plan [your 90-day goal]`

Three decisions in order. Out of order is why most LinkedIn efforts produce a feed of unrelated observations and stop in week five.

When to run

  • "What should I post about?" / "How often should I post?"
  • "Should I start a LinkedIn newsletter?"
  • Before drafting anything — posts without pillars are noise

What you get

1. **A validated positioning brief** — one of six real objectives, an audience specific enough to exclude someone, two to four pillars with shares summing to 100, and at least two exclusions. 2. **Observable 90-day criteria.** Follower count is deliberately not among them. 3. **A weekly plan priced in minutes**, allocated by stage, plus the minimum viable week that survives a bad week. 4. **A newsletter verdict** — green, thin, or refused, with a 12-issue arc and a stop rule.

Workflow

python3 ${CLAUDE_PLUGIN_ROOT}/skills/linkedin-strategy/scripts/positioning_brief.py --input brief.json --output human
#   exit 3 = objective or audience too vague to proceed. Fix that before anything else.

python3 ${CLAUDE_PLUGIN_ROOT}/skills/linkedin-strategy/scripts/cadence_planner.py \
  --minutes 240 --stage starting --target-posts 3 --output human
#   exit 2 = below the 90-minute floor -> comment-only week returned
#   exit 3 = over budget, with the overage named

python3 ${CLAUDE_PLUGIN_ROOT}/skills/linkedin-strategy/scripts/newsletter_planner.py \
  --followers 1800 --cadence biweekly --minutes-per-month 420 --output human

Discipline

  • **One objective.** Two serve neither; sequence instead of blending.
  • **The exclusion list is the positioning.** Do not skip it because it feels negative.
  • **Price the week from a bad week.** The plan has to survive week five, not week one.
  • **From a standing start, most of the budget belongs in other people's comments.**
  • **Review quarterly, not weekly.** A brief revised monthly is a mood.

Stop conditions

  • Brief at exit 0 and the cadence plan fits → done; hand over the minimum viable week.
  • Cadence over budget twice on the same target → the target is the problem, not the plan.

Say so and cut it.

  • Newsletter refused → say why once, recommend posts on a fixed day instead, and stop.

Related

  • Skill: [`linkedin-strategy`](../skills/linkedin-strategy/SKILL.md)
  • Next: [`/cs-linkedin-post`](cs-linkedin-post.md) once the brief exists
Read more
@alirezarezvani
Ships withclaude-skills

415 production-ready skills for Claude Code and 12 other coding agents, covering engineering, product, marketing, compliance, finance and the C-suite. We test whether each skill loads when you ask in plain words, and publish the results.

30k200 skills129 agents2 MCP
Get the whole plugin

Stars on GitHub

Momentum

stars in total
29.8k
Star history of alirezarezvani/claude-skills on GitHub, a chart by star-history.com

Other commands on claude-skills.

focused-fix

focused-fix

Command

Deep-dive feature repair — systematically fix an entire feature/module across all its files and dependencies. Usage: /focused-fix…

plugin-audit

plugin-audit

Command

Comprehensive audit pipeline for skills, plugins, agents, and commands. Validates structure, quality, security, marketplace…

More commands from other plugins.

devbox-entrypoint

devbox-entrypoint

Command

Context: runloop resumes a devbox by re-running the same entrypoint script, which invokes `cn serve --id <agentId> ...`. Because…

@continuedev@continuedevInstall Command
c

c

Command

Shortcut for "continue working" — pick the work in flight back up exactly where it stopped and keep going until it is done or…

lifeos2w20k
@danielmiessler@danielmiesslerInstall Command
sidecar

sidecar

Command

Spawn a read-only sidecar subagent to investigate something in this checkout without editing files, moving branches, or touching…

@builderio@builderioInstall Command