Twitter/X data API via fetcher.sh

Prerequisites: fetcher.sh credits — a Bearer API key (bby_live_...) from https://fetcher.sh/topup, or an x402-capable setup to pay per call in USDC; $0.002–$0.005 per call, no free tier, no refunds on upstream failures; curl or an HTTP client Install "Twitter/X data API via fetcher.sh" for me. It gives the agent @fetcher-sh's playbook for pulling Twitter/X data with one plain HTTP GET per call against https://twitter.fetcher.sh — no developer account, no app review, no OAuth: 15 endpoints covering tweet search with X's advanced operators, account search, profile lookup by @handle (plus /about), a user's tweets/replies/followers/followings, single tweet with replies and retweeters, List members and tweets, and trending topics by country — plus the MCP server setup and error semantics. Repository: https://github.com/fetcher-sh/fetcher-skills/blob/main/skills/twitter-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 "twitter-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. get a fetcher.sh API key and save it in the vault — never paste it into prompts). 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.