LinkedIn Thought Leadership & Growth Post

What it does

/linkedin-post is a Cursor slash command. Type it in chat to run a saved workflow: LinkedIn Thought Leadership & Growth Post.

Formats high-engagement LinkedIn posts: craft scroll-stopping hooks, share transparent build-in-public lessons, and drive traffic to blog posts.

Build-in-public updates, founder lessons, metrics, and engagement hooks. Unlike a skill, a command is something you invoke on purpose. The agent does not decide to run /linkedin-post for you.

Why it exists

Founders retype the same multi-step prompt until it rots. /linkedin-post exists so the pipeline, all 4 steps of it, is a file in .cursor/commands, versioned with the repo.

It ships in the Marketing Kit. It is wired to the Social & LinkedIn Strategist (social-media-strategist) and Content Strategy Lead (content-marketer) agents. Required skills: LinkedIn Thought Leadership & Founder Branding; Content Marketing Funnel (TOFU, MOFU, BOFU).

When to use it

• Use to build founder authority and generate organic inbound leads on LinkedIn.
• Use /linkedin-post when you want that pipeline, not a freeform chat. If you only need one step, use a narrower command or a single agent.
• Start a new chat. Do not run this command in a thread that just touched production SQL.

When not to use it

• Do not run /linkedin-post as a substitute for reading the diff. The command produces files; you still gate them.
• Do not chain it into a 40-turn chat. Fresh context is part of the design.
• Do not run it if you have not filled CURSOR.md. The pipeline will invent a stack.

Example workflow

1. Craft compelling 2-line hook to maximize click-through rate
2. Structure post with concise bullet points and whitespace formatting
3. Share concrete technical insights, metrics, and architecture lessons
4. End with an engaging open-ended question to spark comments

Example usage

Type this in Cursor chat: /linkedin-post Draft founder update post about shipping 34 AI agents in 7 days with Cursor

The command file tells the session which agents to adopt and which skills to read. You should see phase headers, not a single dump of code.

If a phase fails its gate, stop. Do not add 'just continue'.

Example output

• Expected artifact: docs/marketing/linkedin-posts.md

Best practices

• Keep the prompt specific. /linkedin-post Draft founder update post about shipping 34 AI agents in 7 days with Cursor is the shape: object, constraint, and outcome.
• Let the listed agents work in order: social-media-strategist → content-marketer.
• Save outputs in the repo. Chat-only answers evaporate.
• Marketing commands write to docs/marketing/ so the next command can read positioning before it writes a landing page.

Common mistakes

• Typing /linkedin-post with no object ('do the thing'). The pipeline will guess.
• Re-running the command in the same chat after a failed gate instead of fixing the failing file.
• Editing the command file to skip review so it 'goes faster'.
• Skipping the LinkedIn Thought Leadership & Founder Branding skill that the command depends on.