Skip to content

uplika/uplika-plugin / skills/linkedin-reply-handler

linkedin-reply-handler

Verified

Draft replies to LinkedIn comments, one comment or a whole thread in one batch, filtering low-value comments first. Not for top-level comments.

FileKindSize
SKILL.mdskill md14.6 KB
references/examples.mdmarkdown1.3 KB
references/filtering-rules.mdmarkdown2.6 KB
references/reply-templates.mdmarkdown2.2 KB
references/threading-rules.mdmarkdown2.9 KB

references/reply-templates.md

View on GitHub
# 5 Reply Templates for Thread Continuations

## R1: Answer-Their-Question

**When:** counterpart ends with a direct question.

**Skeleton:**
```
[Name] [direct answer in 1 sentence].

[one concrete practice, number, or lived example that backs the answer].
```

**Example (Serge replying to the post author asking "How are you building that conviction muscle with your team?"):**
> conviction doesn't build in meetings, it builds when you ship what you argued for and find out within a week whether the customer actually cared.
>
> our default now.. if a team member can't turn an opinion into something shippable in two or three days, we park the opinion until they can.

---

## R2: Concede-Then-Sharpen

**When:** counterpart pushed back on your original comment.

**Skeleton:**
```
fair point on [what they conceded]. where I'd still push is [narrow slice].

[one specific case that makes your push-back sharper].
```

---

## R3: Extend-Their-Thesis

**When:** counterpart agreed or extended; you take it one layer further.

**Skeleton:**
```
[Name] the piece that compounds is [new angle their take enables].

[concrete example of where that compounding is visible now].
```

---

## R4: Share-Lived-Experience

**When:** the thread is theoretical and you have a real operational story.

**Skeleton:**
```
[Name] we hit this exact thing last [timeframe]. [what broke, one line].

[the fix, or the thing you're still trying]. [one honest caveat].
```

---

## R5: Ask-Back

**When:** counterpart's position is under-specified and their answer would help you both.

**Skeleton:**
```
[Name] before I dig in.. what's the [missing piece] in your framing?

if [scenario A], I'd answer [X]. if [scenario B], closer to [Y]. which side are you standing in?
```

---

## Universal rules

- 150-300 chars. Tighter than top-level comments.
- Capitalize the counterpart's first name (sign of respect).
- Lead with a word that's not "thanks" unless there's a specific reason to acknowledge the favor.
- Em dashes capped (a reply is short, so at most one); use `..` for soft pauses.
- Single line-break between sentence 1 and sentence 2 for mobile scan.
- Match reaction to the tone: APPRECIATION for earned compliments, INTEREST for intellectual engagement, EMPATHY for personal moments.
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