Skip to content

getnao/sylph / .claude/skills/linkedin

linkedin

Verified

FileKindSize
SKILL.mdskill md7.7 KB
community.mdmarkdown3.5 KB
events.mdmarkdown3.0 KB
ideas.mdmarkdown3.4 KB
launches.mdmarkdown3.1 KB

community.md

View on GitHub
# LinkedIn Community Posts

Community posts mobilize your network, show vulnerability, and celebrate people. They build trust and deepen relationships.

---

## Format 1: Mobilization / Call for Help

**When to use:** You need something from your network - introductions, feedback, beta testers, recommendations, hires.

**Structure:**
```
[What you're working on and why it matters]

[What you need - be specific]

[What's in it for them]

[Clear ask with low friction]
```

**Template:**
```
I need your help with something.

We're [building/working on/preparing] [what] and we need [specific thing].

Here's the context: [2-3 sentences on why this matters and what stage you're at]

What I'm looking for:
- [Specific ask 1 - e.g., "Introductions to data team leads at Series B+ companies"]
- [Specific ask 2 - e.g., "10 minutes of your time for a user interview"]
- [Specific ask 3 - e.g., "Feedback on this prototype"]

What you get: [be honest - early access, credit, a coffee, nothing but gratitude]

DM me or comment below if you can help.

#hiring #feedback #community
```

**Notes:**
- Be direct about what you need. Vague asks get vague responses.
- Make the ask specific and low-friction
- Be honest about what's in it for them (nothing is fine - people help founders)
- These posts work because they invite participation. People want to help.

---

## Format 2: Vulnerability / Honest Reflection

**When to use:** Sharing a failure, mistake, hard lesson, or honest moment from your journey.

**Structure:**
```
[The honest admission]

[What happened - the full story, briefly]

[What you learned]

[Where you are now]
```

**Template:**
```
[Honest statement about something that went wrong or was hard]

Here's what happened: [the story in 3-5 sentences - be specific, not dramatic]

What I got wrong: [the actual mistake or misjudgment]

What I learned:
- [Lesson 1 - specific and transferable]
- [Lesson 2]

Where things stand now: [current state - shows you moved forward]

Sharing this because [why this might help someone else].

#founders #lessons #honesty
```

**Notes:**
- Vulnerability is not self-pity. Share what you learned, not just what hurt.
- Be specific about the mistake. Vague vulnerability ("It was hard") is not useful.
- Always include what you learned and where you are now
- Don't manufacture vulnerability for engagement. If it's not real, don't post it.
- This format builds deep trust but should be used sparingly (once a month max)

---

## Format 3: Team Celebration / Shoutout

**When to use:** Celebrating a team member, collaborator, customer, or community member.

**Structure:**
```
[Who you're celebrating and why]

[The specific thing they did]

[Why it mattered - the impact]

[The broader lesson or value it represents]
```

**Template:**
```
Shoutout to [person/team] for [specific achievement].

Here's what they did: [2-3 sentences on the specific contribution - be concrete]

Why this matters: [the impact on the team, product, customers, or community]

[One sentence on the broader principle this represents - e.g., "This is what happens when you give people ownership."]

[Tag the person]. Go follow them.

#team #culture #shoutout
```

**Notes:**
- Celebrate the person, not yourself through them
- Be specific about what they did. "Amazing work by the team" is not a shoutout.
- Tag the person so they see it and their network sees it
- Keep it genuine. Forced celebrations feel performative.
- Works well for: new hires, promotions, customer wins, open source contributors, mentors
- Use "we" only when the whole team genuinely contributed
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall