---
name: linkedin-post
description: Polish dictated drafts into publish-ready LinkedIn posts that build a personal brand around trust, relationships, and collaborative problem-solving.
---

# LinkedIn Post Polisher

## Purpose

Take a raw dictated draft for a LinkedIn post and polish it into a publish-ready post following the style guide below.

## When to Use This Skill

Use this skill when the user provides a rough draft and asks to:
- Polish a LinkedIn post
- Clean up a LinkedIn draft
- Turn a dictation into a LinkedIn post
- Edit a social media post for LinkedIn

## Style Guide

### Core Philosophy & Audience

- The audience is mixed: internal sales colleagues/peers AND end customers/partners.
- Relationship-first: frame interactions from the perspective of building human connections and partnerships. Avoid framing things as "the sales team selling to the customer."
- Human-to-Human (H2H) over B2B: emphasize that business relationships are actually just hyper-local connections between individuals.

### Tone & Voice

- Authentic & humble: use phrases like "It was an honor to..." or "I've learned to..."
- Concise & punchy: keep it brief. Avoid long bulleted lists if they can be condensed into a single cohesive paragraph of core principles.
- Collaborative: highlight teamwork (e.g., working alongside an AE counterpart) and shared goals.
- Value-driven: end with a strong, actionable takeaway or philosophical reflection that benefits the reader.

### Vocabulary: Dos and Don'ts

- DO use: partnerships, connections, people, leaders, experts, relationship-building, understanding, trust, alignment.
- DON'T use: internal sales jargon (e.g., "economic buyer," "prospecting," "closing," "sales cycle").
- DO focus on individuals: use "business and technical leaders" or "experts" rather than "business teams" or "technical teams." Make the connection feel personal.
- DO be precise: clearly distinguish between the vendor (e.g., "the vendor's account team") and the client (e.g., "the customer's business leader and hands-on technical expert") so the dynamic is immediately clear to the reader.

### Formatting & Flow

- Length: aim for 3-4 short paragraphs maximum.
- Repetition: strictly avoid repeating words in quick succession (e.g., using "projects" twice in the same sentence). Read aloud to ensure conversational flow.
- Structure:
  - **Paragraph 1 (The Hook/Context):** What happened and who was involved? (e.g., event, presentation, milestone).
  - **Paragraph 2 (The Insight):** What was the core theme or lesson? Distill complex ideas into a shared principle.
  - **Paragraph 3 (The Takeaway):** How do you apply this? Leave the reader with a definitive statement or piece of advice.
  - **Hashtags:** Include 5-7 relevant hashtags combining company, role, industry, and core themes (e.g., #Verkada #SolutionsEngineering #PhysicalSecurity #Teamwork).

## Workflow

1. Read the user's dictated draft.
2. Identify the core event, insight, and takeaway.
3. Rewrite the post following the style guide above.
4. Present the polished version for review.
5. On approval, ask if the user wants the post copied to clipboard or saved to a file.

## Example

**Input (dictated):**
> presented at the SE spotlight with Cameron, talked about how we build partnerships, basically company to company relationships are just people connections, I always focus on people first then the tech stuff works out

**Output (polished):**
> It was an honor to present to the Verkada Solutions Engineering team during our recent SE Spotlight alongside my AE counterpart, Cameron Breck.
>
> We shared our core principles for building strong, effective partnerships, both internally and with the people we serve. When you get down to it, company-to-company relationships are built on top of hyper-local connections made between the vendor's account team and both the customer's business leader and hands-on technical expert.
>
> I've learned to prioritize these relationships first in meetings, proof of values, and full deployments. Invest in understanding the people behind the project first, and the technical success will naturally follow.
>
> #SolutionsEngineering #OneTeam #PhysicalSecurity #SalesEngineering #PreSales

## Dependencies

None.
