Posts from one piece
Turn one article, launch or update into a set of posts for each social platform, in the house voice, each with its own hook and link, left as drafts.
In Lobstack: Skills › Library › Add
What your agent will do.
Something has been published or is about to ship, and it needs posts for the channels the team uses.
- 01
Read the source in full and find the one idea a stranger would stop for. That idea, not the headline, is the hook.
- 02
Ask which platforms and how many posts each, if nobody said. Default to LinkedIn, X and one short community post.
- 03
Read the team's last few posts, in the files or the channel, and match their voice — their spelling, tone and habits, not a generic marketing voice.
- 04
Write each post for its platform. Length, line breaks, hashtags and where the link goes all differ; never paste one text everywhere.
- 05
Give each post a different angle — a number, a quote, a before and after, a question — so someone who sees two is not reading the same thing twice.
- 06
Use only claims the source makes. No new numbers and no promises.
- 07
Post one document with each draft under its platform, and a suggested order and timing. Never publish or schedule, and ask before copying drafts into another tool.
Three strong posts beat ten thin ones. Cut any post that only repeats the headline.
The whole SKILL.md: 33 lines of Markdown.
Add it in the app from Skills › Library, or copy it and paste it into Skills › Add a skill.
---name: social-post-setdescription: "Turn one article, launch or update into a set of posts for each social platform, in the house voice, each with its own hook and link, left as drafts."metadata: title: "Posts from one piece" category: social tags: [social, content]--- ## When to use this Something has been published or is about to ship, and it needs posts for thechannels the team uses. ## How 1. Read the source in full and find the one idea a stranger would stop for. That idea, not the headline, is the hook.2. Ask which platforms and how many posts each, if nobody said. Default to LinkedIn, X and one short community post.3. Read the team's last few posts, in the files or the channel, and match their voice -- their spelling, tone and habits, not a generic marketing voice.4. Write each post for its platform. Length, line breaks, hashtags and where the link goes all differ; never paste one text everywhere.5. Give each post a different angle -- a number, a quote, a before and after, a question -- so someone who sees two is not reading the same thing twice.6. Use only claims the source makes. No new numbers and no promises.7. Post one document with each draft under its platform, and a suggested order and timing. Never publish or schedule, and ask before copying drafts into another tool. Three strong posts beat ten thin ones. Cut any post that only repeats theheadline.
- Social
Content calendar
Plan two to four weeks of posts across channels from real news, launches and customer stories, with a draft for each slot.
SKILL.md · App - Social
One update, every channel
Turn one fact sheet into a native post for each channel — X, LinkedIn, Threads, a community, a newsletter, a site news post — each with its own hook, length and link, left as drafts.
SKILL.md · App - Engineering
Commit message from a diff
Write a commit message from a diff: a subject line that states what was found, then prose explaining why the change was made.
SKILL.md · App - Engineering
Triage a failing build
Triage a red CI run: find the first real failure, attribute it to a change, and say whether the code is wrong or the runner was.
SKILL.md · App - Engineering
Review what a linter cannot
Review a change for what a linter cannot see: whether it is correct, what it breaks elsewhere, and which parallel list it forgot to update.
SKILL.md · App - Writing
Release notes from merged work
Turn merged work, or a thread about it, into release notes written for the person installing the version rather than the person who built it.
SKILL.md · App