borghei/Claude-Skills / tools/linkedin/linkedin-content-planner
linkedin-content-planner
VerifiedBuilds a weekly or monthly LinkedIn publishing plan from content pillars, a posting cadence and a format mix, with a founder-oriented pillar set as an alternative to the general one. Use when planning a week, a month or a launch period of posts rather than drafting a single post.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 15.7 KB |
| assets/plan_config_template.json | config | 861 B |
| assets/sample_founder_config.json | config | 1017 B |
| assets/sample_plan_config.json | config | 1.2 KB |
| assets/sample_story_bank.json | config | 4.6 KB |
| assets/weekly_plan_template.md | markdown | 3.0 KB |
| references/cadence-formats-and-config.md | markdown | 11.5 KB |
| references/founder-pillar-set.md | markdown | 11.8 KB |
| references/pillars-and-mix.md | markdown | 11.7 KB |
| scripts/plan_builder.py | script | 14.1 KB |
| scripts/plan_rules.py | script | 13.0 KB |
assets/weekly_plan_template.md
View on GitHub# Weekly Publishing Plan
One sheet per week. Copy the slots from the `plan_builder.py` output, then add
the angle and the status by hand. Fix the angle only for the week about to
start; later weeks keep pillar, format and ask and get their angle on the day
they are planned.
## Week
| Field | Value |
|-------|-------|
| Owner | |
| Week starting | |
| Plan this week belongs to (start date, length) | |
| Pillar set | general / founder / own |
| Posts planned this week | |
| Produced-format posts this week (capacity: ) | |
| Story bank attached? | yes / no |
Assumptions made because an input was not confirmed:
-
## Slots
| Date | Day | Pillar | Format | Ask | Source entry (id + title) | Angle in one line | Status |
|------|-----|--------|--------|-----|---------------------------|-------------------|--------|
| | | | | | | | to draft / drafted / approved / published / skipped |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
Angle rule: the line names what happened, not what the post is "about".
"The week the planning software was down and the paper board took over" is an
angle. "Resilience in operations" is not.
## Conversation blocks
| Date | Day | Whose posts to read (3 to 6 names or kinds of people) | Time box | Done |
|------|-----|-------------------------------------------------------|----------|------|
| | | | | |
| | | | | |
## Flags from the builder and what was decided
| Flag | Where | Decision |
|------|-------|----------|
| | | fixed in config / accepted because ... / slot removed |
| | | |
| | | |
## Slots without a source entry
Each needs an interview question, a different entry, or removal. Do not leave
a slot to be improvised on the day.
| Date | Pillar | What will supply it | By when |
|------|--------|---------------------|---------|
| | | | |
| | | | |
## Pre-week checklist
- [ ] Every `error` flag resolved by changing the config and rebuilding
- [ ] Every `warn` flag has a written decision above
- [ ] No more than one promotional post this week
- [ ] Each slot has a source entry or a named plan to get one
- [ ] Naming checked for every entry used: clear, or consent obtained, or anonymised
- [ ] Nothing in this week touches a no-go subject
- [ ] Time set aside on each posting day to answer replies
- [ ] Conversation blocks are in the diary
## End-of-week review
| Question | Answer |
|----------|--------|
| Slots published as planned | of |
| Slots skipped, and which pillars | |
| Which post was easiest to write, and why | |
| Which post drew the readers it was meant for | |
| Entries to mark as used in the story bank | |
| One thing to change in next week's plan (one only) | |
## Example row (fictional)
| Date | Day | Pillar | Format | Ask | Source entry | Angle in one line | Status |
|------|-----|--------|--------|-----|--------------|-------------------|--------|
| 2026-10-13 | tue | craft | text | keep | S-001 Payroll corrections after the cut-off change | Moving the timesheet deadline by twenty hours cut correction runs from nine to two | to draft |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |