I need an automation that allows me to post linkedin content weekly but doesnt sound like AI slop and actually gets engagement
What good looks like
- You give it
- A topic, your professional background or angle, and a rough idea of what you want to say that week, typed in plain language.
- It gives back
- A ready-to-post LinkedIn update written in a natural, first-person voice, with a hook in the first line, a short punchy body, and a closing question or call to action that invites real replies.
1 person needs this
Builders
1 of 3 slots takenUp to 3 builders can work on this at once. Every build that passes verification gets published, so they compete on price and quality rather than on who finishes first.
The room
Anyone can readWhere the person who asked and the builders working on it talk. Open to read so you can see whether this is moving before you back it.
Ready to build
Will update whether what i get actually helps with LI engagement
Okay
Only the requester and the builders who have taken a slot can post here.
The spec
- name
- Weekly LinkedIn Post Generator Human Voice
- tool
- generate_linkedin_post
- input
- topic: string — the subject or story for this week's post\nangle: string — your professional background or point of view (e.g. "10-year SaaS founder", "HR consultant who hates corporate jargon")\nraw_idea: string — a few sentences in your own words, as rough as you like\ntone: enum["direct", "reflective", "contrarian", "storytelling"] — optional, defaults to "direct"\nword_limit: integer — optional, max words, defaults to 250
- output
- post_text: string — the full LinkedIn post, ready to copy and paste\nhook_line: string — the first line in isolation, for quick review\ncharacter_count: integer\ncta_type: string — describes the closing device used (e.g. "open question", "poll prompt", "challenge")
- delivery
- Either
Examples
3 of 3 confirmedWhat a build has to handle. For now the builder and the requester agree these between them. Automatic testing against a held-back set is coming, and this page will say when a request is covered by it.
You give it
Topic: hiring slowly saved my company. Angle: early-stage startup founder, 4 years in. Raw idea: we nearly hired a head of sales too early and it would have killed us. Took our time, hired 18 months later, tripled revenue.
It should give back
A post under 250 words with a specific, story-driven first line that does not start with 'I', a body that includes a concrete detail (the 18-month or revenue figure), and a closing question directed at the reader. No bullet-pointed lists of generic advice. No phrases like 'game-changer' or 'delve'.
You give it
Topic: why most team away-days are a waste of money. Angle: organisational psychologist and consultant. Raw idea: people bond over shared struggle not catered lunches. Away-days that actually work involve doing something hard together.
It should give back
A contrarian or direct-toned post with a hook that challenges a common assumption, a concrete claim supported by the angle, and a call to action asking readers to share their worst or best away-day experience. No corporate buzzwords. No em dashes.
You give it
Topic: I almost quit last Tuesday. Angle: freelance designer, 6 years solo. Raw idea: had a nightmare client, three rounds of pointless revisions, felt totally demoralised. Then got a lovely message from an old client out of nowhere and remembered why I do this.
It should give back
A short reflective or storytelling post that feels personal and specific, references the contrast between the bad day and the unexpected message, and ends with something that invites other freelancers to relate or respond. Must not sound like a motivational poster. Must not use the phrase 'journey'.
How it will be checked
By assertions about the result
A build is run against held-back cases and its answer checked by assertions, such as returning the fields the contract promises.
The held-back cases were written when the first builder took a slot, and have not changed since. This is their fingerprint.
50bd49dac7e3884532e40992746b09eb1786a0bdd18288490a0f142ec11383fe