linkedin-content-planner SKILL.md skillA
linkedin-content-planner from sergebulaev/linkedin-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add sergebulaev/linkedin-skills/linkedin-content-planner@git:20261003.2f00424Pins git:20261003.2f00424 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- sergebulaev/linkedin-skills
- Path
skills/linkedin-content-planner/SKILL.md- Versions recorded
- 8
- Latest version
- git:20261003.2f00424, committed Oct 3, 2026
- First version recorded
- May 11, 2026
- Size
- 8,281 bytes
- Repository stars
- 5,014
- License
- MIT
Generate a 7-day LinkedIn content plan from a theme, audience, and pillars. Produces per-day post pillar, format, hook type, CTA, posting time, daily comment targets, and a weekly inbound-readiness check. Use when the user wants to plan a week or month of content, not draft a single post (use linkedin-post-writer).
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# LinkedIn Content Planner Produce a 7-day LinkedIn plan built around the 3-pillar discipline (Authority 40-50%, Personal Narrative 30-40%, Community 20-30%). Optionally adds a Product/Offer pillar at 10-15%. ## When to use - User asks "plan my week" or "what should I post this week" - User wants to escape ad-hoc shipping and establish rhythm - Before a launch week (user needs product-pillar alignment) ## Input - **Theme** (optional): e.g., "AI agents shipping in production", "first 6 months of Co.Actor" - **Audience description:** e.g., "B2B founders, AI ops leaders, marketing VPs" - **Pillar mix** (optional): defaults to 40% Authority / 30% Narrative / 20% Community / 10% Product - **Posting days** (optional): defaults to Tue/Wed/Thu/Fri (4 posts) - **Voice samples** (optional): only if `../../references/voice-profile.md` is not filled yet ## Output A markdown plan with: ### 7-day calendar | Day | Time | Pillar | Format | Hook formula | 1-line angle | CTA type | Goal | |---|---|---|---|---|---|---|---| | Mon | — | (commenting day) | — | — | — | — | — | …
Read the whole file at its exact version.
How to install
mdr add sergebulaev/linkedin-skills/linkedin-content-planner@sha256:1d4e4c3679e3c0f3The line at the top of this page pins the label git:20261003.2f00424, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_inzdiu5f25fjxxd4)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 8 versions of this file, between May 11, 2026 and Oct 3, 2026, about one every 21 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261003.2f00424 latest | 2026-10-03 | 2f00424 | 8,281 B | A | view · diff |
| git:20260915.6b78503 | 2026-09-15 | 6b78503 | 7,008 B | A | view · diff |
| git:20260909.093982e | 2026-09-09 | 093982e | 6,981 B | A | view · diff |
| git:20260806.4904cf3 | 2026-08-06 | 4904cf3 | 6,979 B | A | view · diff |
| git:20260630.b4fc4c0 | 2026-06-30 | b4fc4c0 | 5,649 B | A | view · diff |
| git:20260521.65b8a91 | 2026-05-21 | 65b8a91 | 4,681 B | A | view · diff |
| git:20260511.c8f8489 | 2026-05-11 | c8f8489 | 4,702 B | A | view · diff |
| git:20260511.6386a74 | 2026-05-11 | 6386a74 | 4,641 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (8281 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
sergebulaev/linkedin-skills · 5,014 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_inzdiu5f25fjxxd4 GET https://markdownregistry.com/api/v1/resolve?ref=sergebulaev/linkedin-skills/linkedin-content-planner GET https://markdownregistry.com/api/v1/blob/1d4e4c3679e3c0f33d992161563ba80abfecd2b6285cfb916e8cf21a7fa85c24
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from sergebulaev/linkedin-skills
Every file in sergebulaev/linkedin-skills