voicemoat-skills

Compare how someone writes now against how they used to write, and name what has changed. Use when someone asks whether they still sound like themselves, whether their posts have got worse or blander, whether AI has flattened their writing, or wants their recent posts compared with their older ones. Do not use it to compare one person against another person.

Run a finished draft through one pre-publish pass and rank what to fix. Use when someone says a post is ready, asks for a final check, asks whether to post something as it stands, or pastes a draft and asks what is wrong with it. Do not use it to write a post from nothing, do not rewrite a whole draft when one line is the problem, and do not predict performance.

Run a finished tweet through one pre-publish pass and rank what to fix. Use when someone says a tweet is ready, asks for a last look, asks whether to post something as it stands, or pastes a draft and asks what is wrong with it. Do not use it to write a tweet from nothing, do not rewrite a draft when one word is the problem, and do not predict performance.

Work out the three to five subjects someone can post about repeatedly without running dry, from what they have already published and what they actually know. Use when someone asks what they should post about, says they have run out of ideas, wants content pillars or themes, or is starting an account and does not know where to aim. Do not use it to plan dates or write posts.

Turn a post you want to be seen under into a comment that adds something, not the agreement everyone else left. Use when someone asks what to comment, wants to engage with creators in their space, says their comments go nowhere, or pastes a post and asks for a reply to it. Do not write flattery, do not disguise an advert as a comment, and do not promise the comment will be seen.

Pull the openings out of posts that worked and name the shape underneath, so you reuse a pattern rather than copying a line. Use when someone wants a hook library, asks what makes an opening work, has collected posts they admire, or keeps writing the same first line. Do not reproduce anyone else's wording, and do not attach performance figures to a pattern.

Interview someone about something that actually happened until there is a story worth telling, then write it without bolting a lesson on the end. Use when someone says they have nothing to write about, has a vague idea they cannot shape, wants to write about an experience, or asks for a personal post. Do not invent details they did not give you, and do not inflate a small thing into a parable.

Diagnose why a post's ending is not earning a reply, then rewrite it or remove it. Use when someone asks for a call to action, says nobody comments, asks how to end a post, or has closed with a question that reads as asking a favour. Do not bolt an engagement prompt onto a post that was already finished, and do not promise that a new ending will bring comments.

Work out whether a tweet's last line is earning its place, and usually delete it. Use when a tweet feels flat at the end, when someone asks how to close a tweet, when they want a call to action on one, or when a draft trails off without landing. Do not add engagement bait, do not promise replies, and do not treat a missing ending as a problem needing a solution.

Go through headline, about and featured in the order a visitor reads them, and rewrite whichever one is losing the click. Use when someone asks for a profile review, has a new role or a new offer, says their profile gets views and nothing else, or wants their headline rewritten. Do not stuff keywords, do not promise search placement, and do not rewrite the parts that are already working.

Diagnose why a post's opening line is not stopping anyone, and rewrite it from several genuinely different angles. Use when someone says a post flopped, asks for a better hook, first line or opener, asks why nobody read something, or is stuck on how to start. Do not use it to write the whole post, and do not promise that a new opening will make a post perform.

Go through name, bio and pinned tweet in the order a visitor reads them, and fix whichever one is losing the follow. Use when someone asks for a profile review, has a new role or a new offer, says people visit and do not follow, or wants their bio rewritten. Do not stuff keywords, do not promise followers, and do not rewrite the parts that are already working.

Turn one company message into posts each colleague can publish in their own words, instead of six people posting the same paragraph. Use when a company wants employees posting, a launch needs internal support, or a team was handed copy to share. Do not write one post for everyone to paste, do not write in a voice they would not recognise, and never ask anyone to post what they disagree with.

Write a reply to somebody else's tweet that is worth reading on its own, rather than one that disappears. Use when someone asks what to reply, wants to grow by engaging, says their replies go nowhere, or pastes a tweet and asks for a response to it. Do not write flattery, do not write a reply that is a disguised advert, and do not promise the reply will be seen.

Sort the replies under a post into the ones worth answering, the ones worth a reaction and the ones to leave, then draft answers. Use when someone has replies they have not worked through, asks how to respond to a comment, is facing a hostile reply, or is keeping up with a post that did well. Do not answer every reply, do not feed an argument, and never send anything unread.

Get from a subject someone could write about to one they could own, and say out loud what they are giving up to do it. Use when someone says their content feels scattered, cannot describe what they post about, is choosing between two audiences, or asks how to position themselves. Do not pick the niche for them, and do not promise that narrowing will grow an account.

Plan a week or a month of Twitter or LinkedIn posts as a dated calendar, with a topic, format, opening line and purpose for each one. Use when someone asks for a content plan, a posting schedule, a content calendar, a week of posts, or help posting consistently. Do not use it to write one post, and do not schedule or publish anything without the person seeing it first.

Turn an article, newsletter, transcript, video or long document into a Twitter or LinkedIn post that stands on its own. Use when someone wants to repurpose existing content, share a link, promote a piece they published, or turn a recording or long draft into something postable. Do not use it to write from scratch, and do not produce a summary with a link attached.

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.

Rewrite text so it stops reading as machine-written, by naming the specific tells and removing them. Use when someone says a draft sounds like AI, sounds generic, sounds corporate, or asks to humanise or de-AI a piece of writing. Do not use it to help anyone pass off writing as human where being honest about authorship matters, such as academic work or disclosures.

Turn a long idea, transcript, article or rambling draft into a Twitter thread where every tweet earns the next one. Use when someone asks for a thread, asks to break something long into tweets, or has a piece of writing too long for one post. Do not use it for LinkedIn, which has no threads, and do not pad a small idea into a long thread.

Work out what a person's best-performing Twitter or LinkedIn posts have in common, and turn that into what to write next. Use when someone asks why a post did well or badly, what their best posts have in common, what to write more of, or wants their recent posts reviewed against their numbers. Do not invent engagement numbers, and do not use this to analyse someone else's account.

Build a picture of the person on the other end from real posts and real responses rather than from a persona template. Use when someone does not know who they are writing for, is attracting the wrong audience, wants to check who is actually reading, or asks for a customer persona. Do not invent a named person with a photo and a coffee order, and do not guess demographics that cannot be seen.

Take apart a post that did unusually well and separate what is repeatable from what was timing and luck. Use when someone asks why a post worked, wants to repeat a hit, is studying a creator's best post, or has one outlier in an otherwise flat month. Do not credit the writing for everything, do not turn a single post into a rule, and do not state a cause you cannot support.

Work out why one specific post underperformed, by separating whether it was not seen, seen and skipped, or read and ignored. Use when someone asks why a post did badly, why nobody engaged, why a post they were proud of went nowhere, or wants one post diagnosed. Do not use it to review a whole account, and do not guess at numbers the person has not given you.

Draft a Twitter or LinkedIn post that sounds like the person asking, by working out their voice from writing they have already published and checking the draft against it. Use when someone asks for a post, a thread, a hook or a rewrite, or asks whether a piece of text sounds like them. Do not use it for writing that is not going on social media.