LinkedIn Post Creator
Generate professional, engaging LinkedIn posts for career milestones, technical projects, and professional updates.
Supported Post Types
- Achievement/Certification - Professional milestones, course completions, certifications
- Project Completion - Technical project showcases with details and links
- Learning Journey - Progress updates, weekly learnings, challenge updates
- Professional Updates - Job changes, promotions, speaking engagements
Workflow
1. Gather Information
Ask the user for:
- Post type - Which of the 4 types above
- Core content - What they want to communicate (achievement details, project description, etc.)
- Technical details (for project posts) - Architecture, tech stack, key features
- Links (optional) - GitHub, demo, blog post, etc.
- Hashtag preference - Auto-generate or user-provided
2. Select Appropriate Pattern
Consult references/patterns.md to determine the structure for the post type:
- Achievement/Certification: Emphasize learning, gratitude, forward-looking
- Project Completion: Technical details, demo, reflection
- Learning Journey: Progress marker, accomplishments list, next steps
- Professional Updates: Announcement, highlights, gratitude
3. Generate the Post
Follow these guidelines:
Formatting:
- Use the pattern structure from
references/patterns.md
- Keep paragraphs short (2-3 sentences)
- Use blank lines between sections for readability
- Professional tone by default, minimal emojis (1-3 max)
- Technical project posts may use more structured formatting with bullets and emojis
Content:
- Lead with a strong hook in the first 2-3 lines
- Be specific with accomplishments and details
- Include concrete examples or metrics when possible
- Add gratitude section for achievement posts
- Include forward-looking statement or call-to-action
Emojis:
- Professional/Achievement posts: None or 1-2 maximum
- Technical/Project posts: Use strategically for structure (📌, ✅, 👉, 📂, 🎥)
- Never use emojis in every line
Lists:
- Use bullet points (•) for features/highlights
- Use checkmarks (✅) for completed tasks/learning items
- Use arrows (👉) to highlight important points
- Keep list items parallel in structure
Links:
- Place at the end before hashtags
- Use emoji prefixes: 📂 for GitHub/code, 🎥 for video/demo
- Format:
📂 GitHub: [URL]
4. Add Hashtags
If user requests auto-generation:
- Consult
references/hashtags.md for relevant tags
- Select 4-6 highly relevant hashtags
- Mix broad (#AI, #SoftwareEngineering) with specific (#LangGraph, #NextJS)
- Include branded tags (company names, program names) when applicable
- Place at the end of the post
- Format:
hashtag#Tag1 hashtag#Tag2 hashtag#Tag3
If user provides hashtags:
- Use their exact tags
- Ensure proper formatting:
hashtag#TagName
Hashtag Guidelines:
- 4-6 hashtags total (never more than 6)
- Prioritize relevance over popularity
- Avoid generic tags (#Success, #Motivation)
- Use professional, industry-standard tags
5. Review and Refine
Before presenting the post:
- Verify the hook (first 2-3 lines) is compelling
- Check that formatting matches the pattern
- Ensure hashtags are relevant and properly formatted
- Confirm emoji usage is appropriate for post type
- Validate all links are included
Reference Files
references/examples.md - Real examples of each post type. Consult for inspiration and structure.
references/patterns.md - Detailed formatting patterns and structures for each post type. Always consult this to determine the correct structure.
references/hashtags.md - Categorized hashtag suggestions by domain and topic. Use when auto-generating hashtags.
Quick Reference
| Post Type |
Emoji Use |
Key Elements |
Example Hook |
| Achievement |
Minimal (0-2) |
Learning, gratitude, forward-looking |
"I'm excited to share..." |
| Project |
Structured (3-6) |
Tech details, demo, reflection |
"📌 [Project Name]..." |
| Learning Journey |
Moderate (2-4) |
Progress marker, checklist, next steps |
"Week 3 of #100DaysOfCode..." |
| Professional Update |
Minimal (0-2) |
Announcement, highlights, gratitude |
"Excited to announce..." |
Tips for Effectiveness
- Hook first - Most important information in first 2-3 lines (shown in feed preview)
- Be specific - Concrete details are more engaging than generalizations
- Show, don't tell - Use examples and metrics instead of adjectives
- Authentic voice - Professional but conversational, not robotic
- Value to reader - What can they learn or take away?
Example Usage
User: "I just completed a React course and want to post about it on LinkedIn"
Response:
- Identify post type: Achievement/Certification
- Ask for details: Course name, platform, key learnings, instructors to thank
- Consult
references/patterns.md for achievement post structure
- Generate post following the pattern
- Auto-generate hashtags from
references/hashtags.md (e.g., #React, #WebDevelopment, #Learning)
- Present formatted post with 4-6 relevant hashtags
1---2name: linkedin-post-creator3description: Generate professional LinkedIn posts for achievements, certifications, project completions, learning journeys, and professional updates. Use when users want to create, draft, or write LinkedIn posts with appropriate formatting, hashtags, and professional tone. Supports both auto-generated and user-provided hashtags. Default to professional style with minimal emojis unless technical project posts require structured formatting.4---56# LinkedIn Post Creator78Generate professional, engaging LinkedIn posts for career milestones, technical projects, and professional updates.910## Supported Post Types11121. **Achievement/Certification** - Professional milestones, course completions, certifications132. **Project Completion** - Technical project showcases with details and links143. **Learning Journey** - Progress updates, weekly learnings, challenge updates154. **Professional Updates** - Job changes, promotions, speaking engagements1617## Workflow1819### 1. Gather Information2021Ask the user for:22- **Post type** - Which of the 4 types above23- **Core content** - What they want to communicate (achievement details, project description, etc.)24- **Technical details** (for project posts) - Architecture, tech stack, key features25- **Links** (optional) - GitHub, demo, blog post, etc.26- **Hashtag preference** - Auto-generate or user-provided2728### 2. Select Appropriate Pattern2930Consult `references/patterns.md` to determine the structure for the post type:31- Achievement/Certification: Emphasize learning, gratitude, forward-looking32- Project Completion: Technical details, demo, reflection33- Learning Journey: Progress marker, accomplishments list, next steps34- Professional Updates: Announcement, highlights, gratitude3536### 3. Generate the Post3738Follow these guidelines:3940**Formatting:**41- Use the pattern structure from `references/patterns.md`42- Keep paragraphs short (2-3 sentences)43- Use blank lines between sections for readability44- Professional tone by default, minimal emojis (1-3 max)45- Technical project posts may use more structured formatting with bullets and emojis4647**Content:**48- Lead with a strong hook in the first 2-3 lines49- Be specific with accomplishments and details50- Include concrete examples or metrics when possible51- Add gratitude section for achievement posts52- Include forward-looking statement or call-to-action5354**Emojis:**55- **Professional/Achievement posts**: None or 1-2 maximum56- **Technical/Project posts**: Use strategically for structure (📌, ✅, 👉, 📂, 🎥)57- Never use emojis in every line5859**Lists:**60- Use bullet points (•) for features/highlights61- Use checkmarks (✅) for completed tasks/learning items62- Use arrows (👉) to highlight important points63- Keep list items parallel in structure6465**Links:**66- Place at the end before hashtags67- Use emoji prefixes: 📂 for GitHub/code, 🎥 for video/demo68- Format: `📂 GitHub: [URL]`6970### 4. Add Hashtags7172**If user requests auto-generation:**73- Consult `references/hashtags.md` for relevant tags74- Select 4-6 highly relevant hashtags75- Mix broad (#AI, #SoftwareEngineering) with specific (#LangGraph, #NextJS)76- Include branded tags (company names, program names) when applicable77- Place at the end of the post78- Format: `hashtag#Tag1 hashtag#Tag2 hashtag#Tag3`7980**If user provides hashtags:**81- Use their exact tags82- Ensure proper formatting: `hashtag#TagName`8384**Hashtag Guidelines:**85- 4-6 hashtags total (never more than 6)86- Prioritize relevance over popularity87- Avoid generic tags (#Success, #Motivation)88- Use professional, industry-standard tags8990### 5. Review and Refine9192Before presenting the post:93- Verify the hook (first 2-3 lines) is compelling94- Check that formatting matches the pattern95- Ensure hashtags are relevant and properly formatted96- Confirm emoji usage is appropriate for post type97- Validate all links are included9899## Reference Files100101- **`references/examples.md`** - Real examples of each post type. Consult for inspiration and structure.102- **`references/patterns.md`** - Detailed formatting patterns and structures for each post type. Always consult this to determine the correct structure.103- **`references/hashtags.md`** - Categorized hashtag suggestions by domain and topic. Use when auto-generating hashtags.104105## Quick Reference106107| Post Type | Emoji Use | Key Elements | Example Hook |108|-----------|-----------|--------------|--------------|109| Achievement | Minimal (0-2) | Learning, gratitude, forward-looking | "I'm excited to share..." |110| Project | Structured (3-6) | Tech details, demo, reflection | "📌 [Project Name]..." |111| Learning Journey | Moderate (2-4) | Progress marker, checklist, next steps | "Week 3 of #100DaysOfCode..." |112| Professional Update | Minimal (0-2) | Announcement, highlights, gratitude | "Excited to announce..." |113114## Tips for Effectiveness1151161. **Hook first** - Most important information in first 2-3 lines (shown in feed preview)1172. **Be specific** - Concrete details are more engaging than generalizations1183. **Show, don't tell** - Use examples and metrics instead of adjectives1194. **Authentic voice** - Professional but conversational, not robotic1205. **Value to reader** - What can they learn or take away?121122## Example Usage123124**User:** "I just completed a React course and want to post about it on LinkedIn"125126**Response:**1271. Identify post type: Achievement/Certification1282. Ask for details: Course name, platform, key learnings, instructors to thank1293. Consult `references/patterns.md` for achievement post structure1304. Generate post following the pattern1315. Auto-generate hashtags from `references/hashtags.md` (e.g., #React, #WebDevelopment, #Learning)1326. Present formatted post with 4-6 relevant hashtags