Workspace: all context paths below (identity, audience, strategy, voice, brand, raw, output, index, log, workspace preferences and context scripts) resolve from context/ in the kit root. Read both the root AGENTS.md and context/AGENTS.md. Skill-local references/ and flowchart scripts/ resolve from this skill directory.
Write a LinkedIn post
Read AGENTS.md, index.md, relevant identity and audience pages, identity/proof.md, voice/linkedin-voice.md, voice/formats.md and the selected pillar/funnel context. Read the full source behind the central claim.
Drafts sound like a bot when the only voice input is a style guide. If the context holds the author's verbatim words (calls, DMs, voice notes, past posts), a story bank or a page on what performs on their account, read the relevant parts too. A story the author has not told in public needs their yes before it goes into copy.
Find the post
Identify one useful point, its source, the intended reader and the post's job. Work from the supplied brief and existing context; ask for missing information only when it would change the substance. Do not invent a milestone, anecdote or customer quote to make an idea interesting.
Choose a structure that suits the material: a sequence for a process, a story for a real change, evidence for a claim, or a comparison for a decision. Do not force every post into one house format.
Write an opening that the body can substantiate. Prefer a specific observation over manufactured suspense. Use the author's actual rhythm and vocabulary. Do not add slang, self-deprecation, deliberate mistakes, dramatic reversals or numeric claims just to sound human.
A stub voice page does not block useful editing of a supplied draft. Preserve the user's wording and use plain language, while being clear that the voice has not yet been calibrated.
Edit for substance
Check that each paragraph adds information. Cut generic praise, unsupported superlatives, repeated morals, empty transitions and slogan-like conclusions. Keep necessary explanations and qualifications. Read the opening, paragraph starts and ending together: the argument should remain understandable.
Check every factual claim, quote, date and number against its source and public-use status. Keep reported results, targets and illustrative examples distinct. Use a CTA only when it fits the chosen funnel job and a real available offer. Resource and video links go in the first comment and the post says so; a link to the author's own site carries UTM parameters (source linkedin, 1 campaign slug per piece or waterfall).
For repurposing, select one argument from the source rather than compressing the entire source into a post. For revisions, address the user's requested changes first and preserve their facts and meaningful phrasing.
Deliver or save
Return one paste-ready draft, brief source notes and any material uncertainty. Offer alternate hooks only when useful or requested. Do not put process commentary inside the copy.
When saving to Notion is requested, follow strategy/notion-schema.md, fetch the configured destination and use templates/notion-content.md. Set Status to Creating, one Pillar and the selected Platform. Add a Publish date only if a date is agreed. Check for the existing card before creating another.
If Notion is unconfigured, deliver in chat and state it was not saved. Never silently use another board. Saving a draft does not schedule or publish it.
