Post to X from DeepSeek Harness

Things to ask it

• "Read the last three commits and post a short changelog thread to X."
• "Write five posts from docs/launch.md and schedule them at my best times this week."
• "Which of my posts did best last month? Write two more on that topic as drafts."
• "Add my top ten posts to the evergreen queue with a 30-day cooldown."

Tools that only read (analytics, lists) and tools that write (publish, schedule, delete) are both exposed. If you want a person to approve every post, keep dsh's approval policy on ask, or tell the agent to create drafts and review them in OpenTweet.

Prefer a skill? Use ~/.agents/skills

dsh reads the Agent Skills format. Its filesystem provider scans .dsh/skills and .agents/skills in the project, then ~/.dsh/skills and ~/.agents/skills. Put this in ~/.agents/skills/post-to-x/SKILL.md and Codex and Gemini CLI pick up the same file:

---
name: post-to-x
description: Publish or schedule posts on X (Twitter) through the OpenTweet API. Use when the user asks to tweet, post to X, or schedule a post.
---

# Post to X

Send requests to https://opentweet.io with the header
`Authorization: Bearer $OPENTWEET_API_KEY`. Never print the key.

- Publish now: POST /api/v1/posts {"text": "...", "publish_now": true}
- Schedule: POST /api/v1/posts {"text": "...", "scheduled_date": "<ISO 8601 UTC>"}
- Thread: POST /api/v1/posts {"text": "first tweet", "is_thread": true, "thread_tweets": ["second", "third"], "publish_now": true}

Rules: one idea per post, under 280 characters unless the user has X Premium,
show the text to the user before publishing unless they said "post now".

A skill calls the REST API with the agent's shell tool. The MCP entry gives typed tools and more of them. Many people run both: MCP for the tools, a short skill for voice and posting rules. More agents and folders on the agent skills page.