x-tweet-fetcher
Low RiskFetch tweets from X/Twitter without authentication
Editorial assessment
Where x-tweet-fetcher fits
x-tweet-fetcher is currently positioned as a social media skill for engineering teams running repository, CI, and issue workflows. Based on the available metadata, the core job to be done is straightforward: fetch tweets from x/twitter without authentication.
The current description adds a practical clue about how the skill behaves in the field: supports regular tweets, long tweets, quoted tweets, and full x articles using fxtwitter api. zero dependencies, zero configuration. Combined with a CLI-based install path, this makes x-tweet-fetcher easier to evaluate than pages that only list a name and external link.
x-tweet-fetcher can usually be trialed quickly, as long as the source and permissions still get reviewed. The current record points to Network requests as part of the operational surface, which should be reviewed during security and workflow testing.
Best fit
engineering teams running repository, CI, and issue workflows
Install surface
git clone https://github.com/openclaw/x-tweet-fetcher.git
Source signal
Public source link available
Workflow tags
Social media, Openclaw, and Cli
Adoption posture
Install command documented
Risk review
Can usually be trialed quickly, as long as the source and permissions still get reviewed
Install Command
git clone https://github.com/openclaw/x-tweet-fetcher.gitBest-fit workflows
X tweet fetcher is best evaluated in social media environments where fetch tweets from x/twitter without authentication
Shortlist it when your team is actively comparing options for social media, openclaw, and cli workflows
Use a disposable workspace for the first pass so you can confirm the install flow, repository quality, and downstream permissions before broader adoption
About
Supports regular tweets, long tweets, quoted tweets, and full X Articles using FxTwitter API. Zero dependencies, zero configuration.
Rollout checklist
Review the source repository at https://github.com/openclaw/x-tweet-fetcher and confirm the README, maintenance activity, and install notes are still current.
Run `git clone https://github.com/openclaw/x-tweet-fetcher.git` in a disposable environment first so you can confirm package resolution, dependencies, and rollback steps.
Verify whether network requests matches your security expectations and least-privilege model.
Map x-tweet-fetcher against the rest of your stack in social media, openclaw, and cli workflows so the team knows whether it is a standalone tool or a supporting utility.
FAQ
What does x-tweet-fetcher help with?
x-tweet-fetcher is positioned as a social media skill. Based on the current summary and tags, it is most relevant for engineering teams running repository, CI, and issue workflows, especially when the workflow requires fetch tweets from x/twitter without authentication.
How should I evaluate x-tweet-fetcher before using it in production?
Start by running git clone https://github.com/openclaw/x-tweet-fetcher.git in a disposable environment, then review the source repository, permission surface, and any workflow-specific dependencies before wider rollout.
Why does this page include editorial guidance instead of only the upstream docs?
ClawList is trying to make each skill page more useful than a bare directory listing. That means surfacing practical signals like the install surface, source link, permissions, workflow fit, and rollout considerations in one place.
Who is the best first user for x-tweet-fetcher?
The best first evaluator is usually the operator or engineer already responsible for social media workflows, because they can verify whether x-tweet-fetcher matches the current stack, risk tolerance, and maintenance expectations.
Security & Permissions
This skill requires the following permissions:
- Network requests
Recommendation: Use the principle of least privilege and regularly review skill behavior.