X API: post tweets and threads, read timelines, search, analytics
Programmatic X (Twitter) interaction — post tweets and threads, timelines, search, media upload, rate-limit handling
- What
- Programmatic X (Twitter) interaction — post tweets and threads, timelines, search, media upload, rate-limit handling
- Cost
- Free
- Needs
- an X developer account with API credentials (free tier covers read-only use — posting and threads require a paid API tier); keep credentials in environment variables or the secure vault, never hardcoded
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @affaan-m's X (Twitter) API integration guide for agents: the auth patterns (OAuth 2.0 bearer token for read-heavy work, OAuth 1.0a user context for posting, DMs and any write flow), the core operations with ready-to-adapt code (post a tweet, post a thread, read timelines, search tweets, get users, upload media then post), rate-limit handling (read the headers at runtime, back off, never hardcode limits), error handling per status code, and a security section — never hardcode tokens, env vars only, never commit `.env`, rotate on exposure, prefer read-only tokens. Includes a content-engine integration loop: pull recent originals for voice matching, draft, validate length and thread structure, post only after approval, track engagement. By @affaan-m, listed here with credit to its creator. Honest caveats: needs an X developer account and credentials; the free tier covers read-only use — posting and threads require a paid API tier; the integration examples reference companion skills (`brand-voice`, `content-engine`, `crosspost`) not included here; MIT-licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: an X developer account with API credentials (free tier covers read-only use — posting and threads require a paid API tier); keep credentials in environment variables or the secure vault, never hardcoded Install "X API: post tweets and threads, read timelines, search, analytics" for me. Give my agent @affaan-m's X API integration: OAuth 2.0 bearer for read-heavy work and OAuth 1.0a user context for writes, core operations (post tweet, post thread, read timelines, search, get users, upload media then post), runtime rate-limit handling and per-status error handling, plus the security rules (never hardcode tokens, never commit .env, rotate on exposure, read-only tokens when write access is not needed). Repository: https://github.com/affaan-m/ecc/blob/main/.agents/skills/x-api/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "x-api". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. create my X developer app and store the keys in the secure vault — never paste them in chat). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.