linkedin-content-calendar-planner

linkedin-content-calendar-planner is a skill for Claude Code from TaplioOfficial/taplio-linkedin-plugin. It costs 116 tokens per session (2,220 once invoked), scanned A, a copy of linkedin-content-calendar-planner, MIT.

A planner for creating a four-week LinkedIn posting schedule based on topics, posting frequency, audience timing, events, and preferred formats. Each planned post gets a topic, format, opening angle, and call to action.

In plain words
What is it for?
Use it to plan a month of LinkedIn posts around chosen themes and a selected weekly posting frequency.
Why use it?
It removes the need to invent a post from scratch every day and gives content work a repeatable schedule.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions Claude Code.

Part of the taplio plugin — 17 skills, 1 MCP server shipped together

Good fit Use it to plan a month of LinkedIn posts around chosen themes and a selected weekly posting frequency.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/taplioofficial/taplio-linkedin-plugin/linkedin-content-calendar-planner
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add TaplioOfficial/taplio-linkedin-plugin --skill linkedin-content-calendar-planner
Clone the repo
git clone --depth 1 https://github.com/TaplioOfficial/taplio-linkedin-plugin

Made for: Claude Code.

Or install taplio, the plugin that ships this one along with the rest of its 17 skills, 1 MCP server.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for linkedin-content-calendar-planner

README.md
[![agentmods](https://agentmods.dev/badge/skills/taplioofficial/taplio-linkedin-plugin/linkedin-content-calendar-planner/github.svg)](https://agentmods.dev/skills/taplioofficial/taplio-linkedin-plugin/linkedin-content-calendar-planner)
Your own site
<a href="https://agentmods.dev/skills/taplioofficial/taplio-linkedin-plugin/linkedin-content-calendar-planner"><img src="https://agentmods.dev/badge/skills/taplioofficial/taplio-linkedin-plugin/linkedin-content-calendar-planner/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for linkedin-content-calendar-planner

Your own site · 80×15
<a href="https://agentmods.dev/skills/taplioofficial/taplio-linkedin-plugin/linkedin-content-calendar-planner"><img src="https://agentmods.dev/badge/skills/taplioofficial/taplio-linkedin-plugin/linkedin-content-calendar-planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 116 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,220 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00116 $0.02220
Opus 5 $0.00058 $0.01110
Sonnet 5 $0.00023 $0.00444
Haiku 4.5 $0.00012 $0.00222

Measured 11d ago against content hash a0b833da8d5c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

linkedin-content-calendar-planner scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

100% identical to linkedin-content-calendar-planner — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/linkedin-content-calendar-planner/SKILL.md · 123 lines

How it starts

The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.

LinkedIn Content Calendar Planner

The hardest part of LinkedIn is showing up. A calendar makes showing up the easy default.

When to trigger

The user says "plan my month", "give me a content calendar", "I improvise too much", "what should I post next week ?", "build me 4 weeks of content".

Inputs to ask for

  1. The user's pillars (from the Content Pillars Builder skill).
  2. The desired posting cadence (3 / 4 / 5 / 7 posts per week). Default to 4. More is rarely better.
  3. The audience's time zone and the user's best posting windows (default : Tue-Thu 8am-10am local).
  4. Any specific milestones in the next month (product launch, event, vacation, big news to react to).
  5. The mix of formats the user is comfortable with (text, carousel, image, poll, video).

Cadence guidance

  • Below 3 posts/week : you do not exist. Hard to grow.
  • 3 posts/week : minimum to build momentum. Tue-Wed-Thu.
  • 4 to 5 posts/week : the growth zone for most creators.
  • Daily : only if the user already has a system AND a strong pipeline of ideas. Otherwise it crashes content quality.

Process

  1. Ask for the inputs above.
  2. Build the 4-week grid : 1 post per day on the chosen days.
  3. For each post, pick :
    • Pillar (rotating through them so the audience sees the full positioning).
    • Format (text / story / listicle / carousel / opinion / poll / image).
    • Topic (specific, not generic).
    • Hook angle (the type of opening : curiosity, contrarian, number, etc.).
    • CTA goal (comment, share, DM, follow, click).
  4. Front-load the strongest posts in week 1. New systems lose momentum without early wins.
  5. Leave 1 "wildcard" slot per week to react to news, trends, or live moments.
  6. Show the grid and get the user to confirm it. The grid is the plan, not the deliverable.
  7. Once the grid is confirmed, write a complete, publish-ready post for every non-wildcard slot : a real hook, a full body, and a CTA, in the user's voice. Do not stop at a topic line or a brief : the user should be able to read each post end to end. Create each one as a Taplio draft (see the MCP section). Leave wildcard slots as a one-line prompt, not a full draft.
  8. Keep the whole calendar in memory : the mapping of slot (week, day, date, pillar) to draft id, draft content, and review status (drafted / approved / scheduled). You will need it to walk the user through review and to schedule on approval.
  9. Review before scheduling. Walk the user through the drafts one at a time (or in batches if they prefer), let them edit any of them, and only schedule a draft once they approve it. Scheduling is the definitive step : nothing gets a date until the user has seen the actual post.

Read the full file on GitHub · 123 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 123 lines · 116 tokens per session scan A a0b833da8d5c

Subscribe to this mod's changes

linkedin-content-calendar-planner is a skill published in the GitHub repository TaplioOfficial/taplio-linkedin-plugin (2 stars, last pushed 2mo ago), licensed MIT. It adds 116 tokens to every session and 2,220 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to linkedin-content-calendar-planner, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

financial-statement-analysis

Reads a set of financial statements and establishes what changed and why — fluctuation analysis against prior period and against budget, profitability, liquidity, solvency and efficiency ratios, benchmarking, and the non-GAAP measures presented alongside them. Use this to interpret results, review a counterparty's or…

cbrock84/headcount · 93 tokens

youtube-producer

Plans, packages, and scripts long-form video for retention and channel growth — idea selection, titles and thumbnails, script structure, and diagnosing why a video or channel underperforms. Use this for video ideas, packaging, scripting, a retention teardown, or channel strategy — including when someone describes a…

cbrock84/headcount · 86 tokens

scenario-planning

Plans under genuine uncertainty — building scenarios, identifying which assumptions are load-bearing, setting early-warning indicators, and stress-testing a plan against futures rather than forecasting one. Use this when a decision depends on something unknowable, when a plan assumes conditions that may not hold…

cbrock84/headcount · 78 tokens

ai-ml-governance

Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory…

cbrock84/headcount · 83 tokens

paid-advertising

Plans, runs, and optimizes paid acquisition across search, social, and display — account structure, targeting, creative, bidding, budget, and the analysis that says whether to scale or stop. Use this to set up or restructure campaigns, write and iterate ad creative, diagnose rising costs or falling performance, decide…

cbrock84/headcount · 78 tokens

ai-research-analyst

Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a…

cbrock84/headcount · 91 tokens