threads-post
/threads-post
Post to Threads and schedule Threads posts from OpenClaw, Hermes, Claude Code or Codex. Publishes to the user's own Threads account via the 1Social MCP server (OAuth, no API key), checks the Threads 500-character limit and image rules first, schedules up to 30 days ahead and returns a delivery receipt. Use to post or schedule on Threads, publish a post, plan Threads content, or check, edit or delete Threads posts.
- Author
- sultanlive ↗
- Repository
- 1social-skills ↗
- Licence
- MIT
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 8
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Post to Threads and schedule Threads posts from OpenClaw, Hermes, Claude Code or Codex. Publishes to the user's own Threads account via the 1Social MCP server (OAuth, no API key), checks the Threads 500-character limit and image rules first, schedules up to 30 days ahead and returns a delivery receipt. Use to post or schedule on Threads, publish a post, plan Threads content, or check, edit or delete Threads posts.
Original author description
Post to Threads and schedule Threads posts from OpenClaw, Hermes, Claude Code or Codex. Publishes to the user's own Threads account via the 1Social MCP server (OAuth, no API key), checks the Threads 500-character limit and image rules first, schedules up to 30 days ahead and returns a delivery receipt. Use to post or schedule on Threads, publish a post, plan Threads content, or check, edit or delete Threads posts.
How it works
- Setup (once)
- Workflow
- Threads rules
- Writing tips
- Posting to other networks too
- After publishing
SKILL.md preview
---
name: threads-post
description: "Post to Threads and schedule Threads posts from OpenClaw, Hermes, Claude Code or Codex. Publishes to the user's own Threads account via the 1Social MCP server (OAuth, no API key), checks the Threads 500-character limit and image rules first, schedules up to 30 days ahead and returns a delivery receipt. Use to post or schedule on Threads, publish a post, plan Threads content, or check, edit or delete Threads posts."
license: MIT
metadata:
openclaw:
emoji: "📣"
homepage: "https://1social.dev/post-to/threads?ref=skill"
hermes:
tags: ["threads", "meta-threads", "threads-scheduler", "social-media", "scheduling"]
category: social-media
---
# Threads with 1Social
1Social publishes to the user's own Threads account and reports what actually reached it.
## Setup (once)
These steps drive the 1Social MCP server. If tools such as `list_accounts` are not available, connect it first. Sign-in is OAuth in the browser; there is no API key to store. Ask the user before running these commands — the login step opens a page where they sign in to 1Social themselves.
- **OpenClaw:** `openclaw mcp set 1social '{"url":"https://mcp.1social.dev/mcp","transport":"streamable-http","auth":"oauth"}'`, then `openclaw mcp login 1social`. Check with `openclaw mcp doctor 1social --probe`.
- **Hermes:** add to `~/.hermes/config.yaml`:
```yaml
mcp_servers:
1social:
url: "https://mcp.1social.dev/mcp"
auth: oauth
```
then `hermes mcp login 1social` (on a headless host: `hermes mcp login 1social --flow device`).
- **Claude Code:** `claude mcp add --transport http 1social https://mcp.1social.dev/mcp`
- **Any other client:** https://1social.dev/mcp lists the setup for each one.
The user needs a 1Social account. New accounts start with a free trial; publishing after it needs a paid plan (https://1social.dev/pricing).
## Workflow
1. **Find the account.** Call `list_accounts`. It returns the connected channels with their ids, each network's live limits, the plan and the remaining monthly quota. If no Threads account is connected, tell the user to connect one at https://1social.dev/app — connecting needs a browser and cannot be done from chat. If `list_accounts` reports a limit that differs from this skill, trust `list_accounts`.
2. **Draft for the network.** Write the post to the rules below. A post is a list of `segments`; each segment is `{ text, mediaIds? }`.
3. **Attach media.**
- The user attached a file in chat → put it in `media`.
- You have a public https link → put it in `mediaUrls`.
- You only have a file on disk (OpenClaw, Hermes, Claude Code, Codex or another CLI agent) → call `upload_media` and follow the upload steps its description gives, then put the returned `publicUrl` in `mediaUrls`. A localhost URL never works. Before that, show the user exactly which files you will upload and wait for a yes: an upload gets a public link at once, and declining the post afterwards does not remove the file.
4. **Preview.** Call `preview_post` with the channel ids and the draft. It is free and publishes nothing. Fix every issue it reports and preview again.
5. **Confirm with the user.** Show the final text, the account it goes to, the media, and when it will go out. Publishing is public and some networks cannot take a post down, so wait for a clear yes.
6. **Publish or schedule.** Call `publish_post`. `scheduledAt: null` publishes now; a UTC ISO-8601 timestamp such as `2026-11-03T07:00:00Z` schedules it (in the future, at most 30 days ahead). Convert the user's local time to UTC yourself, and if they name a time without a timezone, ask which one. Set an `idempotencyKey` (a stable string of 8–128 characters for this draft) so a repeated call cannot publish twice.
7. **Report honestly.** The result is a per-network receipt. Report each network exactly as returned. `unknown` means 1Social genuinely could not tell whether the post went out — say so, never call it a success or a failure.
## Threads rules
- Limit: 500 characters per post.
- Multi-post chains are not available through 1Social on Threads: several segments are joined into one post. Keep the whole post under 500 characters.
- Images: PNG and JPEG both work. Very wide or very tall images (banners) are rejected for aspect ratio; square or 4:5 is safe.
- Video works.
- A published Threads post cannot be deleted through 1Social. Make sure the user is happy before publishing.
## Writing tips
- Conversational tone does better than polished copy; ending with a question invites replies.
## Posting to other networks too
The same 1Social account can publish one post to Instagram, TikTok, LinkedIn, X, Threads, Facebook Pages, YouTube Shorts and Bluesky at once: list several channel ids from `list_accounts`. preview_post checks the draft against every selected network.
## After publishing
- **Check status:** `list_posts` (give a `postId` for one post). It includes stored engagement metrics where the network reports them.
- **Change a scheduled post:** `update_post`. Only works before the post has gone out.
- **Unschedule:** `cancel_post`. Use this, not `delete_post`, for a post that has not been published.
- **Delete a published post:** `delete_post`, only after the user confirms. Report per network what actually came down: Instagram, TikTok, Threads and YouTube posts stay live and only the user can remove them.
- **A delivery failed:** `retry_delivery` retries one network and spends quota again. It is refused for permanent failures such as a revoked connection — then the user must reconnect at https://1social.dev/app.
- **A delivery is `unknown`:** ask the user to look at the network. Only when they tell you whether the post is live, call `confirm_delivery` with their answer. Never guess, and never `retry_delivery` with `force` without asking — it may publish a second copy.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · sultanlive/1social-skills | 100 | MIT |
| publora/skills | 100 | MIT |
| social-media-skills/skills | 100 | MIT |
Database snapshot: 13.11.2026 · package version 7c639136b88f (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100linkedin-post
Post to LinkedIn and schedule LinkedIn posts from OpenClaw, Hermes, Claude Code or Codex. Publishes to the user's own LinkedIn account via the 1Social MCP server (OAuth, no API key), checks the LinkedIn 3,000-character limit and formatting first, schedules up to 30 days ahead… - 100bluesky-post
Post to Bluesky and schedule Bluesky posts and threads from OpenClaw, Hermes, Claude Code or Codex. Publishes to the user's own Bluesky account via the 1Social MCP server (OAuth, no API key), checks the Bluesky 300-character limit and thread rules first, schedules up to 30 days… - 100threads
Publish text, image, video or carousel posts to your Threads (@threads) account via the official Threads API, and read your own recent posts. Use when the user wants to post to Threads, cross-post a short update / thread, attach an image or link, or review their own Threads… - 95threads-marketing
Plan, draft, audit, and publish posts and threads for Threads (Meta). Use when the user wants to write a single Threads post or a multi-post thread, remove AI tells from a draft, reverse-engineer the hook from a viral Threads post, draft a reply or quote post, or plan a week of… - 95threads-marketing
Plan, draft, audit, and publish posts and threads for Threads (Meta). Use when the user wants to write a single Threads post or a multi-post thread, remove AI tells from a draft, reverse-engineer the hook from a viral Threads post, draft a reply or quote post, or plan a week of… - 95boring-threads-publisher
Publish posts and threads to Threads (by Meta) using Boring. Use when the user says 'post to Threads', 'create a thread', 'publish thread', 'write a Threads post', 'reply on Threads', or wants to create text posts, photo/video posts, carousels, or multi-post threads on Threads.