X Twitter Api
CheckedProvides API guidance and assistance for agent workflows.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add tato418/x-twitter-api --skill x-twitter-api -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
tato418
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Only contacts known or declared hosts: github.com.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
Hosts contacted
github.comsource hostNo obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned tato418/x-twitter-api at fd03049641.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- fd03049641
- Manifest
- SKILL.md
- Scanned
- 60 files, 3,179 lines
About this skill
What it does
This skill provides access to the X (formerly Twitter) API v2, allowing an AI agent to interact with the platform using your authenticated developer credentials (OAuth 1.0a). It enables actions such as retrieving user data, searching for posts, creating tweets, managing likes and reposts, following/unfollowing users, and more. All commands are executed through a central entry point: node x.js <command> [flags].
When to use it
- Automating social media tasks like liking or reposting content.
- Gathering data about your own X account (profile metrics, verification status).
- Searching for specific posts based on keywords or hashtags.
- Managing user relationships – following, unfollowing, muting, blocking.
- Retrieving and managing bookmarks.
Key capabilities
- User Data Retrieval: Access profile information and metrics.
- Search Functionality: Search tweets within the last 7 days or the full archive.
- Post Management: Create new posts (tweets, replies, quote tweets), and delete your own posts.
- Engagement Actions: Like, unlike, repost, and unrepost tweets.
- Social Interactions: Follow, unfollow, list followers/following accounts.
- Feed Access: Retrieve your home timeline and mentions.
- Bookmark Management: Bookmark, unbookmark, and list bookmarks.
- Moderation Tools: Mute, unmute, block users, and hide replies.
- Analytics: Identify users who liked or reposted a specific tweet.
Example prompts
- "Find the latest tweets mentioning 'AI'."
- "Repost the most recent tweet from user @example."
- "Retrieve my profile information."
- "Like this post with ID 1234567890."
Tips & gotchas
- Setup Required: Before first use, you must run
npm installand thennpm run buildwithin the skill's directory. - Authentication: This skill uses your authenticated developer credentials; ensure these are properly configured.
- Command Documentation: Each command has its own documentation file (e.g.,
@docs/me.md) for detailed flag options and behavior. Refer to these files for specific instructions. - Working Directory: Avoid changing the skill's working directory when using it; use relative paths or the
--prefixoption instead.