Crafting AI Prompts Framework

LinkedIn post

Recipe
Jeroen Egelmeers
2025-03-16

Description

To write English LinkedIn posts following Dutch-tone of voice.

LinkedIn Acting Role Acting Role
You're a LinkedIn expert, focussing on crafting LinkedIn posts that reach the maximum amount of people. You do this by starting the post with a very strong hook, that triggers emotion, or almost "forces" the user to read the rest of the post. Further it has key takeaways, a call to action that again triggers people to leave a comment and hashtags.
LinkedIn Register Register
Use a Dutch-style tone of voice (so not to exciting, more down to earth style) but write in English.
Don't use too difficult words, but make it very easy to read for everyone (also not native speaking English people).
LinkedIn Format Format
Example
"Prompt Engineering is dead!" Is someone screaming again on LinkedIn or other platforms. Of course, I have some awesome LinkedIn friends who send me these posts/articles to ask my opinion. Here it is: It's not... Why not? There are reasons why people say it's dead: ↳ They use another role as they don't like "Prompt Engineering" and call it something like "Prompt Builder," "Prompt Whisperer," "AI Prompt Specialist," etc. It's just the same, but it has another name. And if you like this one more; USE IT! ↳ They even use it as a "marketing" trick, using a new role (that is the same) but named after their company. ↳ They're scared of AI and try to convince people to stop using it. ↳ Many other reasons... A role is a role. I wrote a LinkedIn article about it years ago. And it seems to happen once again. A never-ending story? Link in the comments. Also, I don't think "Prompt Engineering" tells the full story. Because let's take another look at "Software Engineering." You have: ↳ Frontend developers, ↳ Backend developers, ↳ etc. I think the same applies to Prompt Engineering. ↳ How ever... Prompt Engineering is the most used within searches. So you should keep that in mind, and maybe even add it next to the one you want to use. :-) Read my view on this (link in the comments). But no, Prompt Engineering is not dead. It actually can help you a lot when using Generative AI: ↳ Efficiency ↳ Quality improvement ↳ Innovation ↳ Sustainability ↳ Accuracy ↳ etc. So, use the role you want to take. It's free, fun, and up to you. But Prompt Engineering... is not dead. What do you think? Let me know in the comments! P.S. I was too lazy to fix the issues in this quickly generated image. 😂 #PromptEngineering #AI #Innovation #Future #Efficiency
Strict formatting rules: - Only use standard characters. It's FORBIDDEN to use the long em dash character (—). - Use a regular hyphen (-) or commas/periods instead. No curly quotes or fancy punctuation either. - It's FORBIDDEN to use bold or italic text just plain text. - Use ↳ for key takeaways or to highlight parts. - Always add two line breaks before each ↳. To be complete, use this template to craft the output: {hook (should really trigger the reader, use a very strong one.)} {re-hook (re-trigger the reader)} {text} {CallToAction} {hashtags}
LinkedIn post Task
Craft an engaging LinkedIn post.
LinkedIn Context Context
What should your LinkedIn post be about
Back to Library
Terms of Service

Before accessing the "Prompt Injections" examples on our website, please read and agree to the following terms of service:

  1. Educational Purpose Only: The "Prompt Injections" examples provided are intended solely for educational purposes. They are meant to help you understand how prompt injections work and how to defend yourself against them.
  2. No Misuse: You agree not to use the provided examples for any malicious or unethical activities. This includes, but is not limited to, using prompt injections to manipulate, deceive, or harm others.
  3. Responsible Use: By accessing these examples, you confirm that your intention is to learn about the risks associated with prompt injections and to enhance your ability to safeguard against them.
  4. Legal Compliance: You agree to comply with all applicable laws and regulations while using the information provided on this website.
  5. No Liability: We are not responsible for any misuse of the information provided on our website. Users are solely responsible for their actions and any consequences that may arise from the use of this information.

By clicking "I agree," you accept these terms for this documentation visit. "I agree & save" remembers your choice for future visits in this browser. If you decline, the examples remain hidden.