linkedin-content-calendar
Skill1 starsChanged 46 days agoMITView on GitHub
Plan 1–4 weeks of LinkedIn posts for a personal profile or company page from the user's goals, content pillars or a source to repurpose (blog URL, video, transcript, newsletter), draft every post, and schedule them with the PostOnce LinkedIn MCP. Use when the user asks for a LinkedIn content calendar, a LinkedIn posting schedule, LinkedIn post ideas for the month, or a plan to post on LinkedIn consistently.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- styfinity/linkedin-enginetheir own version, first seen Jun 30, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- styfinity/linkedin-engine★ 9same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 31
Not possible through this server: document (PDF) posts, polls, articles, newsletters and first comments.
- Distinctive: line 38
Keep every post under 3,000 characters.
- Distinctive: line 39
Don't schedule the same text to the profile and the company page at the same time.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
LinkedIn content calendar
Plan a realistic run of LinkedIn posts, draft each one fully, and schedule the set once the user approves it. Consistency matters more than volume; a plan the user can keep beats a daily plan they drop in week two.
Inputs to get first
- Who posts: the user's profile, a company page, or both. (Company pages must already be connected in the PostOnce dashboard.)
- Goal: hiring, leads, audience, a launch, thought leadership.
- 2–4 pillars, or a source to repurpose: blog URLs, a video or podcast transcript, a newsletter, release notes.
- How many weeks (1–4) and posts per week. 2–3 a week is a solid default for most people.
- Timezone and preferred days and times. If they have none, suggest weekday mornings in their audience's timezone as a starting point, and say so.
- Real stories, numbers and media they can use. Never invent them.
Post types to mix
| Type | Media | Notes |
| Text post | None | Story, lesson, opinion. Use linkedin-post-writer. |
| Image post | 1 image | A real photo, chart or screenshot. |
| Multi-image post | 2–20 images | Lists and step-by-steps. Use linkedin-image-carousel. |
| Video | 1 video, up to 30 minutes | Short clips work best for most posts. |
Not possible through this server: document (PDF) posts, polls, articles, newsletters and first comments. If the plan needs a link in the first comment, note it for the user to add after the post goes live.
Rules
- One idea per post. A long source becomes several posts, each with its own angle.
- Rotate pillars and formats so no two neighboring posts feel the same.
- Each draft follows the
linkedin-post-writerrules: hook in the first two lines, short lines, one ending. Check the "see more" fold withlinkedin-text-formatter. - Keep every post under 3,000 characters; longer text is cut off.
- Don't schedule the same text to the profile and the company page at the same time; rewrite it for each voice.
Build the calendar
For each slot: date and time, account, pillar, format, hook (line 1), media needed. Flag slots that still need an image or video from the user.
Output
Return the calendar table, then the full text of every post. Ask for approval and edits. On approval, upload any media with create_upload_url, then call create_post with publish_at for each slot, or create_draft for slots still missing media. Confirm the account (profile or which page) and timezone before the first create_post (see the postonce skill), then report each post ID and scheduled time.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.