agentleFS
Sign inStart free
eddmanneddmann/jeeves/skills/twitter/SKILL.md

twitter

Skill2 starsChanged 9 months agoMITView on GitHub

Fetch X/Twitter timeline and bookmarks. Use when the user asks about their Twitter feed, "what's on my timeline", "my bookmarks", "what have I bookmarked", or wants raw tweet data.

15 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use nano-banana-pro.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 12 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If fetches return errors or redirect to login, cookies have expired.

    line 54

“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “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

Twitter/X Skill

Fetch timeline and bookmarks from X using Playwright with session cookies.

Cookies stored at workspace/skills/twitter/twitter-cookies.json (auth_token + ct0).

Setup

Twitter doesn't offer a usable OAuth flow, so auth uses session cookies exported from the user's browser.

Walk the user through these steps:

  1. Log into x.com in a browser
  2. Open DevTools (F12) → Application tab → Cookies → https://x.com
  3. Copy the values of auth_token and ct0

Then save them:

cat > skills/twitter/twitter-cookies.json <<'EOF'
{
  "auth_token": "PASTE_AUTH_TOKEN_HERE",
  "ct0": "PASTE_CT0_HERE"
}
EOF
chmod 600 skills/twitter/twitter-cookies.json

Fetch Timeline

cd /app && uv run workspace/skills/twitter/scripts/fetch_timeline.py        # default 50 tweets
cd /app && uv run workspace/skills/twitter/scripts/fetch_timeline.py 100    # more tweets

Returns JSON: {count, tweets: [{author, handle, timestamp, content, links}]}

Fetch Bookmarks

cd /app && uv run workspace/skills/twitter/scripts/fetch_bookmarks.py       # default 30
cd /app && uv run workspace/skills/twitter/scripts/fetch_bookmarks.py 50    # more

Returns JSON: {count, bookmarks: [{author, handle, timestamp, content, links}]}

Cookie Refresh

If fetches return errors or redirect to login, cookies have expired. Re-run the Setup steps to export fresh values.

Quick Reference

  • "What's on my Twitter?" → fetch_timeline.py
  • "My bookmarks" → fetch_bookmarks.py

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.

Check your setup, free