Write a SKILL.md That Posts to X
One File, Every Agent

curl https://opentweet.io/api/v1/me \
  -H "Authorization: Bearer ot_your_key_here"

---
name: post-to-x
description: Post, schedule, and thread on X (Twitter) through the OpenTweet REST API. Use whenever the user asks to tweet, post to X, schedule a post, or publish a thread.
version: 1.0.0
---

# Post to X with OpenTweet

Post to the user's connected X account through the OpenTweet REST API.
The base URL is https://opentweet.io. The API key lives in the
OPENTWEET_API_KEY environment variable and starts with ot_.

## Authentication

Every request needs these headers:

    Authorization: Bearer $OPENTWEET_API_KEY
    Content-Type: application/json

## Before you post

Check the connection and the remaining quota first:

    GET https://opentweet.io/api/v1/me

Confirm subscription.has_access is true and limits.remaining_posts_today
is above zero before publishing or scheduling.

## Publish now

    POST https://opentweet.io/api/v1/posts
    {"text": "Tweet text here", "publish_now": true, "platforms": ["x"]}

A successful response carries status "posted", a 24-character id, and a
url pointing at the real X post. Report that url. Never construct one.

## Schedule for later

    POST https://opentweet.io/api/v1/posts
    {"text": "Tweet text here", "scheduled_date": "2026-10-01T09:00:00Z", "platforms": ["x"]}

scheduled_date is ISO 8601 and must be in the future. A scheduled post
comes back with status "scheduled".

## Save a draft

    POST https://opentweet.io/api/v1/posts
    {"text": "Tweet text here"}

Omit both publish_now and scheduled_date. Drafts do not require an
active subscription.

## Post a thread

    POST https://opentweet.io/api/v1/posts
    {
      "text": "First tweet of the thread",
      "is_thread": true,
      "thread_tweets": ["Second tweet", "Third tweet"],
      "publish_now": true
    }

Each entry in thread_tweets is its own tweet with its own character budget.

## List recent posts

    GET https://opentweet.io/api/v1/posts?status=scheduled&limit=20

status accepts scheduled, posted, draft, or failed.

## Rules

- 280 characters per tweet, counted per tweet inside a thread.
- Never send publish_now and scheduled_date in the same request.
- Show the user the drafted text and get confirmation before publishing.
  Publishing to X cannot be undone.
- Make the real HTTP call every time. Never answer from memory and never
  invent a response value.
- A 4xx or 5xx status means the operation failed. Say so plainly. Do not
  report success and do not retry blindly.
- After scheduling, show the id from the response. It is a 24-character
  ObjectId. If you cannot show a real one, the call did not happen.
- Omitting platforms does not mean X only. It follows the user's auto
  cross-post setting. Send "platforms": ["x"] when the user said X.
- Read the results array before reporting an outcome. A post can publish
  on one network and fail on another.
- 403 means no subscription or no connected X account. 429 means a rate
  limit or a daily cap. Pro allows 60 requests per minute, 1,000 per day.
- Bulk creates cap at 50 posts per request.

export OPENTWEET_API_KEY="ot_your_key_here"

echo 'OPENTWEET_API_KEY=ot_your_key_here' >> .env
echo '.env' >> .gitignore

Tweet that the 2.1 release is out, keep it under 200 characters.

Schedule a tweet for tomorrow at 9am UTC about the new pricing page.

Turn my changelog into a three-tweet thread and save it as a draft.