twitterapi-io-cli

Fetch and paginate Twitter/X data using twitterapi.io. Use when you need to fetch one tweet, fetch a user profile, get recent tweets for a user, fetch replie...

MIT-0 · Free to use, modify, and redistribute. No attribution required.
0 · 30 · 0 current installs · 0 all-time installs
byRobin | Liquidium@ropl-btc
MIT-0
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description match the delivered artifacts: instructions focused on reading Twitter/X via twitterapi.io, references point to official docs, and the small compatibility wrapper delegates to the CLI package. There are no unrelated credentials or binaries requested.
Instruction Scope
SKILL.md stays within read-only scope and explicitly warns against adding write flows. It recommends installing the CLI from a GitHub repo and documents config storage at ~/.config/twitterapi-io/config.json; storing an API key locally is expected but worth reviewing before use.
Install Mechanism
The registry contains no automated install spec (instruction-only). SKILL.md recommends pipx install from a GitHub repo (git+https://github.com/ropl-btc/twitterapi-io-cli.git). Installing code directly from a GitHub repo is a common but higher-risk choice than using a vetted package registry; verify the upstream repository before running pipx.
Credentials
Only an API key (TWITTERAPI_IO_KEY or via the CLI auth command) and a local config file are referenced — both are appropriate for a read-only CLI wrapper. No unrelated secrets or system paths are requested.
Persistence & Privilege
Skill does not request always:true, system privileges, or modifications to other skills. It is user-invocable and can be called autonomously per platform defaults — appropriate for this functionality.
Assessment
This skill appears to be what it says: a read-only helper for twitterapi.io. Before installing or running the recommended pipx install: (1) inspect the upstream GitHub repo (https://github.com/ropl-btc/twitterapi-io-cli) to ensure it matches expectations and has no surprising code, (2) prefer exporting the API key as an environment variable (TWITTERAPI_IO_KEY) rather than placing long-lived secrets in files if you have concerns, and (3) note the skill will store config under ~/.config/twitterapi-io/config.json — review that file's permissions and contents. If you need guaranteed provenance, consider installing from a vetted package source or reviewing the package source code before use.

Like a lobster shell, security has layers — review code before you run it.

Current versionv0.1.0
Download zip
latestvk97ekcadcx23mywajfzqhttqb582zqf6

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

SKILL.md

twitterapi-io

Use the installed twitterapi-io CLI for read-only twitterapi.io access.

This skill exists to make common twitterapi.io reads simple and low-noise instead of rebuilding custom API calls each time.

Quick rules

  • Use this skill only for reads.
  • Do not improvise posting/like/reply/delete flows.
  • Prefer compact JSON output by default.
  • Use --raw only when you actually need full API objects.
  • Prefer the official docs links in references/links.md when validating endpoint behavior.

Installation preference

Prefer an installed CLI over hardcoded script paths.

Preferred install:

pipx install git+https://github.com/ropl-btc/twitterapi-io-cli.git

Fallback inside a repo checkout:

pip install .

After install, use:

twitterapi-io

Commands

Show built-in help

twitterapi-io help

Authenticate once

twitterapi-io auth --api-key YOUR_KEY

You can also use env:

export TWITTERAPI_IO_KEY='YOUR_KEY'

Fetch one tweet

twitterapi-io tweet --url 'https://x.com/jack/status/20'

or:

twitterapi-io tweet --id 20

Fetch one user

twitterapi-io user --username OpenAI

Fetch recent tweets for a user

twitterapi-io user-tweets --username OpenAI --limit 10

Include replies:

twitterapi-io user-tweets --username OpenAI --limit 10 --include-replies

Fetch replies to a tweet

twitterapi-io replies --url 'https://x.com/jack/status/20' --limit 20

Optional unix-time filters:

twitterapi-io replies --id 20 --since-time 1741219200 --until-time 1741305600 --limit 20

Fetch quote tweets

twitterapi-io quotes --id 20 --limit 20

Fetch thread context

twitterapi-io thread-context --id 20 --limit 40

Fetch mentions for a user

twitterapi-io mentions --username OpenAI --limit 20

Advanced search

twitterapi-io search --query 'AI agents -filter:replies' --from-user OpenAI --within-time 24h --max-tweets 50

Use Top results when needed:

twitterapi-io search --query 'AI agents' --queryType Top --max-pages 2

Use explicit unix-time operators when needed:

twitterapi-io search --query '$BTC' --since-time 1741219200 --until-time 1741305600 --max-tweets 50

Workflow

  1. Read references/links.md if you need the underlying official twitterapi.io docs links.
  2. Ensure the twitterapi-io CLI is installed.
  3. Ensure the API key exists via auth or env.
  4. Use tweet, user, user-tweets, replies, quotes, thread-context, mentions, or search as needed.
  5. Keep reads narrow and intentional.

Expected outputs

The CLI returns JSON. Parse it instead of scraping human text.

Default output is compact and low-noise. Use --raw when full endpoint payloads are actually needed.

Files

  • Package repo: https://github.com/ropl-btc/twitterapi-io-cli
  • Compatibility wrapper: scripts/twitterapi_io.py
  • Official docs links: references/links.md
  • Config storage: ~/.config/twitterapi-io/config.json

When to stop and ask

Stop and ask before:

  • adding write/posting capabilities
  • adding login-cookie flows
  • adding broad/high-cost scraping defaults
  • changing how API key storage works

Files

3 total
Select a file
Select a file to preview.

Comments

Loading comments…