Skip to content
Back to skills

Flink Weekly Linkedin Routine

ASecurity

Builds your weekly LinkedIn hour as a 60 minute checklist (ideas from this week's calls and emails, one draft, voice and claim checks, comments, conversations to start), with what Claude prepares before you sit down and what only you do. Use for "run flink-weekly-linkedin-routine", "my LinkedIn hour", "weekly LinkedIn routine", "I have one hour for LinkedIn this week", "prep my LinkedIn session", "LinkedIn keeps falling off my week", part of the Claude Playbook for Authentic LinkedIn Presence...

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 5, 2026
ai-agentsgo

Works with

  • cli

Security analysis

A100/100

Scanned October 5, 2026

npx -y skills add polar-bear-org/claude-skills --skill flink-weekly-linkedin-routine --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Flink Weekly Linkedin Routine?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Flink Weekly Linkedin Routine
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/polar-bear-org-flink-weekly-linkedin-routine/badge)](https://www.skillsdirectory.com/skills/polar-bear-org-flink-weekly-linkedin-routine)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: flink-weekly-linkedin-routine
description: Builds your weekly LinkedIn hour as a 60 minute checklist (ideas from this week's calls and emails, one draft, voice and claim checks, comments, conversations to start), with what Claude prepares before you sit down and what only you do. Use for "run flink-weekly-linkedin-routine", "my LinkedIn hour", "weekly LinkedIn routine", "I have one hour for LinkedIn this week", "prep my LinkedIn session", "LinkedIn keeps falling off my week", part of the Claude Playbook for Authentic LinkedIn Presence Pack by Polar Bear.
---

# Weekly LinkedIn Routine

## When To Use
You sell while delivering, and LinkedIn is the first thing to fall off the week. Use this once a week, ideally the day before your blocked hour, to answer: what has Claude already got ready, and what are the few things only I can do in sixty minutes?

## When Not To Use
If you have not decided what goes out this month, run Content Calendar first; this skill runs one week, it does not plan the month. In a week with no hour at all, apply your skipped-week rule and stop; a rushed post does more harm than a quiet week.

## Inputs
- This week's slot from your Content Calendar, and the Idea Bank entry behind it.
- The threads and call notes you choose from this week; with the Gmail connector I search and read only those, never send.
- Your Personal Voice Guide and do-not-claim list.
- Optional: Google Calendar (listed in the official sales plugin connectors) to find the hour, and a Project (beta) holding the files above.
If you have none of this, I start from the one idea you want to post this week and mark the routine as a first draft.

## Approach
A weekly review routine (a common practice, no single originator) works because the thinking is done before the hour starts, so the hour is spent on the parts that need you. LinkedIn's Professional Community Policies set the rules column: authentic engagement, no automation, no pods. The failure this prevents is opening LinkedIn "to post something", scrolling for forty minutes and closing it with nothing written and no one contacted.

## Workflow
1. Ask three questions: when is your hour this week, which threads or call notes may I read, and how do you want the sixty minutes split across the blocks.
2. Before you sit down, I prepare: two or three candidate ideas from the threads you chose, each with its source; the week's draft from the calendar idea; the AI Tells Check and the Claim and Permission Check on that draft. I never prepare comment text or messages.
3. Block one, the draft: you edit it in your voice and resolve every flagged claim. A claim you cannot back comes out, even if the post gets shorter.
4. Block two, comments: on posts you chose, by people whose work you follow, you write two or three comments with something real to add. No pods, no comment swaps, nothing scheduled.
5. Block three, conversations: from your Warm Conversations List, you write and send one to three notes by hand. Warm before cold.
6. Last five minutes: you post, then add one line per conversation started to your Conversations Log. If time ran out, the draft waits; the comments and notes still count.

## Output Format
```markdown
# Weekly LinkedIn Routine
Week of: [date]  |  Hour: [day and time]

## Ready before you sit down (Claude)
- Candidate ideas: [idea, source] / [idea, source]
- Draft: [title], from Idea Bank entry [idea]
- Checks: AI tells [n flags], claims [n unbacked]

## The hour (you)
| Block | Minutes (yours) | What you do | Done |
|---|---|---|---|
| Draft | [your number] | Edit in your voice, clear every flagged claim, post | [ ] |
| Comments | [your number] | Comment on posts you chose, with something real to add | [ ] |
| Conversations | [your number] | Write and send notes from your Warm Conversations List | [ ] |
| Log | [your number] | One line per conversation in the Conversations Log | [ ] |
Rules: no pods, no scheduled comments, no automation tools, no bulk messages.

## Decision
[You confirm the hour and the draft by [day before the hour]; if the week falls apart, you apply your skipped-week rule.]
```

## Done When
- Everything Claude prepared is marked as prepared, with its source, and every comment, note and post sits in a block you do yourself.
- The hour adds up to sixty minutes in your own split.
- The routine ends with the Conversations Log, not with a look at likes.

## Quality Bar
- Ideas come only from threads and notes you chose; I read nothing else.
- No comment or message text is drafted for you; comments and notes start with you.
- The rules column follows LinkedIn's policies; anything that looks like engagement bait is cut.
- A short week shrinks the draft block, never the checks.
- Claude prepares; you post, comment and message.

## Next
Run flink-conversations-log (Conversations Log) to record what this hour started.

## About the makers

This pack is made by Polar Bear, a consultancy built by ex-McKinsey founders with a dream to make AI work for People, not instead of them. We help our clients build people systems and AI-first ways of working, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…