# Linkedin Hackathon Post

> Write LinkedIn posts announcing hackathon wins. Use when user says they won a hackathon, placed in a track, or wants a LinkedIn post about a hackathon project.

- Skill: `peytonli/linkedin-hackathon-post` (Agent Skill)
- Install (CLI): `npx skillmds@latest add peytonli/linkedin-hackathon-post`
- Raw SKILL.md: https://api.skillmd.com/api/skills/peytonli/linkedin-hackathon-post/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: PeytonLi (https://skillmd.com/u/peytonli)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/peytonli/linkedin-hackathon-post

---


# LinkedIn Hackathon Post

## Process

1. Ask the user for:
   - Hackathon name, result (won, finalist, placed), track name if any, partners/sponsors, office/venue
   - What the project does (one sentence)
   - The problem it solves (make it visceral — 3 AM pager, tedious workflow, etc.)
   - The pipeline or workflow (5-6 numbered steps, each one line max)
   - The tech stack
   - Repo link (and Devpost link if available)
   - Any specific tone notes

2. Before drafting, compile the hashtag list: hackathon name, every sponsor, every partner company, the venue, the project's domain, and key technologies from the stack. Present these alongside the draft so the user can pick which to keep.

3. Draft the post following the template structure below.

4. Humanize it: no em dashes, no AI vocabulary clusters, no rule-of-three, no boldface headers. Keep it conversational.

5. Add one emoji after the opening line (🏆). No other emojis unless the user asks.

6. Append hashtags at the bottom. Include the hackathon name, every sponsor, venue, project domain, and key technologies. Hashtags sit outside the 3,000 character post body limit. If the user finds the list too dense, offer to drop generic domain tags first.

## Template Structure

```
Opening:
I [won / was a finalist at / placed in] [Hackathon Name][, Track Name track if applicable], building [w/ partners or solo] at [Venue]. 🏆 Here's what I built.

Problem:
[One paragraph. Make it relatable. Use concrete scenario: time of night, specific action, real pain. Engineers should nod reading it. End on the time/cost of the status quo.]

Solution:
[One paragraph bridging the problem to the project. What the project does at a high level and why the approach fits the problem. Keep it tight — two or three sentences.]

Project intro (must come right before the pipeline):
[Project name] [one-line description of what it actually does — ingestion, consolidation, output, escalation]. Here's the pipeline:

Pipeline:
1. [Step one — trigger/ingestion]
2. [Step two]
3. [Step three]
...
6. [Final step — the payoff, often where the hack's theme shines]

Stack:
[Comma-separated list]

Bigger picture:
[One paragraph on why this matters. Not "this is a game-changer" but the actual gap it closes. End with a concrete benefit.]

Repo: [URL]
Devpost: [URL if available]

Hashtags:
#[HackathonName] #[Sponsor1] #[Sponsor2] ... #[Venue] #[Domain1] #[Domain2] ... #[KeyTech1] #[KeyTech2] ...
```

## Length Constraint

LinkedIn posts have a 3,000 character hard limit. Draft aggressively under it — target 2,800-2,950 to leave buffer for last-minute edits. If the first draft is over:

- Cut the problem paragraph first: fewer scenic details, same visceral punch.
- Pipeline steps: one line each, no exceptions. Drop the "Here's the pipeline:" lead-in to just "The pipeline:" or cut it entirely.
- Stack: one line, abbreviations where obvious (STT, TTS, PSTN).
- Bigger picture: two sentences max. Let the numbers do the work.

## Style Rules

- No em dashes. Periods, commas, or restructure instead.
- No "end-to-end," "seamlessly," "robust," "delightful," "game-changer," "revolutionize."
- One emoji max (🏆 after opening) unless user says otherwise.
- Short sentences mixed with longer ones. Read it aloud to check rhythm.
- Never say "I hope this helps," "Let me know what you think," or "Would love to hear your thoughts."
- Never boldface list headers or inline phrases.
- The problem paragraph is the most important part. Make it specific and real.
- Verify character count before finalizing. If over 3,000, trim before showing the user.