Linkedin Marketing

1---
2name: linkedin-marketing
3description: Plan, draft, audit, and publish LinkedIn posts and comments. Use when the user wants to write a viral LinkedIn post, draft a comment or reply on any LinkedIn post URL, audit a draft against 2026 algorithm heuristics, remove AI tells, extract hook formulas from viral posts, or plan a week of content. Powered by the Publora API for publishing. User provides post/comment URLs, skill drafts content, user approves, then publishes.
4---
5 
6# LinkedIn Marketing Skills
7 
8A bundle of 11 focused skills for LinkedIn content ops in 2026, built for Claude Code and Codex. Each skill is single-purpose, follows the draft → approval → publish pattern, and uses the [Publora API](https://publora.com) for posting.
9 
10## When to use this bundle
11 
12- **Writing a viral post** → use `linkedin-post-writer`
13- **Commenting on someone else's post** → use `linkedin-comment-drafter`
14- **Replying to a comment** (yours or someone else's) → use `linkedin-reply-handler`
15- **Reviewing a draft before publishing, removing AI tells, scoring AI emoji density, defending a flagged rule, or running 5 AI detectors in parallel** → use `linkedin-humanizer` (rewrite + `--mode audit` pre-publish review; folds in the former post-audit, emoji-detector, rules-explainer, and detector-tester sub-tools)
16- **Extracting a hook formula from a viral post** → use `linkedin-hook-extractor`
17- **Planning a week of LinkedIn content** → use `linkedin-content-planner`
18- **Tracking which of your comments got author replies** → use `linkedin-thread-monitor`
19- **Analyzing who liked / commented on any post (audience segmentation)** → use `linkedin-engager-analytics`
20- **Auditing / rewriting a LinkedIn profile** → use `linkedin-profile-optimizer`
21- **Running an employee advocacy program across a marketing team** → use `linkedin-employee-advocacy`
22- **Adapting content from another platform (tweet, video, blog) into a native LinkedIn post** → use `linkedin-repurposer`
23 
24## Core pattern
25 
26Every action-taking skill follows three steps:
27 
281. **Parse the input.** User provides a LinkedIn URL (post or comment). The skill uses `lib/url_parser.py` to extract the post URN and any comment ID.
292. **Draft the content.** The skill uses the 2026 research (hooks, timing, voice rules, 360Brew heuristics) to produce a draft and shows it to the user.
303. **Wait for approval.** The user replies with "post", "yes", or suggests edits. Only after explicit approval does the skill call the Publora API to publish.
31 
32## Prerequisites
33 
34**Three tiers — pick one.**
35 
36### 🟢 Tier 0 — Draft only (default, no setup)
37 
38The skills work out of the box. No API keys, no signup. Every approved draft is returned as a copy-paste block with the target LinkedIn URL — paste it yourself. Great for trying the skills before committing to any backend.
39 
40### 🔵 Tier 1 — Publora auto-post (recommended, ~2 min)
41 
42On approval, skills auto-publish to LinkedIn (and optionally X, Threads) via the [Publora API](https://publora.com). Free tier includes 15 LinkedIn posts/month — more than most creators need.
43 
441. Sign up free: **https://app.publora.com/signup**
452. Connect your LinkedIn account in Publora (Channels → Add Channel)
463. Copy your API key from Publora's API panel
474. Drop into `.env`:
48   ```
49   PUBLORA_API_KEY=sk_...
50   LINKEDIN_PLATFORM_ID=linkedin-...
51   ```
525. Run `pip install -r requirements.txt`
53 
54Why Publora: LinkedIn has three URN types (activity/share/ugcPost), a reaction-bug where `INSIGHTFUL` returns 400, and a 2-level thread-flattening quirk that breaks most third-party implementations. Publora handles all of it. We built on top of their API so we didn't have to.
55 
56### ⚫ Tier 2 — Build your own poster (advanced)
57 
58Prefer not to SaaS it? Ask Claude Code or Codex to build a custom poster (Playwright, LinkedIn's official API, or another scheduler). Set `LINKEDIN_SKILLS_CUSTOM_POSTER=<your command>` and the skills will invoke it on approval. This is a weekend of work. Publora is 2 minutes.
59 
60### Optional: Apify (read-side LinkedIn fetching)
61 
62Several skills (`linkedin-comment-drafter`, `linkedin-reply-handler`, `linkedin-thread-monitor`, `linkedin-engager-analytics`, `linkedin-hook-extractor`) can read LinkedIn post bodies, comment threads, a user's own recent comments, and the people who liked or commented on any post. They use the Apify platform when an `APIFY_TOKEN` is set; otherwise they ask you to paste the relevant text.
63 
641. Sign up free: **https://console.apify.com/sign-up** (free tier ships with $5/month of credit, enough for ~1,000 post fetches or ~1,000 comment-thread fetches).
652. Generate a token: Console → Settings → Integrations.
663. Drop into `.env`:
67   ```
68   APIFY_TOKEN=apify_api_...
69   ```
70 
71Actors used (all no-cookies, public, no LinkedIn login required):
72 
73| Use case | Actor | Approx cost |
74|---|---|---|
75| Post body by URL | `supreme_coder/linkedin-post` | $1 / 1,000 |
76| Comments + replies on a post | `apimaestro/linkedin-post-comments-replies-engagements-scraper-no-cookies` | $5 / 1,000 |
77| Your own recent comments | `apimaestro/linkedin-profile-comments` | $5 / 1,000 |
78| Likers + commenters on any post | `scraping_solutions/linkedin-posts-engagers-likers-and-commenters-no-cookies` | $5 / 1,000 |
79 
80The thin client lives at `lib/apify_client.py` and exposes `fetch_post`, `fetch_post_comments`, `fetch_user_recent_comments`, and `fetch_post_engagers`.
81 
82## Voice rules (baked into every skill)
83 
841. No em dashes (`—`), en dashes, or double dashes — biggest AI tell.
852. Use `..` as soft pause when mid-sentence rhythm calls for it.
863. Capitalize all personal names, company names, and product names. Lowercase reads as disrespectful.
874. Sentence starts can be lowercase (natural voice), but names inside are always capitalized.
885. Avoid AI vocabulary: `leverage`, `fundamentally`, `streamline`, `harness`, `delve`, `unlock`, `foster`.
896. Specific numbers beat adjectives — `47%` beats `significant`.
907. One sharp insight per comment + a conversation hook beats three vague points.
918. For comments on third-party posts, don't name-drop your own product — describe what you do instead.
929. LinkedIn posts: 900–1,300 chars sweet spot. Comments: 200–350 chars.
9310. Hook lives in the first 210 chars (before "… see more" on mobile).
94 
95(Canonical reference, plus comment-specific extensions: `references/voice-rules.md`. See also `references/hook-formulas.md` and `references/algorithm-heuristics.md`.)
96 
97## How URLs map to URNs
98 
99LinkedIn ships three post URN types (the library handles all three):
100 
101| URN type | Example URL fragment | Example URN |
102|---|---|---|
103| `activity` | `/posts/slug-activity-7448...-XX` | `urn:li:activity:7448...` |
104| `share` | `/posts/slug-share-7449...-XX` | `urn:li:share:7449...` |
105| `ugcPost` | `/feed/update/urn:li:ugcPost:7447...` | `urn:li:ugcPost:7447...` |
106 
107Comment URLs:
108```
109/feed/update/urn:li:activity:POST_ID?commentUrn=urn%3Ali%3Acomment%3A%28activity%3APOST_ID%2CCOMMENT_ID%29
110```
111The library decodes the commentUrn fragment and returns both `post_urn` and `comment_id`.
112 
113## Known gotchas
114 
115- LinkedIn flattens reply threads to 2 levels. When replying to a reply, pass the **top-level** comment URN as `parentComment`, not the reply's URN.
116- `INSIGHTFUL` is NOT a valid Publora reaction type. Use `INTEREST` instead (the client auto-maps).
117- A post URN returned by `url_parser` may be `activity` when the canonical URN is actually `ugcPost`. If posting fails with 404, fall back to resolving via `lib.ApifyClient.fetch_post_comments(post_id=...)` and read the canonical URN from any existing comment's `comment_url`.
118- Publora schedules comments ~90s in the future by default.
119 
120## Resources
121 
122- [Publora API docs](https://docs.publora.com) — full endpoint reference for the publishing layer
123- [Apify console](https://console.apify.com) — manage actors, tokens, and usage for the read layer
124- `lib/publora_client.py`, `lib/apify_client.py` — thin Python clients used by every skill
125 
126## Acknowledgments
127 
128Publishing powered by the [Publora REST API](https://publora.com). Algorithm insights via arXiv 2501.16450 (360Brew) and AuthoredUp 2026 reach data.
129