When the user wants to create LinkedIn post copy or optimize for LinkedIn. Also use when the user mentions "LinkedIn post," "LinkedIn article," "professional post," "post to LinkedIn," "LinkedIn content," "LinkedIn copy," "B2B LinkedIn," "LinkedIn engagement," "LinkedIn feed," "share box," "document post," "poll," "Newsletter," "reshare," or "LinkedIn marketing." For LinkedIn ads, use linkedin-ads.
SkillScore91Maintained
Automatic
◆Marketing & Content pack
Last verified 8/21/2026
What it changes
Passed 20 of 22 test cases with the skill, and 11 of 22 without it.
Without skill50%
With skill91%
Checks it passed that the model alone missed
Includes image or document asset specifications.
States the maximum image file size limit is 10 MB.
Provides full post text with explicit character count.
and 8 more in the full report
9 fixed11 passed either way2 still failing0 broke
Pass-rate lift
+41 pp
Tokens
+78%
Agent turns
0%
Response time
-15%
Model gemini-3.6-flashMeasured 8/21/2026v120 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 9
Prompt
What are the recommended dimensions for a square image upload on LinkedIn, and what is the maximum file size limit for native image posts?
What was checked, without and with the skill
Checked
Without skill
With skill
Specifies 1200x1200 pixels for square images.
Passed
Passed
States the maximum image file size limit is 10 MB.
Missed
Passed
case-05 · gemini-3.6-flash · 8/21/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md96 linessingle file
|----------------|
| Start a post | Short update; can include link preview if you paste a URL. Same feed format as other updates. |
| Photo | Single or multiple images (carousel in feed). |
| Video | Uploaded file (distinct from LinkedIn Live, which is live streaming and has separate gating). |
| Write article | Article = long-form editor, separate from the short post box; long URL, better for depth and some off-site discoverability. |
| Document | PDF / PPT / DOC (slides in feed). Official limits (check current help): on the order of ~100MB / ~300 pages per file—verify when publishing. |
| Poll | Engagement driver; keep question and options scannable. |
| More (menu) | Often includes celebrations, hiring-style share, Find an expert, etc. (varies by product/region). |
| Reshare | Reshare or quote another member’s post with your take—adds context; avoid empty reshares. |
| Newsletter | Series subscription; not the same as a one-off post but compound reach over time. |
| Event | Create/promote events via a dedicated flow, not the same as a plain text post. |
Why it matters for copy: Match CTA and length to the form (e.g. a document deck vs a 5-line hot take). Do not treat a short post and an Article as interchangeable.
How the Feed Ranks (what to write for)
The feed is not a pure reverse-chronological friend list. It blends 1st-degree connections, follows, company/topic interest, and recommended “out of network” content from the Economic Graph, plus ads. How the Feed ranks content
Relevance uses context of the post, profile and network signals, and behavior (read, react, comment, share, dwell). Demographics like age or gender are not used to rank feed visibility (per public help guidance).
Platform direction in recent public communications: more LLM/semantic understanding, less inauthentic engagement and engagement-bait / low-quality repetition; favor real expertise and meaningful discussion. Background on feed engineering (blog)
Writing implications: Strong first line and on-topic depth; comments that add substance; avoid templates that look automated or “pod” coordinated.
Off-Site SEO and GEO (brief)
Short feed posts are often login-gated for crawlers; do not assume every post is indexed on Google like a blog post.
Public profile, Company Page, and Articles (where public) are stronger for name/company/role style queries. Align headline, about, and entity names with your site and other public bios for E-E-A-T-style consistency.
GEO (AI/search answers): one clear, quotable line who you help + links to evidence (site, case study, talk) in profile or long-form, not only in DMs or groups.
For link previews on social: open-graph; for people/org entities: entity-seo; for generative/AI search strategy: generative-engine-optimization.