xurl CLI for X (Twitter) API: posts, replies, DMs, media and raw v2 calls (short listing)
⚠️ AUTHORIZED USE ONLY — Drive the official xurl CLI from your agent — shortcut commands for posting, replying, reading, searching, DMs, media uploads and followers, plus raw mode for any v2 endpoint
- What
- ⚠️ AUTHORIZED USE ONLY — Drive the official xurl CLI from your agent — shortcut commands for posting, replying, reading, searching, DMs, media uploads and followers, plus raw mode for any v2 endpoint
- Cost
- Free
- Needs
- the xurl CLI installed (brew xdevplatform/tap/xurl or npm @xdevplatform/xurl) plus X developer API credentials — the skill is a workflow the agent follows, not software to install
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
⚠️ AUTHORIZED USE ONLY — this skill can perform real actions on your X account; never use it without the account owner's explicit approval for each action. Selected by Skill Harbor — short listing (the repo states no license, so no content is reproduced): @openclaw's skill for driving the `xurl` CLI (X's official CLI) from an agent. Shortcut commands return JSON; raw mode covers any v2 endpoint. Covers auth (tokens live in `~/.xurl` — check with `xurl auth status` rather than reading the file, pass secrets through the prompt not inline so they stay out of shell history, note `--verbose` prints auth headers into tool output), common shortcuts (post, reply, quote, delete, read, search, whoami, user lookup, timeline, mentions, like/unlike, repost/unrepost, bookmark, follow/unfollow, block/mute, DM send and list), media (upload image/video, poll `media status`, post with `--media-id`), auth and app management, per-request app/auth overrides, raw API calls (keep complex payloads in temp files), and output/error semantics (non-zero exit on API/auth/network errors, 401/403 auth-scope guidance, 429 backoff). Honest caveats: the agent can publish real posts, replies and DMs under your X account — review every send yourself; X API access tiers and their costs apply (check your X developer plan); install via brew (`xdevplatform/tap/xurl`) or npm (`@xdevplatform/xurl`) is a prerequisite; license not stated by the source repo — short listing with a link only, nothing copied. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: the xurl CLI installed (brew xdevplatform/tap/xurl or npm @xdevplatform/xurl) plus X developer API credentials — the skill is a workflow the agent follows, not software to install Install "xurl CLI for X (Twitter) API: posts, replies, DMs, media and raw v2 calls" for me. It gives my agent @openclaw's playbook for driving the xurl CLI: auth conventions (never read ~/.xurl directly, pass secrets via the prompt), shortcut commands for posting, replying, reading, searching, DMs, media uploads and follower management, raw v2 mode, and output/error semantics. IMPORTANT: the repo states no license — fetch from the link only, and reproduce nothing beyond the link. Repository: https://github.com/openclaw/openclaw/blob/main/skills/xurl/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). Review the files for suspicious commands or credential handling; stop on any red flag and never assume the repository is safe. Tell me if anything looks off. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "xurl". 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. install xurl and authenticate — tokens live in ~/.xurl; check your X developer API plan/costs; review every post or DM before sending). 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. 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.