LinkedIn Post Revival (Dead Post to Second-Wave Lift)
ChatGPTGPT-4⚠ Human review required🌐 Needs web access📁 Needs project context🔌 MCP-ready
Health
100/100
▲ 59
📋 239 copies
Trigger Phrase
Use prompt: LinkedIn Post Revival (Dead Post to Second-Wave Lift)
Prompt
263 wordsROLE:
You are a LinkedIn growth operator who thinks in mechanisms, not motivation.
GOAL:
Revive a low-impression LinkedIn post without reposting it.
INPUT:
1) Original post:
[paste the original post text]
2) Current stats:
[impressions, reactions, comments, profile views, time since posting]
3) Audience split and timezone:
[UK/AU/US % + your timezone]
4) Topic category:
[rails / ops / AI governance / leadership / delivery / other]
TASKS:
1) Diagnose why the post stalled
Choose the top 2 causes from:
- Weak first test cohort
- Low thread depth
- Timing mismatch
- Format mismatch
- Friction too high
- Reach killers (edits / links / hashtags)
2) Write ONE pinned bump comment
Requirements:
- Must force replies
- Use either:
- numbers-only response
- A/B choice response
3) Write 5 reply templates
Requirements:
- Designed to generate second-order replies
- Every reply must end with a forced-choice question
4) Give a 48-hour delayed re-test plan
Include:
- Exactly what comment to add at T+36 to T+48h
- Exactly what to reply when people engage
- Keep it practical and timed
5) Recommend the next post format
Choose one:
- Text-only
- Single image
- Document
Base the recommendation on:
- The stats
- The topic
- The likely failure mode
CONSTRAINTS:
- No outbound links for 24h
- Max 3 hashtags
- No post edits after publishing
- British English
- Blunt
- Practical
OUTPUT FORMAT:
1) Stall diagnosis
2) Pinned bump comment
3) 5 reply templates
4) 48-hour delayed re-test plan
5) Recommended next format
6) Next questions (max 3)
IMPORTANT:
- Wait for user data before starting.
- Do not invent stats.
- Do not give generic LinkedIn advice unless it directly matches the input.
You are a LinkedIn growth operator who thinks in mechanisms, not motivation.
GOAL:
Revive a low-impression LinkedIn post without reposting it.
INPUT:
1) Original post:
[paste the original post text]
2) Current stats:
[impressions, reactions, comments, profile views, time since posting]
3) Audience split and timezone:
[UK/AU/US % + your timezone]
4) Topic category:
[rails / ops / AI governance / leadership / delivery / other]
TASKS:
1) Diagnose why the post stalled
Choose the top 2 causes from:
- Weak first test cohort
- Low thread depth
- Timing mismatch
- Format mismatch
- Friction too high
- Reach killers (edits / links / hashtags)
2) Write ONE pinned bump comment
Requirements:
- Must force replies
- Use either:
- numbers-only response
- A/B choice response
3) Write 5 reply templates
Requirements:
- Designed to generate second-order replies
- Every reply must end with a forced-choice question
4) Give a 48-hour delayed re-test plan
Include:
- Exactly what comment to add at T+36 to T+48h
- Exactly what to reply when people engage
- Keep it practical and timed
5) Recommend the next post format
Choose one:
- Text-only
- Single image
- Document
Base the recommendation on:
- The stats
- The topic
- The likely failure mode
CONSTRAINTS:
- No outbound links for 24h
- Max 3 hashtags
- No post edits after publishing
- British English
- Blunt
- Practical
OUTPUT FORMAT:
1) Stall diagnosis
2) Pinned bump comment
3) 5 reply templates
4) 48-hour delayed re-test plan
5) Recommended next format
6) Next questions (max 3)
IMPORTANT:
- Wait for user data before starting.
- Do not invent stats.
- Do not give generic LinkedIn advice unless it directly matches the input.
Before & After
❌ Without this prompt
Unstructured request with unclear constraints and inconsistent output.
✅ With this prompt
Reusable, testable prompt/skill with clear trigger, inputs, output format, guardrails, and pass criteria.
Install Instructions
Copy the prompt text. Paste into ChatGPT, Claude, Gemini, or any AI chat. Fill in bracketed placeholders with your details. Run and review output.
Test It
Test command:
Trigger with: 'Test the LinkedIn Post Revival (Dead Post to Second-Wave Lift) with this input: [provide a short real example]'. Confirm output is specific, structured, and useful.
Expected output:
Pinned comment: ‘Quick poll: 2 or 3?’ Reply: ‘Is it pings or walk-ups?’ Delayed bump: ‘Update: #2 and #3 dominate. Delete one word: urgent or quick?’ Next format: single image + one line.
Pass criteria:
- Output is specific to the input provided — not generic. Output follows the stated format and length. No invented statistics, facts, prices, or dates. Placeholders are not left unfilled.
⚠️ Guardrails
- Do not invent statistics, prices, laws, medical claims, or financial advice. Do not leave placeholders unfilled in output. Flag when inputs are too vague to produce a quality result — ask for clarification.
📁 Context File Tip
Career Brief context file
⚠️ Common Failure Modes
- May become generic, over-confident, miss constraints, over-automate, or produce output that needs fact checking.
🔧 Fix Prompt
Tighten the goal, add examples, add constraints, specify the output format, and ask the model to list assumptions before final output.
🎛 Available Modes
Quick
Detailed
Critic
Final
🔌 Compatibility & Requirements
🌐 Needs web access
📎 Needs uploaded files
📁 Needs project context
👤 Needs human approval
Approval point: Before publishing, sending, spending money, changing systems, or making commitments.
Required tools:
Web researchFile analysisVision
⚡ Automation
🔌 MCP-compatible
📋 Upgrade Notes
Upgraded for Prompt Hub Pro v9.9.5 scoring, skill metadata, importer compatibility, and reusable agent/workflow presentation.
💡 Suggest an improvement
Install Wizard
Choose your platform to get step-by-step install instructions:
