Individual skill
publicity-distribution
Write and distribute launch and publicity content across LinkedIn, X/Twitter, Instagram, Discord, Medium, Substack, and YouTube. Produces per-platform copy that does not read as AI-written (no em dashes, no "thrilled to announce", no engagement-bait), plus the exact image/video specs and character limits each platform wants. Use this skill whenever the user wants to announce, launch, publicize, promote, cross-post, or share anything - a product, a feature, an open-source release, a research paper, a blog post, a demo video, a milestone, a job opening, or a conference talk. Trigger it on phrases like "post this on LinkedIn", "write a launch tweet", "announce this", "share this in Discord", "turn this into a thread", "what should I post", "write a Medium article about", "help me with distribution", "draft a YouTube description", "make this sound less like AI", or "de-slop this post". Also use it when the user has just finished shipping something and asks how to get it in front of people.
skills/publicity-distribution/SKILL.md
Source commit 7a708ce17d05bd390da88b2350f4b794d9427f18
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Instructions only
- Last checked
- Nov 3, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 2,124
- Repository last updated
- Oct 7, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 7,603 bytesSKILL.mdcore · 7,603 bytesSKILL.mdcore · 7,603 bytesexamples/discord-soft-share.mddoc · 4,662 bytesexamples/paper-launch.mddoc · 8,527 bytesexamples/product-launch.mddoc · 5,625 bytesplatforms/discord.mddoc · 9,991 bytesplatforms/instagram.mddoc · 3,686 bytesplatforms/linkedin.mddoc · 6,157 bytesplatforms/medium.mddoc · 4,961 bytesplatforms/substack.mddoc · 4,873 bytesplatforms/twitter-x.mddoc · 4,493 bytesplatforms/youtube.mddoc · 6,136 bytesreferences/anti-ai-tells.mddoc · 9,899 bytesreferences/asset-specs.mddoc · 4,015 bytesreferences/campaign-playbooks.mddoc · 7,520 bytesstyles/builder-technical.mddoc · 3,639 bytesstyles/professional.mddoc · 4,233 bytesstyles/whatsapp-lowercase.mddoc · 3,378 bytes
Read excerpt
# Publicity and Distribution
Shipping something is half the work. This skill covers the other half: turning one thing you built into channel-native copy that people actually read, without it smelling like it came out of a language model.
## The two failure modes
Almost all bad launch content fails in one of two ways:
1. **It reads as AI-written.** Em dashes, "I'm thrilled to announce", rocket emojis, three perfectly parallel bullets, a closing question nobody will answer. Readers on LinkedIn and X have been trained to spot this in under a second and they scroll past it or, worse, mock it in the comments. Fixing this is not optional and it is not cosmetic.
2. **It is the same paragraph pasted five times.** A LinkedIn post and a tweet and a Discord message are different formats for different rooms. Copying one into the other five places is visible and it is lazy.
Everything below exists to avoid those two things.
## Workflow