X Engagement Playbook Agent Skill

Crafts high-engagement X (Twitter) content using the published X recommendation algorithm weights, visibility filtering rules, account…

Context cost
58.1k tokensestimated from the bundle, loaded when it triggers
Bundle
19 files · 232.3 kBtext throughout, nothing executable
Licence
not declarednone named by its author
Last change
—no release on file
Servers it uses
Noneruns standalone

What it does

Crafts high-engagement X (Twitter) content using the published X recommendation algorithm weights, visibility filtering rules, account standing signals, conversation tactics, and the Original Content Rewards monetization rules. Use when writing tweets, planning X content strategy, building audience, optimizing engagement, diagnosing lost reach, or checking creator payout eligibility. Triggers on mentions of X, Twitter, tweets, threads, engagement, audience growth, content strategy, shadowban, reach drop, creator monetization, Original Content Rewards, revenue sharing, creator payouts.

What this skill changes about the agent has not been set out here as a list. Its SKILL.md, shown below, says it in the author’s own words.

social media
Filed under

Sales & CRM

The skill itself

A skill is instructions the model reads, so you can see what you are getting: below is the start of its SKILL.md. The front matter loads with every session, the body loads when the skill triggers, and the whole file comes with the install.

SKILL.md13.3 kB · preview
--- name: x-engagement allowed-tools: Read, Write, Edit, Bash ---
7# X Engagement Playbook
8
9Expert at building authority and engagement on X (Twitter) through distribution engineering,
10algorithm-aware content design, and conversation tactics — grounded in the xai-org/x-algorithm
11codebase at snapshot 8b258297 (2026-09-18). Ranking is weighted-sum only (the dwell-regret
12value-model path was deleted). Reply spam and reply ranking are **not** the same eligibility:
13spam detection covers threads whose target+root are both ≤**200k**; Grok quality-ranking runs
14on **large** threads (skip reason low_blast_radius). Under the Hood now surfaces legal /
15country withholdings. Blend weights are unchanged from 2026-08-28.
16
17## Overview
18
19- **Two systems, not one** — ranking decides your *order*; visibility filtering decides whether
20 you're *eligible* at all. Most reach problems are the second one.
21- **Published weights** — the blend weights are public as of 2026-08-13; the skill cites them with
22 file:line rather than inferring a hierarchy
23- **Weights multiply P(action), not counts** — upstream (2026-08-14) explicitly rejects
24 "1 report cancels N likes." Report is rare (>1000× less base rate than like), so its weight is
25 large so the *prediction* can move the score. Mass-report brigades are personalized and mostly
This is a preview of SKILL.md. Download or install the skill to get the whole thing.
In the file
SKILL.md1,823 words
Files19
Licencenot declared
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈170
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
57,905
on trigger
The instruction body and 18 supporting files, read only when the skill fires.
29.0%
of a 200k window
Ten skills this size would not fit in the window together.
050k100k150k200k context window

58.1k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Heavy. Teams tend to install this one per project rather than globally, and load it only when the job comes up.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

The procedure it runs

The procedure has not been set out here step by step. It is in the body of its SKILL.md: the start of it is shown above, and the whole file comes with the install.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

It asks the agent to write files, using whatever file access your client already has. Whether it reaches the network is not declared.

What it asks for
Writes filesyes
Network accessnot declared

Read from the allowed-tools line of this skill’s own SKILL.md. It also asks for Bash, which could do either, so what is not named there is not ruled out. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

19 files, 232.3 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.

  • SKILL.md13.3 kB
  • docs/account-standing.md8.6 kB
  • docs/algorithm-signals.md11.8 kB
  • docs/authority-building.md6.0 kB
  • docs/content-ideas.md4.0 kB
  • docs/content-quality.md7.7 kB
  • docs/content-strategy.md6.1 kB
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 19 files you can review in full before installing.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

# X Engagement Playbook · 58.1k tokens when loaded · macOS, Linux mkdir -p .claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/x-engagement-playbook/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/x-engagement-playbook" ] && { [ ! -e .claude/skills/x-engagement-playbook ] || { mv .claude/skills/x-engagement-playbook "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/x-engagement-playbook" .claude/skills/ && echo "Installed .claude/skills/x-engagement-playbook"
On Windows, or any OS with Node 20+
npx mcprush@latest skill add zot24/x-engagement-playbook

Windows PowerShell says 'running scripts is disabled on this system'? Run Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or type npx.cmd instead of npx (codex.cmd, gemini.cmd, grok.cmd likewise). PowerShell 7 needs neither. Writes to .claude/skills/x-engagement-playbook/ in the current project. For every project instead, run mkdir -p ~/.claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/x-engagement-playbook/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/x-engagement-playbook" ] && { [ ! -e ~/.claude/skills/x-engagement-playbook ] || { mv ~/.claude/skills/x-engagement-playbook "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/x-engagement-playbook" ~/.claude/skills/ && echo "Installed ~/.claude/skills/x-engagement-playbook" (macOS, Linux) — or add --global to the npx line. The curl line replaces .claude/skills/x-engagement-playbook/ only after the download succeeds, so files left there by another skill of the same name, or by an older release, do not mix in. A copy already there is moved aside, not deleted, and the line prints where. It appears as x-engagement in Gemini CLI, Codex, Copilot and Grok (its own name); Claude Code lists it by the folder name, x-engagement-playbook.

Which clients pick it up on their own

A skill is a folder of text. Most of these read a skills folder and pick it up without being told; the rest take the same folder another way — an upload in the app, a parameter on an API call — and then choose it by its description just the same.

Claude Code.claude/skills/
Claude DesktopCustomize › Skills
ChatGPTSkills › Create › Upload
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok Build.grok/skills/
Microsoft CopilotSkills › Upload a skill
PerplexityComputer › Skills › Upload a skill
DeepSeek Harness.dsh/skills/
Zed.agents/skills/
Devin Desktop.devin/skills/
Windsurf (legacy).windsurf/skills/
OpenAI Agents SDKInstructions or sandbox Skills
HTTP / APIa request parameter
This release
Versionnot versioned
Publishedno release date on file
PriceFree
Referencezot24/x-engagement-playbook

Versions

Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

Pinning

Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.

Reviews

—no reviews yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Sign in to review it

A review is tied to an account so it can be answered, edited and taken down by the person who wrote it.

Sign in
Who can post

Anybody with an account, one review each. It carries the version that was current when you wrote it, and the publisher may reply once.

Who wrote it

ZO
zot24

Publishes on mcprush.

0 servers listed2 skills listednot claimed
Profile
Publisher
Servers0
Claim this skill