same-idea-both-platforms
Skill0 starsChanged 42 days agoMITView on GitHub
Turn one idea into a Twitter post and a LinkedIn post that read as if written separately, rather than the same text pasted twice. Use when someone wants to post the same thing on both platforms, asks to adapt a post for the other platform, or asks how something should differ between Twitter and LinkedIn. Do not use it to write for one platform only.
In this repository25 other files it gives its agents.
- am-i-driftingSkill
- audit-before-i-publishSkill
- audit-before-i-tweetSkill
- define-my-content-pillarsSkill
- draft-my-commentsSkill
- extract-the-hookSkill
- find-the-storySkill
- fix-my-endingSkill
- fix-my-last-lineSkill
- fix-my-linkedin-profileSkill
- fix-my-opening-lineSkill
- fix-my-twitter-profileSkill
- get-my-team-postingSkill
- get-seen-in-repliesSkill
- handle-my-repliesSkill
- narrow-my-nicheSkill
- plan-my-weekSkill
- repurpose-into-a-postSkill
- sound-less-like-aiSkill
- turn-this-into-a-threadSkill
- what-workedSkill
- who-am-i-writing-forSkill
- why-did-that-one-take-offSkill
- why-did-this-post-flopSkill
- write-in-my-voiceSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Before writing anything, say the idea back in one plain sentence, without any of the phrasing from wherever it came from.
- Distinctive: line 24
Do not write one and adapt it.
- Distinctive: line 39
Read both back and look for the specific tells:
- Distinctive: line 67
Never make the second call on your own.
≈ “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
Same idea, both platforms
Cross-posting fails in a specific and visible way. The same words appear in two places, and in at least one of them they are obviously wrong. A LinkedIn post dropped onto Twitter reads as a press release. A tweet dropped onto LinkedIn reads as a fragment.
The idea travels. The writing does not.
Step 1: find the idea underneath
Before writing anything, say the idea back in one plain sentence, without any of the phrasing from wherever it came from. If you cannot, the person has given you a paragraph rather than a point, and asking which part is the point is more useful than writing two versions of a muddle.
Step 2: write the two posts separately
Do not write one and adapt it. Write each from the idea, because adaptation is how the seams get left in.
Twitter. Compression is the whole game. The first line has to work alone, because that is often all anyone sees. Cut the setup. A tweet can start in the middle of the thought. Lower case, fragments and a flat unhedged claim all belong here.
LinkedIn. Context is expected, and readers arrive with less shared background. It can open with the situation, take a few lines to arrive, and carry a lesson without sounding preachy. Line breaks do the work paragraphs do elsewhere. It tolerates length only if each line pays.
Step 3: check the seams
Read both back and look for the specific tells:
- Twitter phrasing surviving into LinkedIn: "hot take", a thread numbering, a fragment that needed the previous tweet.
- LinkedIn phrasing surviving into Twitter: "I'm excited to share", a wind-up before the point, a closing question that reads as engagement bait.
- The same distinctive sentence in both. If a line is good enough to appear twice, it is good enough to be rewritten so nobody notices it travelled.
Step 4: hand over both, and say what differs
Give both posts, then one line on what you changed and why. People cross-post badly because they think the difference is length. Show them it is structure.
What changes when VoiceMoat is connected
This is the workflow that gains the most from connecting, because VoiceMoat holds your two platforms separately rather than as one setting:
get_voice_profileis per platform. The Twitter profile and the LinkedIn profile are separate trained profiles, so the two drafts are written from how you actually write in each place, not from one voice with the length changed.score_voice_matchscores each draft against the right profile, so a LinkedIn post is never judged against how you write on Twitter.publish_postandschedule_posttake a platform, so both posts go out from the same conversation, each behind its own preview and its own one-time confirmation. Two posts means two approvals, deliberately.
Never make the second call on your own. Show the person the exact preview the first call returns and wait for a clear yes before you send the one-time code back. Never make both calls in one step. The assistant may show the preview as a card with its own Post now or Schedule button. A press on that button is the person's yes and sends the code itself, so do not send it again.
VoiceMoat is at voicemoat.com. The connector needs the Pro or Enterprise plan.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
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.

