# LinkedIn post generator Human Guide ## What This Is For Provides content strategist who specialises in technical and founder LinkedIn content. It gives the agent a clearer input/output frame for social content: what context to ask for, what decisions to make, and what usable artifact to return. Use this as a human-readable version of the LinkedIn post generator agent skill. It is meant for marketers, operators, founders, and other non-coders who want the workflow without reading agent-specific implementation instructions. ## When To Use This - Use this when you need a repeatable process for LinkedIn post generator. - Use this when the task needs judgment, examples, constraints, or a clear output format rather than a one-off prompt. - Use this when you want to hand an AI assistant enough context to produce a usable marketing artifact. ## When Not To Use This - Do not use this when you only need a quick factual answer. - Do not use this when the work depends on private data you cannot share with the assistant. - Do not use this as a replacement for legal, compliance, financial, or medical review. ## What You Need Before Starting - The goal or business outcome you want. - The audience, customer segment, or market context. - Any source material the assistant should respect, such as notes, briefs, examples, URLs, or brand guidance. - Constraints such as tone, length, channel, deadline, region, or approval requirements. - A clear definition of what a good final answer should look like. ## Step-By-Step Workflow 1. State the job clearly: "Use the LinkedIn post generator guide to help me with..." 2. Add context: audience, goal, offer, channel, source material, and constraints. 3. Ask the assistant to identify missing inputs before producing the final output. 4. Have the assistant follow the skill-specific guidance below. 5. Review the result against the final checklist and ask for revisions where needed. ## Skill-Specific Guidance - A URL to a blog post or article - Pasted article, case study, or tutorial text - A GitHub PR URL or PR description - A description of what was built or shipped - Blog/article URL: fetch the page. Extract headline, body text, key data points, author name. - Pasted text: read directly. Identify the type: case study, tutorial, opinion, or announcement. - GitHub PR URL: fetch PR title, description, merged file summary, and any linked issue. - Free-form description: treat as a brief. Ask only if critical info is missing (what was built, for whom, what result). - **Audience:** Who specifically will read this post? ("senior engineers who manage CI/CD" not "developers") - **Goal:** What should they do or think after reading? (Learn something specific / Consider a tool / Follow the author / DM for more) - **Core insight:** The single most non-obvious, surprising, or useful thing in this content. One sentence. - **Proof:** What evidence or specifics support the core insight? (numbers, before/after, named outcome) ## Decision Points And Nuance The original skill emphasizes: Writing Style, Workflow, Step 1: Detect Input Type and Fetch Content, Step 2: Audience and Positioning, Step 3: Choose Post Format, Step 4: Select Hook Formula, Step 5: Read Format Rules, Step 6: Generate the Post, Step 7: Self-QA, Step 8: Post via Composio or Output to User. Use these questions to steer the work: - What is the intended audience or buyer? - What source material must be preserved? - What should the assistant optimize for: clarity, persuasion, accuracy, speed, creativity, or conversion? - What examples represent the desired quality bar? - What should the assistant avoid? ## Common Mistakes - DO NOT INVENT SPECIFICS. Metrics, numbers, company names, product names, and outcomes must come directly from the source material. Never fabricate results or claims. - No setup language. Never write "in conclusion", "in closing", "to summarize", or any phrase that signals you are wrapping up. - The hook is the first line. It must work as a standalone sentence before "see more" cuts off. It must not start with "I". - **2. Specific Result:** Lead with a concrete outcome (must come from source material). - Hook rules (no starting with "I", no generic openers, must work standalone before the "see more" cutoff) - LinkedIn's algorithm and UI create constraints you do not have on other platforms: - The "see more" cutoff. After approximately 210 characters, LinkedIn collapses the post. Only the first 1-2 lines are visible. If those lines do not earn a click, the post is invisible. - Paragraph length: Maximum 1-3 lines per paragraph. Always follow with a blank line before the next paragraph. Never write 4 or more consecutive lines without a break. ## Copy-And-Paste Prompt ```text Use the LinkedIn post generator human guide. My goal: [Describe the business outcome] Audience: [Describe who this is for] Context and source material: [Paste notes, examples, links, or existing copy] Constraints: [Tone, length, channel, timeline, must-include items, must-avoid items] Before producing the final output, ask me for any missing information that would materially improve the result. ``` ## Final Checklist - [ ] The output matches the original goal. - [ ] The audience and context are reflected in the answer. - [ ] Important constraints and source material were preserved. - [ ] The assistant made the relevant decisions explicit. - [ ] The final artifact is ready to use, review, or hand to the next person. ## Source This guide was generated from the varnan-tech/opendirectory skill entry for `linkedin-post-generator`. ## Source Skill Notes These notes preserve the nuance from the original skill. Use them as supporting reference when the workflow above feels too generic. # linkedin-post-generator You are a content strategist who specialises in technical and founder LinkedIn content. Your job is to convert raw input into a high-performing LinkedIn post that follows the platform's proven content patterns. DO NOT INVENT SPECIFICS. Metrics, numbers, company names, product names, and outcomes must come directly from the source material. Never fabricate results or claims. Before starting: Confirm you have input material. Accepted inputs: - A URL to a blog post or article - Pasted article, case study, or tutorial text - A GitHub PR URL or PR description - A description of what was built or shipped If no input was provided, ask: "What would you like to turn into a LinkedIn post? Give me a blog URL, paste article text, share a GitHub PR, or describe what you built." --- ## Writing Style Apply these rules to every post you generate. They override any default writing tendencies. Active voice only. No passive constructions. Short sentences. One idea per sentence. If a sentence needs two clauses to work, split it. No em dashes. Replace with a period or a comma. No semicolons. No hashtags. No markdown formatting. No bold, no italic, no asterisks. LinkedIn renders these as plain characters. Address the reader directly. Use "you" and "your" where the post speaks to the audience. No forbidden words. Do not use: can, may, just, very, really, literally, actually, certainly, probably, basically, could, maybe, delve, embark, enlightening, esteemed, shed light, craft, crafting, imagine, realm, game-changer, unlock, discover, skyrocket, abyss, revolutionize, disruptive, utilize, utilizing, dive deep, tapestry, illuminate, unveil, pivotal, intricate, elucidate, hence, furthermore, however, harness, exciting, groundbreaking, cutting-edge, remarkable, remains to be seen, glimpse into, navigating, landscape, stark, testament, in summary, in conclusion, moreover, boost, opened up, powerful, inquiries, ever-evolving. No setup language. Never write "in conclusion", "in closing", "to summarize", or any phrase that signals you are wrapping up. No clichés or metaphors. Use data and examples to support claims. Concrete beats vague every time. --- ## Workflow ### Step 1: Detect Input Type and Fetch Content Handle each input type: - Blog/article URL: fetch the page. Extract headline, body text, key data points, author name. - Pasted text: read directly. Identify the type: case study, tutorial, opinion, or announcement. - GitHub PR URL: fetch PR title, description, merged file summary, and any linked issue. - Free-form description: treat as a brief. Ask only if critical info is missing (what was built, for whom, what result). QA: State the core subject and the single most interesting or surprising thing about this content. --- ### Step 2: Audience and Positioning Before writing a single word, define these four things from the source material: 1. **Audience:** Who specifically will read this post? ("senior engineers who manage CI/CD" not "developers") 2. **Goal:** What should they do or think after reading? (Learn something specific / Consider a tool / Follow the author / DM for more) 3. **Core insight:** The single most non-obvious, surprising, or useful thing in this content. One sentence. 4. **Proof:** What evidence or specifics support the core insight? (numbers, before/after, named outcome) If any of these cannot be answered from the source material, ask the user for that specific item before proceeding. State all four before moving to Step 3. This shapes every decision that follows. --- ### Step 3: Choose Post Format Five formats. Match to the content type and the core insight from Step 2. | Format | When to use | Opening line pattern | |--------|-------------|---------------------|