LinkedIn Strategy Planner

LinkedIn Strategy — brief, cadence, newsletter

by alirezarezvani · MIT license · ★ 26,349 on GitHub · updated Aug 30

LinkedIn Strategy — brief, cadence, newsletter cover

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…

---
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
  author: Alireza Rezvani
  category: marketing
  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

Overview

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

Manual install (npx, ZIP)
Claude Codenpx skills add alirezarezvani/claude-skills --skill linkedin-strategy -g -a claude-code
Claude Code (degit)npx degit alirezarezvani/claude-skills/marketing/linkedin/skills/linkedin-strategy#main ~/.claude/skills/linkedin-strategy
Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md5.0 KB
Read SKILL.md here
alirezarezvani/main1 file shown
SKILL.md
Show the full text100 lines

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 human

It 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 human

Exit 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 human

Refuses 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.

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

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

1---
2name: linkedin-strategy
3description: 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.
4license: MIT
5metadata:
6 version: 1.0.0
7 author: Alireza Rezvani
8 category: marketing
9 updated: 2026-08-25
10---
11 
12# LinkedIn Strategy — brief, cadence, newsletter
13 
14Three decisions, in this order. Out of order is why most LinkedIn efforts produce a feed of
15unrelated observations and stop in week five.
16 
17## Workflow
18 
19**1. The brief — an editorial constitution, not a wish.** Walk the five questions one at a
20time, each with a recommended answer, then validate:
21 
22```bash
23python3 scripts/positioning_brief.py --input brief.json --output human
24```
25 
26It refuses on the two things that make everything downstream impossible: an objective that
27is not one of the six real ones (`career-change`, `consulting`, `thought-leadership`,
28`hiring`, `fundraising`, `community`), and an audience too broad to exclude anyone. It also
29refuses fewer than two exclusions — **a positioning that excludes nothing is availability.**
30 
31Pillars: two to four, shares summing to 100, at least one backed by proof that already
32exists, at least one at 10-20% as the experimental slot. Every pillar needs a "why you"; if
33anyone could post it, cut it.
34 
35The script emits observable 90-day criteria. Follower count is deliberately absent — it moves
36for reasons unrelated to whether the objective is being met.
37 
38**2. The cadence — priced against a bad week.**
39 
40```bash
41python3 scripts/cadence_planner.py --minutes 240 --stage starting --target-posts 3 --output human
42```
43 
44Exit 0 fits / 2 below the 90-minute floor / 3 over budget with the overage named. Every
45activity is priced in minutes including the reply window, which is part of the post and not
46an extra. Allocation shifts with stage: from a standing start **60% of the budget belongs in
47other people's comment sections**, because a post published to nobody reaches nobody.
48 
49Below 90 minutes a week it refuses to plan a posting schedule and returns a comment-only
50week: a cadence abandoned in week five is worse than one never started, because the
51abandonment is visible on the profile. Every plan ships with a minimum viable week.
52 
53**3. The newsletter — only if the promise can be paid.**
54 
55```bash
56python3 scripts/newsletter_planner.py --followers 1800 --cadence biweekly \
57 --minutes-per-month 420 --pillar "..." --output human
58```
59 
60Refuses below LinkedIn's published 150-follower evaluation floor, and refuses a cadence
61whose six-month cost exceeds the budget. Emits a 12-issue arc rotating issue types across
62pillars, and a stop rule written before issue one.
63 
64## Rules
65 
66- **One objective.** Two objectives serve neither; the audiences overlap less than they look.
67- **The exclusion list is the positioning.** Refuse to skip it.
68- **Price the week from a bad week, not a good one.**
69- **Consistency over volume.** A skipped week is fine; a skipped month resets you.
70- **Review the brief quarterly, not weekly.** A brief revised monthly is a mood.
71 
72## Scripts
73 
74| Script | Role |
75|---|---|
76| [`scripts/positioning_brief.py`](scripts/positioning_brief.py) | Validates objective, audience, 2-4 proof-backed pillars, and the exclusion list; emits observable 90-day criteria. |
77| [`scripts/cadence_planner.py`](scripts/cadence_planner.py) | Prices the week in minutes, allocates by stage, refuses over-budget targets, emits the minimum viable week. |
78| [`scripts/newsletter_planner.py`](scripts/newsletter_planner.py) | Eligibility + six-month sustainability gate, 12-issue arc across pillars, stop rule. |
79 
80## References and assets
81 
82- [`references/objective_to_pillars.md`](references/objective_to_pillars.md) — the six objectives and the pillar arithmetic (7 sources)
83- [`references/cadence_and_consistency.md`](references/cadence_and_consistency.md) — what a post really costs and why the floor exists (7 sources)
84- [`references/newsletter_playbook.md`](references/newsletter_playbook.md) — eligibility, cadence as a promise, the stop rule (7 sources)
85 
86- [`assets/positioning_brief_template.md`](assets/positioning_brief_template.md) — fillable brief
87- [`assets/example_brief.json`](assets/example_brief.json) — a passing brief, for the validator
88 
89## Distinct from
90 
91- **`linkedin-content`** — drafts and lints individual posts. This decides what they are about
92 and how many there are. Posts without pillars are noise; offer this first, never chain silently.
93- **`linkedin-analytics`** — tells you what happened. This decides what to do next.
94- **`marketing-skill/content-strategy`** — company-level content marketing. This is one
95 person's own presence.
96 
97---
98 
99**Version:** 1.0.0
100 
View all files on GitHub →

Details

Updated
Aug 30, 2026
License
MIT
Stars on the repo
★ 26,349
Checked
Source
alirezarezvani/claude-skills ↗
Creator
alirezarezvani · 363 listings
View creator

Similar skills

See all →
SkillLead Magnet Buildercoreyhaines31/marketingskills · by coreyhaines31Tell us about your business and who you sell to, and get back a ready-to-launch free offer that turns website visitors into email signups and future customers.★ 51.1k GitHub starsSkillEmail Newsletter Writercwinvestments/memstack · by cwinvestmentsUse this skill when the user says 'newsletter', 'email newsletter', 'weekly digest', 'subscriber growth', 'open rates', or needs subject lines, content structure, sponsorship placement, and growth tactics for email newsletters. Do NOT use for lead magnets or content pipelines.★ 423 GitHub starsSkillSignal Based Cold Emailkami-community/kami · by kami-communityWrite a signal-based cold outreach email that earns a reply. Use when drafting outbound/SDR email to a prospect with a known recent signal (funding, hiring, exec hire, launch, community post).★ 64 GitHub starsSkillHostinger Email Marketinghostinger/hostinger-agent-skills · by hostingerHostinger Reach (Email Marketing) API for contact management, segmentation, contact groups, and profile management. Use when creating or listing contacts, managing contact segments or groups, filtering contacts by subscription status, or working with email marketing profiles.★ 23 GitHub starsAgentEmail Lifecycle Strategistmsitarzewski/agency-agents · by msitarzewskiExpert email marketing strategist for CRM-driven campaigns, lifecycle automation, segmentation architecture, and deliverability. Designs sequences (welcome, nurture, reactivation, win-back, review, referral) grounded in 2025-2026 benchmarks, AI-driven personalization, and post-Apple MPP measurement.★ 154k GitHub starsSkillB2B Email Writercoreyhaines31/marketingskills · by coreyhaines31Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Also use when the user mentions "cold outreach," "prospecting email," "outbound email," "email to leads," "reach out to prospects," "sales email," "follow-up email sequence," "nobody's replying to my emails," or "how do I write a cold email." Covers subject lines, opening lines, body copy, CTAs, personalization, and multi-touch follow-up sequences. For warm/lifecycle email sequences, see emails. For sales collateral beyond emails, see sales-enablement.★ 51.1k GitHub stars

More from alirezarezvani

SkillExperiment Resume Toolalirezarezvani/claude-skills · by alirezarezvaniResume a paused experiment. Checkout the experiment branch, read results history, continue iterating. Use when the user runs /ar:ar-resume or asks to pick up a previously started autoresearch experiment.★ 26.3k GitHub starsSkillExperiment Dashboard Vieweralirezarezvani/claude-skills · by alirezarezvaniShow experiment dashboard with results, active loops, and progress. Use when the user runs /ar:ar-status or asks how an autoresearch experiment is going.★ 26.3k GitHub starsSkillAutonomous Experiment Runneralirezarezvani/claude-skills · by alirezarezvaniStart an autonomous experiment loop with user-selected interval (10min, 1h, daily, weekly, monthly). Uses CronCreate for scheduling. Use when the user runs /ar:loop or asks to run an autoresearch experiment continuously on a schedule.★ 26.3k GitHub starsSkillSingle Experiment Iteratoralirezarezvani/claude-skills · by alirezarezvaniRun a single experiment iteration. Edit the target file, evaluate, keep or discard. Use when the user runs /ar:run or asks for one manual autoresearch iteration.★ 26.3k GitHub starsSkillAutoresearch Experiment Setupalirezarezvani/claude-skills · by alirezarezvaniSet up a new autoresearch experiment interactively. Collects domain, target file, eval command, metric, direction, and evaluator. Use when the user runs /ar:setup or asks to start optimizing a file with the autoresearch loop.★ 26.3k GitHub starsSkillExecutive Boardroom Deliberatoralirezarezvani/claude-skills · by alirezarezvani/cs:boardroom <brief> — 6-phase multi-role deliberation across the C-suite with Phase 2 isolation, critic pre-screen, and synthesis. Outputs a board memo. Use when a decision spans multiple executive domains — e.g. a pricing change touching finance, positioning, and product, or a raise-vs-cut runway call.★ 26.3k GitHub stars