agentleFS
Sign inStart free
VorElzeVorElze/hermes-office-skills/skills/meta-threads-oauth-lifecycle/SKILL.md

meta-threads-oauth-lifecycle

Skill0 starsChanged 18 days agoMITView on GitHub

Use when configuring Meta Threads OAuth and token refresh.

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. Distinctive:

    Use whenever a task involves the Threads Graph API/OAuth (connect account, fix permission errors, refresh/rotate tokens, debug …

    line 20
  2. Very specific:

    DELETE post → cek me/threads kosong).

    line 37
  3. Very specific:

    Delete post perlu threads_delete.

    line 61

≈ “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

Meta / Threads API — OAuth Lifecycle & Secure Handoff

Kelas kerja: menghubungkan kantor ke API Meta (khususnya Threads) untuk publishing otomatis. Skill ini khusus OAuth app + token API.

When to Use

Use whenever a task involves the Threads Graph API/OAuth (connect account, fix permission errors, refresh/rotate tokens, debug publish/delete failures).

Urutan kerja yang terbukti (Threads API)

  1. Buat app dengan use case Threads API.
  2. Permissions & features: klik Add pada threads_content_publish dan threads_delete (kalau butuh rollback) sampai status Ready for testing. Status dashboard ≠ izin di token.
  3. Settings → Basic → isi dan simpan Redirect Callback URL sebelum OAuth flow.
  4. App Secret (Settings → Basic → Show) diserahkan ke server via endpoint gated, TIDAK PERNAH lewat chat.
  5. OAuth authorize → Approve → server tukar code ke short-lived, lalu th_exchange_token untuk long-lived 60 hari.
  6. Refresh otomatis: GET /refresh_access_token?grant_type=th_refresh_token&access_token=<token> — token harus ≥24 jam, jadi cron guard harus skip bila lebih muda.
  7. Verifikasi izin nyata dengan tes publish (create container → publish → DELETE post → cek me/threads kosong).

Pola handoff kredensial aman

  • Endpoint gated di Apache conf terpisah, bukan vhost utama. Untuk vhost dengan ProxyPass / catch-all, kecualikan route via scoped <Location> ProxyPass !.
  • Gate acak 32-char di .gate (640 root:www-data); pakai query ?k= karena browser form tidak bisa mengirim Authorization header.
  • PHP form POST simpan rahasia atomik (file 600), tidak pernah mengembalikan nilainya. Callback terpisah menukar code dan menampilkan hanya akun/scope/ expiry, bukan token.
  • Setelah selesai: disable conf, hapus endpoint/gate/secret, verifikasi tak ada secret tersisa dan probe publik tidak lagi mencapai endpoint.

Pitfalls terbukti

  1. User Token Generator tidak memberi izin custom; scopes yang ditambah di app perlu alur OAuth eksplisit.
  2. Panjang token bukan bukti scopes. Bukti = API nyata (mis. DELETE success).
  3. debug_token hostnya graph.facebook.com, bukan graph.threads.com.
  4. PHP Apache bisa tidak punya curl extension: cek sebelum callback; bila hilang, pasang paket PHP curl yang cocok dan reload Apache.
  5. Refresh GET-only; POST menghasilkan error 33.
  6. Token <24 jam tidak dapat refresh (error 452/4279019).
  7. Delete post perlu threads_delete; error code 10 berarti scope tidak ada pada token aktual.
  8. hermes cron create --script menerima basename relatif ke profile scripts, bukan path absolut.

Batasan platform

  • Post maks 500 karakter; container 24 jam; 250 post/hari; edit tidak tersedia. Koreksi post = DELETE + repost (perlu threads_delete).
  • Long-lived token 60 hari; tanpa refresh tepat waktu token expired dan harus OAuth ulang. Pasang cron refresh sebelum mengandalkan token produksi.

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