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

social-threads

Skill4 starsChanged 20 days agoMITView on GitHub

Threads API: post text or an image, read your posts and profile. Use the `social` CLI (Bun) for every threads action; every endpoint is reachable through `social api threads <path>`, so prefer this CLI over raw API calls in all cases.

  • Reads credentials

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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 threads.

    line 19
  2. Distinctive:

    No machine-readable spec: none.

    line 23
  3. Very specific:

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

    line 27

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

social threads

Threads API: post text or an image, read your posts and profile.

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

Credentials

  • THREADS_USER_ID
  • THREADS_ACCESS_TOKEN

Create an app with the Threads API use case, add yourself as a Threads Tester (accept in Threads > Settings > Account > Website permissions), authorise at https://threads.net/oauth/authorize?client_id=…&redirect_uri=…&scope=threads_basic,threads_content_publish&response_type=code, exchange the code (POST graph.threads.net/oauth/access_token; the reply carries user_id), then make it long-lived: GET graph.threads.net/access_token?grant_type=th_exchange_token&client_secret=…&access_token=… (60 days; refresh with /refresh_access_token?grant_type=th_refresh_token). https://developers.facebook.com/docs/threads/get-started/get-access-tokens-and-permissions

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

API description this wrapper is built from

No machine-readable spec: none.

Commands

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

social threads post <text>

post to Threads (500 chars), optionally with a public image URL

  --image <url>              attach an image (JPEG/PNG, 8 MB max)

social threads posts

your recent threads

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

social threads me

the Threads profile this token belongs to

Anything else: the escape hatch

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

Reach for social api threads … 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.