threads-publish

Automate Threads post publishing with a draft-first workflow and archiving.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/zdpk/skills --skill threads-publish
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: threads-publish
Source: https://github.com/zdpk/skills/tree/main/dotfiles/skills/custom/threads/threads-publish
Command: npx skills add https://github.com/zdpk/skills --skill threads-publish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Publishing Threads posts can be time-consuming and error-prone when done manually across accounts. This Skill automates the process using browser automation while enforcing a draft-first workflow and post-publish archiving to reduce the risk of accidental publishing.

Core Features & Use Cases

  • Draft-first publishing: drafts posts automatically and only publishes after explicit user confirmation.
  • Account-aware publishing: uses per-account profiles to validate login and post content safely.
  • Archiving: automatically archives published posts for traceability.

Quick Start

Invoke the automation to publish a drafted Threads post for the specified account after confirming safety.

Frequently Asked Questions about threads-publish

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate publishing Threads posts safely without accidental submissions?

To publish Threads posts safely, this automation prepares a draft first and only publishes after you explicitly confirm, preventing accidental submissions while archiving the post afterward.

Do I need browser automation tooling to publish Threads drafts?

Yes, browser automation tooling is required. Specifically, the claude-in-chrome MCP tooling is needed to drive the draft-first Threads publishing workflow and manage the explicit confirmation step before submission.

How does account-aware automation work for scheduling Threads content?

Account-aware automation uses per-account profile data stored at accounts/{id}/profile.yaml to validate login state and ensure post content is safely managed for the specified Threads account before publishing.

What is the best way to manage multiple Threads accounts via social posting automation?

The best way to manage multiple Threads accounts is using per-account profile data files to validate login and apply a draft-first workflow, ensuring each account's posts are confirmed and archived individually.

Why does my Threads automation require explicit confirmation before publishing?

Threads automation requires explicit confirmation before publishing to reduce the risk of accidental publishing, enforcing a safe draft-first workflow where drafts are only submitted after manual user approval.