agentleFS
isaacrowntreeisaacrowntree/claude-social-skills/skills/social-x/SKILL.md

social-x

Skill4 starsChanged 20 days agoMITView on GitHub

X (Twitter) API v2: post, reply, delete, read your timeline, upload media. Use the `social` CLI (Bun) for every x action; every endpoint is reachable through `social api x <path>`, so prefer this CLI over raw API calls in all cases.

  • Reads credentials

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check what is present with social auth status x.

    line 21
  2. Very specific:

    Every command accepts --json (raw JSON) and --jq <expr> (filter the JSON with jq).

    line 29

“Common” is measured: kept by at least 6 in 10 of the 3 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

social x

X (Twitter) API v2: post, reply, delete, read your timeline, upload media.

Run: social x <command> (installed via bun link in this repo, or bun run /path/to/claude-social-skills/src/cli.ts x …). Add --dry-run before any command to print the request instead of sending it.

Credentials

  • TWITTER_API_KEY
  • TWITTER_API_SECRET
  • TWITTER_ACCESS_TOKEN
  • TWITTER_ACCESS_TOKEN_SECRET

OAuth 1.0a user-context keys from the X developer portal.

Check what is present with social auth status x; store a value with social auth set x <KEY> <value> (OS keyring, else ~/.config/social/.env). Docs: https://docs.x.com/x-api

API description this wrapper is built from

openapi: https://api.x.com/2/openapi.json. Refresh with social specs pull x; CI fails if upstream changes.

Commands

Every command accepts --json (raw JSON) and --jq <expr> (filter the JSON with jq).

social x apis

the x API groups and how many operations each has

social x ops [filter]...

search operations: every word must appear in the id, summary, path, description or field names; best matches first

  --api <name>               only this API group (see `social x apis`)

social x describe <op>

parameters, body, scopes and response shape of one operation

  --depth <n>                how deep to expand nested fields (default 2)

social x call <op>

call any operation by id; --dry-run prints the request instead

  -p, --param <k=v>          path/query/header parameter (default [])
  -f, --field <k=v>          body field, typed (numbers, booleans, null, JSON literals) (default [])
  --raw-field <k=v>          body field, always a string (default [])
  --file <field=path>        file for a multipart part (image=./photo.jpg) or a binary body (default [])
  --output <file>            save a binary response (PDF, image, feed file) here
  --input <file>             request body from a JSON file (- for stdin)

social x post <text>

post a tweet

  --reply-to <id>            reply to a tweet id
  --media <ids...>           media ids from `x upload`

social x delete <id>

delete a tweet you posted

social x user <username>

look up a public account (bearer token is enough)

social x me

the authenticated user

social x timeline [username]

recent tweets: yours, or a given @username (bearer token is enough)

  -n, --max <n>              count (5-100) (default "10")

social x upload <file>

upload an image/video for --media (v2 media upload)

Anything else: the escape hatch

social api x <path>                       # GET, path relative to the API root
social api x <path> -q key=value          # query parameters
social api x <path> -f key=value          # JSON body field (typed: numbers, booleans, null, JSON literals); implies POST
social api x <path> --raw-field key=value # string field
social api x <path> -X DELETE
social api x <path> --input body.json     # or --input - for stdin
social api x <path> --form                # urlencoded body instead of JSON
social api x <path> --jq '.data[0].id'

Reach for social api x … before concluding something is unsupported.

Behaviour

  • Retries 502/503/504 on idempotent methods (3 attempts, 250 ms then 1 s); waits once on 429 up to 90 s.
  • Errors print HTTP <status> <method> <url> and the response body, exit code 1.
  • --dry-run prints the method, URL and body of any mutating call and sends nothing.
  • social doctor makes one cheap authenticated read per configured platform.

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.