- Home
- Skills
- Social Media
- LinkedIn Content Planner: 7-Day Plan
More screenshots
Works with the AI Agents you already use
LinkedIn Content Planner: 7-Day Plan
Plan a week of LinkedIn posts where every post has a job: balanced mix, named angles from real material, a commenting shift, a scored plan.
$5
LinkedIn Content Planner: 7-Day Plan
Example session with this skill installed
I run a bootstrapped SaaS, 30-person team. I want more inbound from LinkedIn without sounding like a guru. My material: in March I changed our pricing and lost 4 of 31 customers before signups recovered; our onboarding drop-off is 38% between signup and first project; and I tell prospects not to buy until they have a named project owner. Audience is US ops leads. Plan my week.
- Read your context and instructions
- Compiled the linkedin content planner
Material first, per the protocol. You brought: a pricing change in March that churned 4 of 31 customers before signups recovered; onboarding drop-off measured at 38% between signup and first project; and a position that costs you something — you tell prospects not to buy until they have a named project owner. Goal is inbound leads, so the default mix holds: Teach 40, Reveal 30, Gather 20, Invite 10. With four posts that is Teach twice, Reveal once, Gather once, and the Invite folded into your pinned post this week.
The week (ET; your audience is US ops leads). Mon: commenting only, 12 comments, patterns below. Tue 8:30 AM, Teach, text post, hook shape the odd number: "What a 38% onboarding drop-off actually costs a 30-person team, in dollars." Ending: question. Target: saves. Wed 9:00 AM, Reveal, text, hook shape the confession: "The pricing email I sent in March that cost us four customers in a week." Ending: soft statement. Target: comments. Thu 8:30 AM, Gather, text with tags, hook shape the gratitude list: "Three support leads whose onboarding teardowns I steal from, by name." Target: reposts. Fri: no post — a second commenting shift, weighted heavier to prospects as a named exception, since your changelog ships that day.
Commenting shift. Tue: three peer founders, first-substantive-comment pattern. Wed: two ops leads posting about onboarding, bring-data pattern (your 38%). Thu: the three named support leads, gratitude pattern. Fri: two prospects mid-onboarding-redesign, answer-their-question pattern.
Score: receipts 2, balance 2, hooks 2, commenting 2, offer discipline 1 — the pinned post is carrying the Invite alone, acceptable once, flagged. Total 9/10. Pre-flight passes: a Reveal with real cost on Wed, receipts on Tue, no disguised Invite in any post, reaction targets spread across saves, comments, and reposts. Ship it. One note for next week: if Wed outperforms, the March story gets a second life as a document post — that repurpose is planned now, not improvised later.
Connects securely to your tools. The creator never sees your data.
About this skill
Posting daily on instinct produces five versions of the same post, or five posts that have nothing to do with each other. This skill plans the week instead: you bring a theme, an audience, and real material, and it returns a day-by-day plan where every post does a different job.
It starts with the mix. Four content jobs — Teach, Reveal, Gather, Invite — get named percentages up front, with a decision table that swaps the mix for fundraising, hiring, or pure authority goals, plus a founder variant (Conviction, Building in Public, The Math, Proof). The protocol then gathers real material before any planning: a turning point with a date, a number with a named referent, a position that costs you something. Themes are not material, and the skill refuses to plan against them.
Each posting day locks a job, a one-line angle, a format, a hook shape (never repeated in the same week), an ending, and the reaction the post is for. The commenting work that actually drives inbound gets scheduled like it matters: named targets, a pattern per target (first substantive comment, bring data, answer their question), and a 70/20/10 split across peers, aspirational accounts, and prospects.
Before the week ships it is scored on a five-criterion rubric — receipts, balance, hook variety, commenting weight, offer discipline — and read against a seven-item pre-flight gate. Under the bar, the plan gets fixed, not shipped hopefully. A complete worked week for an ops consultant shows the plan, the commenting targets, and the scoring filled in. Edge cases included: the one-post-a-week minimum, planning a month without scripting it into fiction, company pages, regulated industries, and a launch landing mid-week.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Social Media.
This skill produces the plan — the week table, commenting shift, score, and pre-flight verdict. It does not draft the individual posts, schedule them, or post them; writing from the locked angles is a separate step, and publishing stays a human action. The plan is only as good as the material behind it: with no real turning point, number, or costly position available, the honest first deliverable is a material-gathering interview, not a filled-in calendar. Posting times and job mixes are tuned for B2B audiences and may need adjustment for consumer or non-English audiences.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 24 days ago
Permissions
No special permissions declared or detected