Grow a Twitter/X account with SuperX. Use when someone asks for a weekly growth recap or account analytics, wants to find leads or buyers on X, needs draft posts or threads written and scheduled, wants replies drafted or reply history reviewed, asks who engages with them most, wants inspiration from high-performing posts, or wants X Articles written and published. Also covers contact lists, signal agents (automated lead finders), Engage feeds, tagging, media attachments, AI cover images, and the Context settings (profile, interests, rules, reply settings, favorite creators, style guide, products) that steer SuperX writing. Everything runs through the superx CLI or the SuperX API; nothing is posted without a person saying so.
Ask your Agent
Use this Skill: https://skilld.dev/gh/superx-so/superx-agent/superx
This session only. Nothing lands on disk.
≈112 tokens on demand. Your agent reads this file only when SKILL.md points to it.
The ranked winners, the shape they share, and what to write more of.
SINCE=$(date -u -v-30d +"%Y-%m-%dT00:00:00Z" 2>/dev/null || date -u -d "30 days ago" +"%Y-%m-%dT00:00:00Z")
superx posts:list --type posts --sort likes --since "$SINCE" --limit 25
superx posts:analytics --since "$SINCE"MCP: get_post_analytics -> get_account_overview
Stops at: the pattern read in chat. Reads only, no AI credits.
Source: SKILL.md on GitHub
The SuperX skill enables an AI agent to manage X (Twitter) account growth through a specialized CLI tool provided by a recognized vendor (superx-so). The skill uses shell commands to perform analytics, scheduling, and content generation. The primary security risk is Indirect Prompt Injection, as the agent is instructed to process and respond to untrusted data from X (such as post replies and keyword feeds) without explicit instructions for data sanitization or boundary management. The skill also requires the installation of an external CLI tool and the management of API credentials.
1 alert: gptAnomaly
Risk: MEDIUM · 1 issue
Signed by skilld at 2276277. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.
Last checked against GitHub 2 weeks ago.
{
"openclaw": {
"emoji": "🚀",
"requires": {
"bins": [
"superx"
],
"env": []
}
}
}