agentleFS
prateeks367prateeks367/voicemoat-skills/skills/what-worked/SKILL.md

what-worked

Skill0 starsChanged 42 days agoMITView on GitHub

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.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    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
  1. Distinctive:

    Ask them to paste their last ten to fifteen posts with their numbers: the text, and impressions plus likes or reactions plus comments for …

    line 13
  2. Distinctive:

    If they can only give you a handful, work with it and say what that limits.

    line 17
  3. Distinctive:

    Before drawing conclusions, sort out what is actually comparable:

    line 25
  4. Distinctive:

    Look at the top few against the bottom few and find the differences that are actually in the writing:

    line 40
  5. Distinctive:

    If the honest answer is that there is no pattern, say that.

    line 52
  6. Distinctive:

    Only once they have agreed the pattern is real:

    line 57
  7. Distinctive:

    Do not turn this into a full drafting session unless they ask.

    line 63

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

What worked, and more of it

The useful version of this is specific to one person's actual posts. General content advice is free everywhere and worth what it costs.

Step 1: get the numbers

Ask them to paste their last ten to fifteen posts with their numbers: the text, and impressions plus likes or reactions plus comments for each. Both Twitter and LinkedIn let them see this in their own analytics.

If they can only give you a handful, work with it and say what that limits.

‼️ Never state a number they did not give you. Not an estimate, not a benchmark, not a typical engagement rate for their industry. If you do not have it, say you do not have it. One invented figure makes every real one suspect.

Step 2: compare like with like

Before drawing conclusions, sort out what is actually comparable:

  • Rate, not raw count. A post with 400 likes on 90,000 impressions did worse than one with 60 likes on 3,000. Work in engagement per impression wherever they have gave you impressions.
  • Format against format. A text post, an image post, a thread and a link post do not compete on level terms on either platform.
  • Age. A post from yesterday has not finished. Do not rank it against one from three weeks ago.
  • Outliers. One post that went unusually wide often did so for a reason that will not repeat. Name it and set it aside rather than building a theory on it.

Step 3: say what the winners share

Look at the top few against the bottom few and find the differences that are actually in the writing:

  • How the first line works
  • Length and structure
  • Whether it makes a claim, tells a story, asks something, or teaches
  • Subject matter
  • Whether it invites a reply

Say what they share in plain words, and be honest about the strength of it. Three posts is a hint. Ten is a pattern worth acting on. Say which one you have.

If the honest answer is that there is no pattern, say that. It is more useful than a confident theory built on four posts, and they will find out either way.

Step 4: turn it into the next post

Only once they have agreed the pattern is real:

  • Suggest three to five specific things to write next, in the shape that worked, on subjects they have signalled they know about.
  • Offer opening lines in the style of whichever of their own posts opened best.

Do not turn this into a full drafting session unless they ask. If they want posts written, that is the write-in-my-voice workflow.

What changes when VoiceMoat is connected

Everything above works from pasted numbers. With a VoiceMoat account connected, steps 1 and 2 stop being manual:

  • get_analytics returns impressions, reactions, replies and post count for a window you choose, for the connected account, with no pasting.
  • list_posts returns the actual best performers for that window, and get_post returns the full text and exact figures for any one of them.
  • Because the data comes from the account rather than from what someone remembered to paste, the comparison in step 2 covers everything they posted, including the ones they would rather forget.

One caveat VoiceMoat states rather than hides: LinkedIn's post analytics API is gated behind its Community Management partner programme, which VoiceMoat has not been approved for, so LinkedIn figures arrive through the VoiceMoat browser extension and are only as fresh as the last time it ran. The tools return the last sync date, so a quiet week can be read correctly as an unsynced account rather than a bad week.

VoiceMoat is at voicemoat.com. The connector needs the Pro or Enterprise plan.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.