sxsphinxstack

Skills / Social post

Social post

Announce something the person made in their own words. Covers one suitable platform, a truthful draft, checked media and link, publication, and follow-up. Use when they say "how do I announce this", "help me post about my project", or they shipped something and nobody knows.

Use this skill. Nothing to install.

Open in ChatGPT Open in Claude prefilled and ready; just hit send
for Gemini, Copilot, or Cursor: paste it, then say "use the social post skill"

Don't have an agent?  ·  Raw file: skills/social-post.md

Watch the first two minutes

This is how a session goes, including what happens to the first draft. Click through it.

​(pastes the skill) I finished my bus tracker site last week and literally nobody knows it exists. posting about it feels so cringe though
The cringe fear is normal, and shipping into silence is the actual loss. First: where do the people who'd care about a transit site hang out, and where do you already have any presence at all? We post to one platform, today.
I have like 40 followers on X, mostly people from my school and a few devs. draft: "so I made a little thing, it's probably nothing, but if anyone's bored here's a link lol"
That's the humility throat-clear, and it's a costume, same as "thrilled to announce!!" would be. Both get cut. Try again as a plain statement of fact: what did you build? Lead with the thing.
"I built a site that shows where the 42 bus actually is, live, because the posted schedule at my stop is wrong." then the link?
Yes. Read it out loud: would you say that sentence to a classmate while showing them the site on your laptop? That's the test, and it passes. Now the image, because the image is what stops the scroll. Screenshot of the map with the bus mid-route, taken now.
done. should I add hashtags? #coding #webdev #buildinpublic #transit #maps
That's hashtag salad; zero to two, and only ones a human follows. Keep #buildinpublic if you actually read it, drop the rest. Test the link logged out, then press post while I'm here. If it gets replies, answer them today like a person. If it gets silence, that's the most likely outcome for a first post and means nothing about the work.

Scripted example of a real session.

Isn't posting about my own stuff cringe?

Cringe is a style problem and styles can be cut. What reads as cringe is the costume: false humility on one side, hype voice on the other. A plain statement of what you made, with a picture and a working link, reads as confidence, and it's the post you'd want to see from someone else. The skill also keeps you honest on frequency: one post per real event. An account that only announces real things builds exactly the reputation you want.

What you end up with

One post, live, in your words. Same announcement, before and after the workshop.

Example
BEFORE 1
so I made a little thing, it's probably nothing, but if anyone's bored here's a link lol 🚀🚀 #coding #webdev #buildinpublic #transit #maps
AFTER 2
I built a site that shows where the 42 bus actually is, live. The posted schedule at my stop is wrong more often than it's right, so I stopped trusting it and started tracking the bus instead.
busmap.example.dev
[screenshot: the map, bus marker mid-route] 3
  1. The before asks the reader to do the believing. "Probably nothing" begs for reassurance, the rockets fake excitement, and five hashtags spray at nobody in particular. Every element is a costume.
  2. The after is facts a stranger can check. The thing, then the honest itch it scratches, in words you'd use out loud. Nobody owes the post a read; the first sentence earns the second.
  3. The image does the stopping. On every platform the picture stops the scroll, so capturing a good one is part of the session, and the link gets tested logged out before posting.

Anatomy of the first sentence

The workshop pushes your opening line into this shape:

I built a site that shows where the 42 bus actually is, live. busmap.example.dev

Questions people actually ask

Is this free?

The skill is free, no account, no catch. The agent you paste it into may or may not be: Gemini has the widest free tier, Copilot's free tier is enough to try it, ChatGPT and Claude free plans can also run it in a chat.

Will my post sound like AI wrote it?

The skill treats machine tells as cuts on sight: "I'm excited to share", rocket emoji clusters, rhythmic feature lists. If it sounds like a press release it gets scrolled past like one. The standard is the read-aloud test, would you say this sentence to a classmate, and you write every word that survives it.

Which platform should I post on?

The one where people who'd care about your thing actually are, and where you already have any presence: X or Bluesky for code, Instagram or TikTok for visual and physical things, LinkedIn for professional stuff, Show HN if the project genuinely stands alone. One platform on day one; cross-posting can come later if it lands.

What if I get zero likes?

Silence is the most likely outcome for a first post, and the skill says so before you post. It means nothing about the work. The post now exists as the link you send when anyone asks what you've been doing, and it gets saved next to the project as part of its public record.

How often should I post?

One post per real event. Ship something, announce it, done. When the next real thing ships, run the skill again. No content calendar, no posting for the algorithm.

Where to go from here

Nothing shipped yet? Make the thing worth announcing:

A real site, live at a URL Browser game at a URL Discord bot your server uses

Announcement out? Build the longer surfaces:

Blog post LinkedIn profile Newsletter issue
Curious? Read the full skill — the exact instructions your agent gets 
---
name: social-post
category: write
description: Announce something the person made in their own words. Covers one suitable platform, a truthful draft, checked media and link, publication, and follow-up. Use when they say "how do I announce this", "help me post about my project", or they shipped something and nobody knows.
---

# social-post

Help someone announce a thing they made — a project, a
site, a first blog post — to people who do not know it exists. The
task is to state what was made, show it, and link it without hype. Say
what you made, show it, link it, in the words you would use with a
friend. They write it, you push back, and it gets posted before the
session ends.

## One platform, picked for the audience

Ask where the people who would care about this thing actually are.
A code project: X or Bluesky where developers hang out, or a Show
HN if it genuinely stands alone. A design or physical thing:
Instagram or TikTok. Professional or internship-adjacent: LinkedIn.
Post to one platform, the one where they already have any presence
at all. Start on one platform so the person can check the public result and
respond; other platforms can come later.

## The post

Have them draft it, then workshop. What works:

- Lead with the thing, not the journey. "I built a site that tracks
  every bus in Pune in real time" — then the link.
- One honest line on why: the itch it scratches, in their words.
- Show it: screenshot, GIF, or short clip. On every platform the
  image is what stops the scroll; help them capture a good one now.
- The link, working, tested logged-out.

What gets cut, every time:

- The humility throat-clear ("so I made a little thing, it's
  probably nothing...") and its cousin the hype voice ("thrilled to
  announce!!"). Both are costumes. Plain statement of fact reads as
  confidence.
- The lifestory preamble. Nobody owes the post a read; earn the
  second sentence with the first.
- Machine-writing tells: "I'm excited to share", rocket emoji
  clusters, a rhythmic triple list of features. If it sounds like a
  press release, it will be scrolled past like one.
- Hashtag salad. Zero to two, only ones a human actually follows.

The read-aloud test settles arguments: would they say this sentence
to a classmate showing them the thing on a laptop? If not, rewrite
until they would.

## Post it, then stay

- They press post in the session. Not scheduled, not saved to
  drafts. This is the whole point of the skill.
- Replies get answered, same day, like a person — questions
  especially. A maker who responds is half of what makes a post
  land.
- Silence is the most likely outcome for a first post and means
  nothing about the work. The post now exists as the thing they
  link when anyone asks what they have been doing.
- Save the post link next to the project (README, resume notes).
  It is now part of the project's public record.

## Done

- One truthful post published from the person's account on the chosen platform
- Media and link checked from the public view; no private information exposed
- Post URL saved with the project and replies assigned to the person

One post per real event. When they ship the next thing, run this
again — an account that only ever announces real things builds
exactly the reputation they want.