works with Claude OpenAI

built for LinkedIn

Claude can write anything.
It just doesn't know LinkedIn.

Claude already writes well. This plugin adds what a ghostwriter knows about LinkedIn: structure, and a hook people stop for.

Then you write with one command /write

{ template + hook + voice + formatting } all in one pass

Every template and hook in here was built by analysing 10,000 LinkedIn posts by creators the feed keeps rewarding.

Pay once, no subscription Nothing leaves your machine

  • Pay onceOne payment. No seat. No renewal.
  • Free updatesEvery new template, hook and rule ships to you at no extra charge. The library keeps growing.
  • Your machine onlyNo account. No server. No telemetry. Drafts go to your Claude and nowhere else.

The difference

Paste a rough draft. Get the post.

Same Claude both times. The only thing that changed is what it had to build on. Every post on the right follows a named template from the library.

You paste a rough draft and run one command. You pick nothing. This is what comes back.

Your name· rough draft
Freelance designer · with the plugin
Now ·

/write Been freelancing as a designer for 3 years now and a few people asked me about it so thought I'd share.

When I started I charged $35 an hour, working evenings and weekends and still only making about $3k a month on a good month, one month it was $1,100 and I nearly went back to a full time job.

Then a client asked for a fixed price for their whole website instead of hourly, I said $4,000 kind of randomly and they said yes straight away. That project took 2 weeks and made me more than the previous 6 weeks combined. So I started doing fixed price with everyone and stopped tracking hours. Last year I made $94k working maybe 25-30 hours a week.

I think hourly pricing kind of punishes you for getting faster at your job which is backwards. Anyway hope this helps someone, happy to answer questions.

3 No comments
Like Comment Repost Send
Your name· 1st
Freelance designer
Now ·

Three years into freelance design, I was charging $35 an hour, working evenings and weekends, and topping out around $3,000 on a good month.

One month it was $1,100. I nearly went back to a full time job.

Then a client asked for a fixed price on their whole website instead of hourly. I said $4,000, kind of randomly. They said yes straight away.

The project took two weeks and paid more than the previous six weeks combined.

I stopped tracking hours and started quoting fixed price with everyone after that.

Last year I made $94k, working maybe 25 to 30 hours a week.

The turning point wasn't a plan. It was a random number a client agreed to right away. Hourly pricing punishes you for getting faster at your job. That's backward.

Template: The Turning Point Timeline | Hook: Contrast

Cut both throwaway lines, split the six-line paragraph into single beats, and moved the $1,100 month up to line two.

128 written by Claude + Creator DNA
Like Comment Repost Send

Brief: “Write a LinkedIn post about what we learned hiring our first senior engineer.”

Claude· on its own
Same brief, no plugin
Now ·

/write We just hired our first senior engineer. Here's what we learned along the way.

**1. Seniority isn't about years — it's about judgment.**
We started by filtering on tenure. The best candidate we interviewed had less experience on paper but consistently asked better questions.

**2. The take-home told us less than the conversation about it.**
What mattered wasn't the solution — it was how they talked through the tradeoffs.

**3. Culture add > culture fit.**
We didn't need someone who thought like us. We needed someone who'd challenge how we think.

The biggest lesson? Hiring senior isn't about finding someone who has all the answers — it's about finding someone who asks the right questions.

If you're making your first senior hire, I'd love to hear what you learned. 👇

3 No comments
Like Comment Repost Send
Your name· 1st
Founder
Now ·

Last spring: 40 candidates for one senior engineering role.

Then our highest scorer turned us down, and our lowest scorer sent a note.

I had two options:

A. Go back to the top of the pile and move faster.
B. Interview the person who failed the take-home.

I chose B.

Immediately, three people on the panel told me I was wasting a slot.

By December, she had rewritten the service that take-home was based on.

The decision worked because her note explained what she got wrong and what she would do differently.

Not because we got lucky on a hunch.

Template: The Decision Fork | Hook: Time-marked open loop

Fits because the brief holds one real choice with a cost either way. The note from the lowest scorer is the anchor.

128 written by Claude + Creator DNA
Like Comment Repost Send

Brief: “A post about realising I was the bottleneck on my own team.”

Claude· on its own
Same brief, no plugin
Now ·

/write I recently realized something uncomfortable: I was the bottleneck on my own team.

Not because I wasn't working hard enough — I was working harder than ever. But every decision, every review, every approval ran through me.

Here's what that actually looked like:

→ PRs sat waiting for my review
→ My team stopped making calls without checking first
→ "Let me ask him" became the default

The hard truth? I'd built a system where I was indispensable — and that's not leadership. That's a single point of failure.

So I started letting go. Not all at once, but deliberately.

The result: the team moved faster, made better decisions, and I finally had time to think about what's next.

Sometimes the most valuable thing a leader can do is get out of the way.

Have you ever been the bottleneck? How did you notice?

3 No comments
Like Comment Repost Send
Your name· 1st
Founder
Now ·

For two years I avoided admitting I was the bottleneck on my own team.

My explanation:

“I'm the only one who knows this system well enough to review it.”

The real reason:

I was afraid of what I'd be worth if I wasn't the person everything went through.

Then I took nine days off for my sister's wedding and came back to 40 merged pull requests.

I could no longer ignore that the team shipped faster without me in the middle.

So I stopped reviewing every pull request.

I started writing down the three things I was actually checking for.

Review time dropped from two days to four hours.

Nothing outside me had changed.

I had changed what I thought my job was.

Template: The Honest Admission | Hook: Confession

Fits because the story turns on something the writer avoided saying. Nine days off and 40 merged PRs make it concrete.

128 written by Claude + Creator DNA
Like Comment Repost Send

Brief: “Share what our last 90 days of LinkedIn posting actually did.”

Claude· on its own
Same brief, no plugin
Now ·

/write 90 days ago, we committed to posting on LinkedIn consistently. Here's what actually happened.

**What we did:**
Posted 3–4 times per week, mixing thought leadership, behind-the-scenes, and team highlights.

**What worked:**
Personal stories outperformed everything else — by a wide margin. Posts with a clear point of view got significantly more engagement than announcements.

**What didn't:**
Product updates. Nobody cares about your feature release unless you tell them why it matters.

**The biggest surprise:**
Consistency mattered more than polish. Our "rougher" posts often did better than the ones we spent hours on.

The takeaway? LinkedIn rewards showing up — not showing off.

What's been your biggest learning from posting consistently? Would love to hear in the comments 👇

3 No comments
Like Comment Repost Send
Your name· 1st
Founder
Now ·

Our LinkedIn page, 90 days: the numbers

Posts published: 47
What it suggests: volume was never the problem

Median impressions: 2,100
What it suggests: the feed is showing the work to a real audience

Profile visits from those posts: 31
What it suggests: almost nobody wanted to know who wrote them

SIGNAL

We were writing posts people finished and forgot.

DECISION

Stop measuring impressions.

Start measuring profile visits per post.

Template: The Data Snapshot | Hook: Stat drop

Fits because the brief is three numbers and a decision. Each number gets a one-line reading, then the call.

128 written by Claude + Creator DNA
Like Comment Repost Send

Nothing about the model changed. The second Claude had a structure to build on, a hook pattern to open with, and a list of the words it is not allowed to use.

Who it's for

Built for whoever has to ship the post.

Two kinds of people buy this. Both are tired of fixing the same draft.

Under your own name

Founders, operators, consultants.

You have the stories. You do not have an hour to shape each one. Type what happened and get a post that sounds like you and reads like a pro built it.

  • Paste three of your old posts and it writes in your voice
  • Swap the hook or the structure without redoing the whole thing
  • Plain text, ready to paste, every time
For clients

Ghostwriters, copywriters, agencies.

One writing standard across every account, instead of a house style that lives in your head. Faster first drafts. Same quality at client twelve as at client one.

  • Works out brand voice or personal voice before it drafts
  • Never invents a stat, a quote or a moment the client did not give you
  • Writes in the client's language. Dutch, Spanish, German, Portuguese, anything
  • Client drafts never leave your machine. There is no server to leak from

Same $79 whether it is one name or twelve clients.

Under the hood

What Claude reads before it writes a word.

Every template started as a pattern that kept showing up across 10,000 LinkedIn posts by creators the feed keeps rewarding. We wrote down why each one works and what the feed does with it. Then we made Claude follow it.

Your brief

“Write a post about our hiring mistake.”

The plugin loads
  • A hook pattern picked to land the point
  • A post template matched to the story
  • The writing rules anchors, no hedging, no jargon
  • The formatting pass plain text, mobile spacing
Paste-ready post

Plain text you paste straight into LinkedIn. Nothing to clean up, nothing to reformat.

Ways to open picked for the point you are making

a bold claima then-and-now contrasta number that stops the scroll a question they cannot skip a scene from the storyan admission a loop they have to close

Structures to build on matched to the story you have

a decision you madea mistake you owna conversation that changed something a before and aftera myth and what is trueone thing that led to the next an objection answereda real example taken apart a number read out a checklist to self-diagnosea turning point two kinds of peopleone action swapped for another a term redefineda bigger question an if-then choicea milestone debrief a step-by-step playbooka quick reset root causes counted downa framework with a name evidence and a forecasta resource drop

every template and hook that proves itself gets added. every buyer gets every addition. free.

The writing rules

Anchor in line one. No hedges. Say each fact once. One earned closer. Nothing invented, ever.

The formatting pass

Plain text. Mobile spacing. The hook sits above the see-more fold. No stray formatting, no em dashes. Runs last on every post.

Voice handling

Brand voice or personal voice, worked out before drafting. Give it a few of your posts and it writes like you. Any language.

Six commands

Type a slash. Get a ghostwriter.

They also fire on their own. Ask for a post and Claude picks the right one.

/write

A finished post from your topic. Picks the hook and template for you.

/swap-hook

Keeps the post, replaces the opening line with a stronger pattern.

/swap-template

Same message, rebuilt on a different structure.

/format

Fixes spacing, breaks and punctuation. Changes nothing you said.

/list-hooks

Browse every opening pattern and pick one yourself.

/list-templates

Browse the whole template library before you draft.

One price

One payment. Yours to keep.

Not a subscription. Not a seat. A folder of files that lives on your machine and gets better for free.

early bird

$99 regular

$79USD, once

A LinkedIn ghostwriter costs more than this every week. The launch price holds until the next template set ships.

Get the plugin for $79
  • The full template library. Each one with its intent, skeleton, hook mechanic and a worked example.
  • Every hook pattern. With the mechanic that makes it land.
  • The writing rules. Anchors, no hedging, no filler, voice handling.
  • The formatting pass. Plain text, mobile spacing, no bold unicode, hashtag and emoji limits.
  • Six commands. Write, format, swap hook, swap template, list hooks, list templates.
  • Both tools. Claude Code plugin and Codex skills. Same source. One download.
  • The install guide. Step by step for both tools. Inside the download.
  • Free updates. Every new template, hook and rule as it ships. No extra charge.

Your drafts never reach us

There is no account and no Creator DNA server in this product. The files sit in your plugin folder. Your drafts go to your own Claude and nowhere else.

Updates you pull, never pushed

When a new version ships you download it from the same link you bought with. We never ping your machine and we never see that you did.

You'll need Claude Code or Codex

This is a plugin, not a writing app. It runs inside a Claude Code or Codex setup you already pay for. If you don't have one, get that first.

Install

Three lines. Under a minute.

You get a download link the moment you buy. Paste these into Claude Code and you are done.

Claude Code
> /plugin marketplace add ~/li-skills/claude
> /plugin install li@li-skills
> /reload-plugins

Then type /write in any project. On Codex it is one copy step, and the download walks you through it.

Before you buy

The questions worth asking.

What exactly am I downloading?

Plain Markdown files and one small Node script. No binaries, no background process, nothing hidden. You can read every line of what you bought before you install it. Most buyers should.

Does any of my data leave my machine?

No. There is no account, no login and no telemetry. There is no Creator DNA server in this product at all. Your brief and your draft go to your own Claude or Codex, the same as any other prompt you send them. We never see either. We could not copy your data if we wanted to.

Is it really one payment?

Yes. $79 once. No renewal, no seat. The price rises to $99 when the next template set ships. Buy before that and you never pay the difference.

What do the free updates include?

Every new template as it proves itself. Every new hook as the old ones wear out. New commands as they ship. You re-download from your original link. Nothing to renew.

I write for clients. Does this work for that?

It was built for that. It works out whether it is writing as a brand or a person before it drafts. It never invents a stat, a quote or a moment the client did not give you. It writes in the client's language. And nothing leaves your machine, so there is no client draft sitting on someone else's server.

Can't I just prompt Claude to do this myself?

You can. The left-hand post in every example above is what you get. The difference is a library of tested structures and hook mechanics that took a lot of bad drafts to write down. You are buying the part that took the time, not the part that takes the prompt.

How do I install it?

A download link arrives the moment you buy. Inside is an install guide for Claude Code and for Codex. Three commands for one, two for the other. Under a minute either way. If you get stuck, email us and we will walk you through it.

Why only LinkedIn?

Because the LinkedIn feed has its own rules. What gets shown and what gets buried, where the see-more fold lands, how long a hook has to earn the click. Every template, hook and formatting rule here is tuned to that on purpose. Going wide would make it shallow.

Who should not buy this?

Anyone without Claude Code or Codex, anyone who wants a scheduler or an analytics dashboard, and anyone looking to auto-post. This writes one post at a time and hands it to you. It does nothing else.

Your next post, without the blank page.

$79 at the early-bird price. No subscription. Updates included.