opentweet-x-poster_skill

Overview

This skill automates Build-in-Public posts for founders, indie hackers, and developers using the OpenTweet API. It drafts release announcements, milestone posts, progress threads, technical TILs, feature launches, and bug acknowledgments with an emphasis on specificity and transparency. GitHub integration is optional to enrich posts with real release, commit, and repo metrics.

How this skill works

Before creating or scheduling any post the skill verifies the OpenTweet connection and remaining daily post quota via GET /api/v1/me. It then drafts concise X posts or threads using provided input or fetched GitHub data (releases, commits, stars) and formats them to meet tone and hashtag rules. Finally it creates posts via POST /api/v1/posts and can schedule or publish when the user confirms and subscription limits allow.

When to use it

• Announce a new release or tag on GitHub
• Share weekly progress or a daily build log
• Celebrate user, MRR, or star milestones
• Explain a technical fix or TIL to the community
• Acknowledge and explain a bug and its fix
• Schedule a week of Build-in-Public content in advance

Best practices

• Always call GET /api/v1/me first to check authentication and remaining_posts_today
• Provide concrete numbers, dates, and short context — do not use vague language
• If available, supply GITHUB_TOKEN to auto-populate release notes and metrics
• Keep each tweet under 280 characters; remember each thread tweet consumes quota
• Use at most two hashtags (one should be #BuildInPublic) and limit emojis to one or two sparingly
• Never publish without explicit user confirmation unless autonomous posting was explicitly granted

Example use cases

• Convert a GitHub release into a 1–3 tweet announcement highlighting top changes and impact
• Post a daily build log listing what shipped, what’s next, and current blockers
• Create a 4–6 tweet weekly recap thread summarizing features, bugs fixed, and metric shifts
• Celebrate reaching 1,000 users or $1K MRR with a short milestone post that includes timeframe and lesson
• Acknowledge a login bug: what broke, how it was found, fix applied, and mitigation steps