⏳ This skill is pending AI review.

Scores will appear once the review pipeline completes.

v1.0.0

x-audit

jakeschincariol@jakeschincariol⭐ 93 stars· last commit 1mo ago· 0 open issues

>-

Choose how to use this skill

You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.

1. Native installer

This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.

Do not guess an installer command or replace an existing version without reviewing the diff.

2. Complete package recommended

Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.

No complete ProSkills package is published for this listing yet.

3. Prompt-only

Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.

Need only the instruction file?

Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.

No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.

—/10

// RATINGS

⭐GitHub Stars
⭐⭐ 93 on GitHubGitHub ↗

Growing

🟢ProSkills Score
—
📍

Not yet listed on ClawHub or SkillsMP

// README

The X agent skill

Eleven Claude skills that run an X account. Free, MIT, no signup, no API key, nothing to connect.

They write your posts, comment on other people's threads, handle your replies, fix your profile and plan your week. And one of them is the virality skill: it finds the posts that are actually outperforming in your niche, breaks each one down into hook, structure and format, and recreates the winners in your voice, for your audience.

Under the skills are nine tools that actually run. One counts a post the way X counts it (links are 23, emoji are 2). One scores your first line before you post it. One cuts a draft into a thread that fits. One reads X's own published ranking code and tells you what it rewards this week. One reads your analytics export and tells you what worked, with the sample size on every claim.

Nothing is posted until you approve it. These skills write. You post.

Install

Paste this into Claude:

https://github.com/Jakeschincariol/x-agent-skill

Install this skill, then confirm /x-post works.

Or do it yourself, in Claude Code:

git clone https://github.com/Jakeschincariol/x-agent-skill.git
cp -r x-agent-skill/skills/x-* ~/.claude/skills/

Or as a plugin:

/plugin marketplace add Jakeschincariol/x-agent-skill
/plugin install x-agent

Project-local instead of global: copy the same folders into your repo's .claude/skills/. No Claude Code at all? Paste any single SKILL.md at the top of a chat and it runs as a mode. You lose the Python tools, which is most of the point of /x-post, /x-viral and /x-human, but the rest works.

Then spend ten minutes on templates/voice.md. Copy it to ~/.claude/x/voice.md and fill it in, or paste five of your own posts into Claude and say "write my voice.md from these". Every skill reads that file. Skip it and everything comes out sounding like everyone else on the timeline.

The eleven

commandwhat it does
/x-postPost WriterOne idea into a post. Three hooks from 21 formulas, scored, one draft, counted the way X counts, humanized.
/x-commentComment DrafterReplies on other people's posts and threads. Nine types, picked by what the post is. Reply or quote, decided first.
/x-profileProfile OptimizerScores your profile against a 12-part rubric out of 100, then rewrites bio, pinned post and header in fix-first order.
/x-replyReply HandlerThe replies under your own posts, sorted into lead / substance / peer / question / support / noise, then answered in that order.
/x-planContent PlannerThe week: what to post, which format, when, and the 10 accounts to engage with.
/x-viralVirality EngineFinds what is outperforming in your niche, ranks it by multiple over each account's own median, breaks down hook, structure and format, recreates the top three for you.
/x-threadThread BuilderThread, long post or single post, decided first. Then post 1, one idea per post, cut to fit, and a last post people act on.
/x-humanHumanizerStrips em dashes, slop and invisible characters, then scores the draft on a five-check panel.
/x-repurposeRepurposerOne video, podcast, newsletter or LinkedIn post into a week of X posts and a thread.
/x-dmDM HandlerThe first message, two follow-ups, and triage for your inbox and message requests.
/x-auditAccount AuditReads your analytics export. Ranks by engagement, replies and shares per impression, not by impressions.

The nine tools

Every one runs on a clean Python 3 with no dependencies. Seven never touch the network. pull.py calls X's documented oEmbed API and weights.py reads a public GitHub file; neither needs an account or a key.

python3 skills/x-post/count.py post.txt                   # X's weighted count + six lints
python3 skills/x-post/hookscore.py hooks.txt              # score and rank first lines, name the formula
python3 skills/x-thread/thread.py draft.txt --number      # cut a draft into a thread that fits
python3 skills/x-human/humanize.py draft.txt --report     # strip the fingerprint
python3 skills/x-human/detect.py before.txt after.txt     # five-check panel, before and after
python3 skills/x-viral/pull.py urls.txt > swipe.tsv       # post URLs you picked -> text, format, date
python3 skills/x-viral/swipe.py swipe.tsv                 # outliers, broken down, as a swipe file
python3 skills/x-audit/audit.py analytics.csv             # what worked, with n on every claim
python3 skills/x-plan/weights.py                          # what X's ranker rewards, live from X's code

Counting the way X counts

X does not count characters. It counts weighted characters: every link is 23 however long it is, every emoji is 2 (a family emoji built from seven code points is still 2), Chinese, Japanese and Korean are 2, and "…" is 2, which is more than the three dots it replaces. count.py implements those rules, then draws the post the way the timeline shows it:

  WHAT FITS
  +------------------------------------------------------+
  | Most people use AI to post more. I used it to post   |
  | less.                                                |
  |                                                      |
  | In March I cut from 3 posts a day to 1. Followers    |
  | went from 2,100 to 6,800 by August.                  |
  |                                                      |
  | The system: one idea a day, drafted with Claude, cut |
  | in half by me, and I'm there for the first hour of   |
  | replies.                                             |
  |                                                      |
  | Showing up beats post                                |
  +------------------------------------ cut here, 4 over +

  FAIL  LENGTH      284 / 280, 4 over. X will not let you post it.
  PASS  FIRST LINE  56 characters, reads in one glance
  PASS  LINKS       none
  PASS  HASHTAGS    0
  PASS  MENTIONS    0
  PASS  ENDING      no reflex bait

With --premium the limit is 25,000 and the box shows where the timeline cuts a long post to "Show more", at about 280. It also flags an @mention past that point, because X does not notify it.

The hook

On X the first line is not the start of the post. It is most of the post. hookscore.py scores it on five properties (length, specificity, stakes, whether the payoff is up front, who it is aimed at), flags the dealbreakers, and names which of the 21 formulas it uses:

HOOK RANKING
==============================================================================
-> 100.0 STRONG  Nobody tells you your first 1,000 followers come from rep...
        #6 Nobody Tells You  ·  weakest: LENGTH (100)
    78.4 STRONG  I posted every day for 90 days. Here's what actually move...
        #2 Number Reveal  ·  weakest: FRONTLOAD (70)
    52.2 OK      The hottest new marketing hire is a skill file.
        #7 The Hottest New  ·  weakest: SPECIFICITY (15)
    36.2 WEAK    Hey guys, here are some thoughts on growing on X
        #21 The One-Liner  ·  weakest: STAKES (20)
        dealbreaker: Greeting. Nobody opened X to be greeted.
     4.8 WEAK    A thread 🧵
        #16 Thread Promise  ·  weakest: FRONTLOAD (0)
        dealbreaker: Opens on the word "thread". That is packaging. Put the
                     payoff in line 1 and let X's own UI say it is a thread.

Every formula in hooks.json carries a template, a filled example, what it is for, how it usually gets ruined, and a regex, so the same 21 names describe a hook you are writing and a hook you found in someone else's feed. That is what lets /x-viral say "the top third of your niche is The Hottest New and Field Report" instead of "posts that did well".

The virality engine

python3 skills/x-viral/pull.py urls.txt > swi

// HOW IT'S BUILT

// FILES

2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.

  • skills/x-audit/SKILL.md4.2 KBupstream ↗
    ---
    name: x-audit
    description: >-
      Post-mortem on what the user has already published on X - which posts
      actually worked, why, and what to stop doing - from their own analytics
      export. Use when the user shares their X analytics CSV or past posts and
      asks "what's working", "why did this flop", "read my analytics", "audit my
      account", "what should I double down on", or wants to know whether links,
      threads or a posting time actually matter for them.
    ---
    
    # x-audit
    
    The only honest source of what works for an account is that account. Every
    rule in every X guide, including the ones in this pack, is a prior. The
    user's own last 30 posts are the evidence.
    
    One tool lives in this folder and it runs:
    
    ```bash
    python3 audit.py account_analytics_content.csv
    ```
    
    ## Input
    
    In order of preference:
    
    1. **The analytics export.** On desktop: x.com/i/account_analytics, then
       Export. It is a Premium feature. One row per post: impressions plus the
       engagement counts (likes, replies, reposts, bookmarks, shares, new
       follows, profile visits). X does not document the column names and they
       have changed before, so `audit.py` matches them loosely; the older
       analytics.twitter.com export parses too.
    2. **A sheet by hand** with post text, impressions, and whatever counts the
       user can see. Twenty rows is enough for a first pass.
    3. **Screenshots** of the posts with their numbers. Transcribe into a CSV.
    
    Also read `~/.claude/x/log.md` if it exists: it records which hook formula
    each post used.
    
    ## What it measures, and why not impressions
    
    Impressions are mostly a function of how many people already follow the user.
    `audit.py` ranks on things that are not:
    
    | metric | what it tells you |
    | --- | --- |
    | **Engagement rate** | whether the post earned the reach it got |
    | **Replies per 1k impressions** | whether it started a conversation. X's ranker weighs replies far above likes |
    | **Shares per 1k** (reposts + shares) | whether it travelled. Shares by DM or copied link are among the highest-weighted actions X publishes |
    | **Bookmarks per 1k** | whether someone plans to use it |
    | **Follows per 1k** | whether it made anyone want more of the user |
    
    Posts under a noise floor of impressions are left out of the ranking, and the
    user's replies on other people's posts (rows starting with @) are counted and
    set aside so a good week of replying does not drown the posts.
    
    ## Then find the pattern
    
    `audit.py` groups the posts by hook formula (classified with
    `../x-post/hooks.json`), by length, and by format (text only vs with a link
    or media), and reports every group whose engagement rate is 1.4x above or
    below everything else, with its n and a confidence word. It checks day of
    week **last**, and only mentions it when nothing else separates. It is almost
    never the cause, and it is where people want it to be.
    
    Add what the script cannot see, reading the top 5 and bottom 5 side by side:
    
    - Topic. Which of the user's themes are in the top five?
    - Whether the user replied in the first hour.
    - Whether the post was the user looking good or the user looking bad.
    
    **The link question, answered with their own data.** X says it stopped
    down-ranking link posts over a year ago. An independent analysis in January
    2026 still measured fewer views on them. If the format finding shows link
    posts well below the rest with n of 5 or more, that is the answer for this
    account, whatever anyone says. If it shows nothing, links are fine here.
    
    State every finding as a claim with the evidence attached, and say how
    confident it is. With 30 posts a pattern can show. With 8, say that instead
    of inventing one.
    
    ## Output
    
    ```
    AUDIT  ·  38 posts  ·  Jul 01 - Aug 28  ·  15 replies set aside
    
    TOP BY ENGAGEMENT RATE
        5.8%    8.6 rep/1k    8.6 shr/1k     5,705 imp  "$4,000 is what one bad hire cost me."
        ...
    
    WHAT THE DATA SAYS
      1. format = text only: 2.7% vs 0.8% for everything else (3.3x, above). n=26, solid.
      2. hook formula = Cost Confession: 3.9% vs 1.9% (2.0x, above). n=4, weak.
      Day of week shows nothing. Stop optimising it.
    
    STOP:     link-first posts. Put the link in a reply for the next ten and re-run.
    DO MORE:  the posts where you paid a cost, with the number in line 1.
    ```
    
    Then hand the conclusions to `/x-plan`, so next week is built on the user's
    own evidence instead of on defaults.
    
  • README.mdupstream ↗

    Contents are not inlined in the catalog. Open the upstream file.

Plain-text copy, no login: /skill-bundles/jakeschincariol-x-agent-skill-skills-x-audit.md

// REPO STATS

93 stars
0 open issues
Last commit: 1mo ago