launch-announcement
Skill0 starsChanged 28 days agoMITView on GitHub
Plan and schedule a multi-day announcement campaign with PostEverywhere. Use when the user is launching a product or feature, promoting an event, running a sale or offer, opening a waitlist or sign-ups, or wants teaser, launch-day, reminder and last-call posts.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- posteverywhere/cursor-pluginword for word, first seen Oct 15, 2026
- posteverywhere/claude-pluginword for word, first seen Sep 29, 2026
Other versions2 projects use a version of this.
Word for word · 2
- posteverywhere/claude-plugin★ 1100% same
- posteverywhere/cursor-plugin★ 0100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- agency-clientsSkill
- approval-workflowSkill
- brand-voiceSkill
- connect-social-accountsSkill
- cross-post-videoSkill
- fix-failed-postsSkill
- plan-content-calendarSkill
- recycle-top-postsSkill
- repurpose-contentSkill
- review-post-performanceSkill
- schedule-social-postsSkill
- weekly-reportSkill
- write-blog-postSkill
- write-x-thread-or-articleSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 1 is distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Check the calendar: Call list_accounts to get the account ids.
- Very specific: line 14
Pick a cadence: Use the template in references/launch-cadence.md.
- Very specific: line 16
Media: Use images or videos the user gives you (upload_media_from_url or list_media).
- Very specific: line 18
Group it: Call list_campaigns and reuse a matching campaign, or create one with create_campaign (a name like "Spring sale 2026").
- Distinctive: line 19
Create the posts: After the user confirms, pick one of two ways and tell the user which:
- Very specific: line 27
If the launch date moves, move every post in the campaign.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Launch announcement
Build a short campaign around one date: tease it, launch it, remind people, and close it. The user sees every post before anything is scheduled.
Steps
- Get the facts. Ask for anything missing: what is launching, the launch date and time zone, the end date (for an offer or event), the link, the price or offer terms, and which accounts. Use only facts the user gives. Never invent prices, dates, discounts or features.
- Check the calendar. Call
list_accountsto get the account ids. Calllist_posts_advancedwithstatus: "scheduled"and the campaign dates, so the new posts don't clash with posts already booked. - Pick a cadence. Use the template in
references/launch-cadence.md. Shorten it for a small launch. Tell the user the plan in one line per day before you write the posts. - Write the posts. Write each post for its platform (see
schedule-social-postsfor the rules). Each stage says something new: the teaser builds interest without giving everything away, launch day says what it is and where to get it, the reminder adds a detail or a proof point the user gave you, and the last call states the deadline plainly. Follow the user's voice guide if there is one (seebrand-voice). - Media. Use images or videos the user gives you (
upload_media_from_urlorlist_media). Instagram, TikTok, Pinterest and YouTube posts need media; leave those platforms out if there is none, and say so. - Show the plan. Present a table: date and time, stage, accounts, and the full text. Ask the user to confirm or change it.
- Group it. Call
list_campaignsand reuse a matching campaign, or create one withcreate_campaign(a name like "Spring sale 2026"). - Create the posts. After the user confirms, pick one of two ways and tell the user which:
- Schedule now:
bulk_create_postswith each post'saccount_ids,scheduled_for,timezoneandcampaign_id. The posts are booked and grouped in the campaign. - Save as drafts for a last check in the app:
bulk_create_postswithdraft: trueon each. Drafts are not linked to the campaign. Schedule each one later withschedule_post.
- Schedule now:
- Report back. List every post with its id, date and accounts. Mention anything that failed validation and why.
Changes after scheduling
- To move or edit a scheduled post, use
update_post. To cancel one, usedelete_post. - If the launch date moves, move every post in the campaign. Find them with
list_posts_advancedandcampaign_id.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

