agentleFS
nikhonitnikhonit/social-media-api-skills/skills/twitter-api/SKILL.md

twitter-api

Skill3 starsChanged 3 months agoMIT-0View on GitHub

X (Twitter) data toolkit via ScraperSocial — video transcripts, AI summaries, post stats, profiles, user tweets, list tweets and keyword search.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read public X (formerly Twitter) data as clean JSON.

    line 34
  2. Distinctive:

    You need to post, reply or DM: Read-only.

    line 50
  3. Very specific:

    Every script also accepts --limit, --cursor, --fields, --format and --fresh.

    line 79
  4. Distinctive:

    Every response uses the same envelope:

    line 87

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

X (Twitter) API skill

Read public X (formerly Twitter) data as clean JSON. This Twitter API skill returns post statistics, profiles, a user's tweets, the tweets in a list, keyword search — and, less commonly available, transcripts and AI summaries of the video attached to a post.

X's own API pricing pushed a lot of people off the platform's data entirely. These endpoints start at 1 credit, which makes ordinary reads viable again.

This skill wraps 7 live X (Twitter) endpoints from the ScraperSocial API. Public data only, returned as clean JSON.

When to use this skill

  • A user pastes a post URL and wants its engagement numbers or the video transcribed.
  • You are tracking what an account posts, or monitoring a keyword.
  • You are researching a profile's reach and posting pattern.
  • You need the tweets from a curated list as a monitoring feed.

Do not use this skill when

  • You need real-time streaming. These are point queries, not a firehose.
  • You need to post, reply or DM. Read-only.
  • You need protected accounts or deleted posts. Public data only.
  • A link appears in passing with no question attached — get_transcript.js at 7 credits and get_summary.js at 9 are not calls to make speculatively.

Setup

export SCRAPERSOCIAL_KEY=sk_live_...   # https://scrapersocial.com/app/keys

Signing up at scrapersocial.com/signup includes 100 free credits, no card required.

Permissions and scope

These scripts do exactly three things and nothing else: read one environment variable (SCRAPERSOCIAL_KEY), send HTTPS requests to https://api.scrapersocial.com (the host is a constant in the code, not configurable), and print JSON. They run as node scripts/<name>.js with no other shell use, no file writes and no persistence. call_endpoint.js accepts only the 7 documented /v1/twitter/ paths in the table below and refuses anything else before a request is made.

Scripts

ScriptWhat it doesInputCredits
get_list_tweets.jsList X/Twitter list tweets.url1 credit per tweet
get_profile.jsFollower counts, bio and profile metadata for an account on X.handle5 credits
search.jsKeyword and advanced-search over public posts on X.query2 credits per result
get_stats.jsViews, likes, reposts and replies for a single post on X.url1 credit
get_summary.jsShort AI summary of a video posted on X, built on its transcript.url9 credits
get_transcript.jsFull transcript of a video attached to a post on X.url7 credits
get_tweets.jsLatest posts from an account on X with per-post metrics.handle1 credit per tweet
call_endpoint.jsCall any /v1/twitter/ endpoint directlypath + paramsvaries

Every script also accepts --limit, --cursor, --fields, --format and --fresh. --limit is clamped to 50: above that the API returns an async job instead of data.

Example

node skills/twitter-api/scripts/search.js "llm benchmarks"

Every response uses the same envelope:

{ "data": {}, "meta": { "count": 20, "next_cursor": "..." }, "request_id": "a18e4ef88ad4b00b" }

meta appears on paginated endpoints only. Keep request_id — support traces calls with it.

Endpoints

EndpointInputReturnsCreditsPaginated
/v1/twitter/list-tweetsurltweet1 credit per tweetyes
/v1/twitter/profilehandlelookup5 creditsno
/v1/twitter/searchqueryresult2 credits per resultyes
/v1/twitter/statsurltweet1 creditno
/v1/twitter/summaryurlvideo9 creditsno
/v1/twitter/transcripturlvideo7 creditsno
/v1/twitter/tweetshandletweet1 credit per tweetyes

Costs shown per item for paginated endpoints, per call otherwise. Failed calls are not charged.

FAQ

How do I get tweet stats as JSON?

get_stats.js with the post URL, 1 credit. get_profile.js returns an account for 5.

Can I transcribe the video in a post?

Yes. get_transcript.js with the post URL returns the spoken content for 7 credits; get_summary.js returns an AI summary for 9.

How do I monitor a keyword on X?

search.js with a query, 2 credits per result. For a curated feed, get_list_tweets.js returns the tweets in a list at 1 credit each.

How does this compare to X's official API?

X's own API is the sanctioned route and the only one that supports posting. This is a read-only alternative with per-call pricing and no monthly tier commitment.

Is this an official X API?

No. ScraperSocial is independent and not affiliated with X Corp. It returns publicly available data only.

Links

Disclaimer

ScraperSocial is an independent product and is not affiliated with, endorsed by, or sponsored by any platform named in this repository. All product names, logos and brands are property of their respective owners. These skills return only publicly available data.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.