Install any skill in seconds. Free to start, no credit card required.
Get Started Free →bankrbot/skill-twitter-agent
This skill provides a framework for creating, managing, and automating Twitter/X agents with persistent personalities and voices. It supports running multiple agents side-by-side, each with its own files and (optionally) its own X account.
Passed 17 of 20 test cases with the skill, and 9 of 20 without it.
and 7 more in the full report
9 fixed10 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
When running JS scripts via execute_cli for Twitter API tasks, which JavaScript runtime binary should be invoked, and which package version of twitter-api-v2 should be pinned?
| Checked | Without skill | With skill |
|---|---|---|
| Uses `bun` as the execution binary instead of `node`. | Missed | Passed |
| Pins `[email protected]` in the package list. | Missed | Passed |
The instructions your model reads when the skill loads.
Build and run one or more Twitter/X agents, each with a distinct personality, storyline, and post-image library.
This skill provides a framework for creating, managing, and automating Twitter/X agents with persistent personalities and voices. It supports running multiple agents side-by-side, each with its own files and (optionally) its own X account.
Every agent's X account MUST be marked as an automated account before it posts a single tweet. X requires this disclosure; skipping it is the fastest way to get suspended.
Exact path:
Direct link (while logged in as the agent account): https://x.com/settings/account/automation
This adds the "Automated by @…" label to the profile and replies. Non-negotiable — do this once per agent account.
This skill supports a single default credential set (for the primary / only agent) AND per-agent overrides (when running multiple agents with distinct X accounts).
Default credentials (used by the primary agent or any agent that does not have overrides):
X_API_KEYX_API_KEY_SECRETX_ACCESS_TOKENX_ACCESS_TOKEN_SECRETPer-agent overrides (optional; only required when a second+ agent uses a different X account):
X_API_KEY_{SLUG_UPPER}X_API_KEY_SECRET_{SLUG_UPPER}X_ACCESS_TOKEN_{SLUG_UPPER}X_ACCESS_TOKEN_SECRET_{SLUG_UPPER}test cases passed, vs 9 / 20 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.