ApprovedMarketinglinkedinsocial-media
Professional-network post from a real experience
PL by Prompier Library
☆☆☆☆☆ New
Version 1 · updated Nov 10, 2026
Reviewed by moderator Prompier Library on Nov 10, 2026. Checked for personal data, secrets, risky instructions and a clear license.
About this prompt
Interviews you briefly, then writes a short, mobile-friendly professional-network post based on what you actually built or learned. Use when you want a post that sounds human, not corporate.
Prompt text
You help me write a professional-network post that is grounded in something real I did or learned.
Inputs
- What I did, built or learned: {{experience}}
- Why it matters and to whom: {{why_it_matters}}
- Result, struggle or surprise worth sharing: {{insight}}
- Intention (educate, share news, inspire, invite conversation): {{intention}}
- Maximum length in words: {{max_words}}
Steps
1. Check the inputs. If the concrete detail is thin, ask 3-5 short questions about the problem, the turning point and any specific number before writing anything. If the inputs are rich, skip the questions.
2. Choose one main message. A post that makes one point beats one that makes four.
3. Write the hook: one line, under 12 words, that creates curiosity without clickbait.
4. Write the body in short lines with blank lines between small groups of lines, easy to read on a phone. Use simple words and active voice.
5. Include one concrete detail (a number, a moment, a mistake) taken only from my inputs.
6. End with a single genuine question or invitation.
7. Offer two alternative hooks.
Output format
- The post, ready to paste
- Two alternative opening lines
- A one-line note on anything you left out or assumed
Quality bar
- Do not invent results, quotes, customers or statistics.
- No buzzwords, no hashtags stuffing (at most 3 at the end if I ask), no emoji unless requested.
- Stay under the word limit.
- Sound like a person talking to a colleague.
Variables
5 variables| Variable | What to enter | Example | Default |
|---|---|---|---|
| {{experience}} | What you did, built or learned | Ran our first customer workshop after years of only doing webinars | — |
| {{why_it_matters}} | Why it matters and to whom | Other small B2B teams who struggle to get honest product feedback | — |
| {{insight}} | The result, struggle or surprise worth sharing | Only 12 people came, but we got more useful feedback than from 300 survey answers | — |
| {{intention}} | What the post should do: educate, share news, inspire or start a conversation | Start a conversation | — |
| {{max_words}} | The longest the post may be, in words | 200 | — |
Try it
Live previewWhat you did, built or learned
Why it matters and to whom
The result, struggle or surprise worth sharing
What the post should do: educate, share news, inspire or start a conversation
The longest the post may be, in words
Your finished prompt
You help me write a professional-network post that is grounded in something real I did or learned.
Inputs
- What I did, built or learned: {{experience}}
- Why it matters and to whom: {{why_it_matters}}
- Result, struggle or surprise worth sharing: {{insight}}
- Intention (educate, share news, inspire, invite conversation): {{intention}}
- Maximum length in words: {{max_words}}
Steps
1. Check the inputs. If the concrete detail is thin, ask 3-5 short questions about the problem, the turning point and any specific number before writing anything. If the inputs are rich, skip the questions.
2. Choose one main message. A post that makes one point beats one that makes four.
3. Write the hook: one line, under 12 words, that creates curiosity without clickbait.
4. Write the body in short lines with blank lines between small groups of lines, easy to read on a phone. Use simple words and active voice.
5. Include one concrete detail (a number, a moment, a mistake) taken only from my inputs.
6. End with a single genuine question or invitation.
7. Offer two alternative hooks.
Output format
- The post, ready to paste
- Two alternative opening lines
- A one-line note on anything you left out or assumed
Quality bar
- Do not invent results, quotes, customers or statistics.
- No buzzwords, no hashtags stuffing (at most 3 at the end if I ask), no emoji unless requested.
- Stay under the word limit.
- Sound like a person talking to a colleague.
Sample output
We almost shipped a feature nobody asked for.
Last month our team spent two weeks on a reporting screen.
Then we showed it to five customers.
Four said they only wanted the data sent to them by email.
So we scrapped the screen and built the email in three days.
The lesson for me: show a rough version before you build the polished one.
What is the cheapest way you test an idea before building it?
Alternative openings:
- Two weeks of work, deleted in an afternoon.
- I was wrong about what customers wanted.
Note: I did not name the customers or the product.
An example the author shared. Your result will differ.
Reviews
No written reviews yet. If you have used this prompt, tell others how it went.
0 forks
Public forks of “Professional-network post from a real experience” by Prompier Library (v1).
Lineage: Original prompt → this prompt → 0 forks
No forks have been shared publicly yet.