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.
In Lobstack: Skills › Library › Add
What your agent will do.
Something shipped or happened and it should go out on several channels without the same paragraph pasted everywhere.
- 01
Write a fact sheet first: what changed, who it is for, one number or example, the link. Every post is cut from it, so nothing drifts.
- 02
Read the last five posts on each channel and match that voice.
- 03
Write each one in its own shape: X short and concrete; LinkedIn a few short paragraphs from the builder's side; a community post plain and friendly; a newsletter item one paragraph; a site post with a headline that says what the reader gets.
- 04
One point and one link per post. Mark any that needs an image.
- 05
Show every draft side by side with its channel, link and suggested time.
Drafts only. Publishing is a person's yes, per channel. Never invent a customer, a quote or a number the fact sheet does not hold.
The whole SKILL.md: 28 lines of Markdown.
Add it in the app from Skills › Library, or copy it and paste it into Skills › Add a skill.
---name: channel-adapt-postdescription: "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."metadata: title: "One update, every channel" category: social tags: [social, distribution]--- ## When to use this Something shipped or happened and it should go out on several channelswithout the same paragraph pasted everywhere. ## How 1. Write a fact sheet first: what changed, who it is for, one number or example, the link. Every post is cut from it, so nothing drifts.2. Read the last five posts on each channel and match that voice.3. Write each one in its own shape: X short and concrete; LinkedIn a few short paragraphs from the builder's side; a community post plain and friendly; a newsletter item one paragraph; a site post with a headline that says what the reader gets.4. One point and one link per post. Mark any that needs an image.5. Show every draft side by side with its channel, link and suggested time. Drafts only. Publishing is a person's yes, per channel. Never invent acustomer, a quote or a number the fact sheet does not hold.
- Social
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.
SKILL.md · App - 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 - 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