twitter-cli
01Skill Claude CodeCodex
Use twitter-cli for ALL Twitter/X operations — reading tweets, posting, replying, quoting, liking, retweeting, following, searching, user lookups. Invoke whenever user requests any Twitter interaction.
34 tagged x, measured the same way as everything else here.
Browse within: twitter 39social-media 15social 11card 9byok 6hermes-agent 6ai-design 5quote 5skills 5xquik 5公众号 5
Skill Claude CodeCodex
Use twitter-cli for ALL Twitter/X operations — reading tweets, posting, replying, quoting, liking, retweeting, following, searching, user lookups. Invoke whenever user requests any Twitter interaction.
Skill Claude CodeCodex
X/Twitter automation MCP server — 104 tools for search, posting, media upload, DMs, scheduled tweets, drafts, bookmark folders, lists, communities, topics, community notes, account settings, profile management, highlights, notifications.
Skill Claude Code
Slurp work/progress context and run topic grills — brainstorm dig-deeper angles from Brain, X, sessions, and more. Never generates tweet or video copy. Use when asked for content topics, content grill, or what to dig into from recent work.
Skill Claude CodeCodex
Use Xquik from Hermes Agent for X search, posting, replies, likes, retweets, follows, DMs, monitors, extraction jobs, draws, media, and trends.
christian-beep383/carryfeed-agent-tools
Skill Codex
Use the CarryFeed CLI to resolve public X/Twitter profiles, posts, article-style links, image, video, and GIF media for agent workflows. Use when an agent needs source-preserving public X/Twitter context, profile metadata, post text, media candidates, or download URLs without browser login flows or CarryFeed internal…
Skill Claude CodeCodex
Use and configure Kan's public read-only X/Twitter MCP server at https://x.mcp.2-38.com/mcp, backed by twitter.2-38.com. Load when an agent needs to search public X posts, inspect profiles, fetch post details, media timelines, trends, or typeahead suggestions through MCP.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: