linkedin-shoutout-post
Skill1 starsChanged 17 days agoMITView on GitHub
Use this skill when you want to publicly praise a B2B founder or company for something they do well in go-to-market, and break down why it works. Produces a ready-to-paste LinkedIn post, a first comment, and a source list for every claim. Also use for "shoutout post", "shout out [name]", "celebrate this founder", "who's doing it right", "positive breakdown post".
In this repository67 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- morning-paper-outreachSkill
- client-activation-checkinSkill
- client-churn-autopsySkill
- client-win-backSkill
- late-payment-chaseSkill
- network-path-mappingSkill
- rate-increase-planSkill
- sales-call-debriefSkill
- weekly-funnel-reviewSkill
- buyer-readSkill
- punch-upSkill
- call-topic-miningSkill
- ceo-exec-assistantSkill
- og-image-from-templateSkill
- weekly-site-and-ad-reportSkill
- icp-reviewSkill
- weekly-content-ideas-from-callsSkill
- client-performance-reviewSkill
- cold-email-sequenceSkill
- email-content-reviewerSkill
- scoring-analysis-and-distributionSkill
- delivery-audit-discovery-callSkill
- directionSkill
- rundownSkill
- source-checkSkill
- work-reviewSkill
- demandbird-exact-time-linkedin-postSkill
- kondo-owed-reply-sweepSkill
- linkedin-export-contact-importSkill
- mail-messages-contact-touchesSkill
- riverside-short-social-scheduleSkill
- youtube-transcript-panel-pullSkill
- email-voice-setupSkill
- upsell-opportunity-briefSkill
- ad-creative-content-strategySkill
- klaviyo-account-auditSkill
- facilitator-notesSkill
- local-prospectingSkill
- weekly-linkedin-postsSkill
- linkedin-watchlist-briefSkill
- pipeline-by-scriptSkill
- pre-session-flash-cardSkill
- write-in-the-owners-voiceSkill
- reddit-gtm-sprintSkill
- process-captureSkill
- sales-call-market-analyzerSkill
- plain-language-copy-checkSkill
- revenue-goal-funnel-mathSkill
- case-study-buildSkill
- cash-runway-forecastSkill
- client-profitability-readSkill
- client-proposalSkill
- content-briefSkill
- quarter-goal-filterSkill
- win-to-anglesSkill
- activity-incentive-sprintSkill
- candidate-interview-coachSkill
- client-list-stack-pitchSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 11 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 25
Not someone you have critiqued in public.
- Distinctive: line 27
Write the post in this shape:
- Distinctive: line 33
Write the first comment. It goes one level deeper on a single pattern from the post.
- Very specific: line 34
Run the check in references/post-check.md.
- Distinctive: line 53
MUST back every claim with a post, page or public number you can link.
- Distinctive: line 54
MUST make the only CTA "follow them".
- Distinctive: line 55
MUST keep the breakdown to 3 to 5 patterns, each with evidence.
- Distinctive: line 56
NEVER mention your own offer, services, clients or a call link, in the post or the first comment.
- Distinctive: line 57
NEVER add "but", "gap", "opportunity" or "what I'd add".
- Distinctive: line 58
NEVER claim numbers about them that they have not published.
- Distinctive: line 59
NEVER shout out someone you have publicly critiqued, and never the same person twice.
- Distinctive: line 60
NEVER post more than one shoutout a week.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Applies when you have a founder or company in mind who is visibly good at something your audience wants to learn. Produces one post that teaches the tactic, tags them, and asks your readers to follow them.
A shoutout does three jobs, in this order: it starts a relationship with the person tagged, it shows your audience you can tell good work from bad, and it puts the post in front of the tagged person's audience. It does not book calls. That is fine; it makes the posts that do book calls land harder.
The play
- Pick the target. All five must be true; the full screen is in references/target-and-research.md.
- B2B founder or company your audience overlaps with.
- 10K to 100K followers. Under 10K the tag reaches too few people. Far over 100K your post is noise to them.
- Visibly good at one thing in your field, not "great overall".
- Verifiable: you can point to posts, pages or public numbers.
- Not someone you have critiqued in public. Never both.
- Research before writing. Read their last 15 to 20 posts, their site, their newsletter if they have one, and any interviews. Find 3 to 5 specific things they do well, each with a piece of evidence. Use the checklist in references/target-and-research.md.
- Write the post in this shape:
- Hook: "[Name] is doing [specific thing] better than almost anyone I've seen."
- Who they are: 2 to 3 lines, max.
- The breakdown, 60 to 70% of the post: "Here's what they do right:" then 3 to 5 numbered patterns. Each one is what they do, the evidence, and why it works.
- Why it matters: 1 to 2 lines turning it into a principle the reader can apply.
- CTA: "Give [Name] a follow. This is what good looks like."
- Write the first comment. It goes one level deeper on a single pattern from the post. No link to anything you sell.
- Run the check in references/post-check.md. Any fail, rewrite before posting.
- Branch by what they are good at:
- Content: name cadence, format mix, hook pattern, and their best post with its numbers.
- Outbound or email: only what is visible from outside (the messages you received, their public talks). Never guess at their numbers.
- Funnel or site: walk the path a buyer takes and name the step that is unusually good.
- Post at most one shoutout a week. Weeks between shoutouts are what make them read as real.
Worked examples are in references/worked-examples.md. Open them before writing your first one.
What good looks like
- First thing I check that most people skip: whether the tagged person would screenshot it and share it. If they would not, it is too vague or it has a hidden "but".
- The mediocre version: "Huge respect for [Name], their content is fire." Praise with no tactic. Nobody learns anything, nobody shares it, and the tagged person gives it a like at most.
- The other mediocre version: a teardown with a compliment on top. "They do X well, but they could also..." That is a critique, and the subject feels used.
- I know the post is right when a reader who has never heard of the subject could copy one of the patterns tomorrow, and every claim has a link behind it.
- I know it landed when the subject comments or reshares within 48 hours, and their followers start connecting with you.
Rules
- MUST back every claim with a post, page or public number you can link.
- MUST make the only CTA "follow them".
- MUST keep the breakdown to 3 to 5 patterns, each with evidence.
- NEVER mention your own offer, services, clients or a call link, in the post or the first comment.
- NEVER add "but", "gap", "opportunity" or "what I'd add". That is a different post.
- NEVER claim numbers about them that they have not published.
- NEVER shout out someone you have publicly critiqued, and never the same person twice.
- NEVER post more than one shoutout a week.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

