Pinned Comment

LinkedIn Pinned Comment + Image Prompt Skill

Codex and Claude runtime

• Use this skill in Codex or Claude with the tools actually available in the current task. AskUserQuestion examples describe the questions, not a required API: use an available question tool within its limits, or ask in chat. Reuse answers and source material already supplied.
• Work in the user-selected project. Read its about-me.md, voice.md and relevant brand files before personalised work. Confirm the intended author if files conflict or contain starter defaults. Ask for missing facts or run voice-builder; never inherit the maintainer's identity, accounts or private files.
• Resolve bundled references/ relative to this skill folder. For an explicitly requested profile refresh, read and update the canonical about-me.md, voice.md or newsletter-voice.md in place, preserving unrelated user facts and rules. Consumers must reread those canonical files. Use a new filename only for new deliverables that would collide with unrelated existing files. Installation alone never starts an interview or writes files. Do not write persistent learnings unless requested.
• Use supplied evidence first. Verify external claims through available search/source tools when needed. If a source or integration is unavailable, name the missing capability and offer supplied text/export input. Never invent facts, first-person experience, metrics or a successful tool run.
• Connect only services needed for the chosen route through the user's existing account. Never print credentials or overwrite connections. Drafting, saving and reviewing do not authorise publishing, sending messages or changing accounts.

Visual completion state

This skill's image prompts are prompt-ready, not generated or visually reviewed assets. Keep its named Gemini workflow unless the user requests another generator. A missing image service does not block writing a prompt. When images are supplied or generated, open and inspect each export at full size and feed size (about 360px wide, 320px for thumbnails). Check exact copy, dimensions, clipping, legibility, brand colours, font appearance, logos and reference fidelity. Fix and re-inspect failed exports. Record any unavailable export or inspection as pending. An image prompt or raster export is not an editable design file.

Why This Skill Exists

The post delivers value. The pinned comment builds personality, trust, and rewatch value. It gives the author room for a real, self-deprecating aside.

Funny is subjective and easy to miss. This skill exists to make hilarious pinned comments REPEATABLE from the author’s own context.

The Core Insight (read this first)

The image carries the joke. The comment captions the image.

If the comment makes sense without the image, the comment is doing too much work. If the image needs the comment to be funny, the image is too weak.

Develop the image prompt first. Actual generation is separate and must not be claimed from a prompt alone.

THE PROCESS (follow in order)

Step 1. Find the admission

Read the supplied post and author context. The examples below are fictional creative patterns, not facts about the user. Do not invent an admission or imply sponsorship, dependence or personal experience that the user has not supplied.

Every the author post hides one quiet confession. Examples:

• "Cowork does most of my actual job now"
• "I am embarrassingly dependent on Anthropic"
• "I gave away a 9-month product for free"
• "I am a sponsored creator who lost objectivity"

Write the admission as one sentence before doing anything else. If you cannot name the admission in one sentence, stop. The post is not pinned-comment material yet.

Step 2. Build the image first

Three rules for the image:

1. One clear visual gag. The eye lands on it in under a second. Examples that worked: tie draped on a laptop keyboard, a shrine to Anthropic with a rose and candles, a banquet table where every other seat is a tech logo.
2. Played completely straight. No winking. No thumbs up. No exaggerated faces. The humour comes from treating the absurd as normal.
3. The author is the lower-status figure. Always. Claude wins. The logo wins. The mum wins. The author loses with quiet dignity.

Use the standard format:

"Using the person in the attached reference image, create a photorealistic image of [scene]. [One clear visual gag described in detail]. [the author's posture and expression, played straight]. [Lighting and framing notes]."

Step 3. Caption the image with the 4-line comment

The comment names what the image shows as if reporting the news.

Fixed structure:

📌 [Line 1: Describe the absurd thing as normal fact]
[Line 2: Flip the author's status downward]
[Line 3: A sad flex, the smallest possible win]
[Line 4: Resigned acceptance, no punchline reach]

Step 4. Run the 5 tests before sending

1. Image gag test. Can you describe the visual gag in 5 words? If not, the image is too busy. Simplify.
2. Caption test. Does line 1 caption the image as fact? If line 1 sets up a separate joke, rewrite.
3. Loser test. Is the author the lower-status figure in every line? If he wins anywhere, rewrite.
4. Reach test. Does line 4 try too hard for a punchline? If yes, make the line smaller and sadder. Resigned beats clever.
5. Boring-on-its-own test. Read the 4 lines without the image. Is the comment boring alone? Good. That means the image is doing the heavy lifting.

If any test fails, fix before sending.