Menu
When the user wants to draft tweets, plan threads, post to Twitter/X, or manage their Twitter presence
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Learn from corrections, mistakes, and discoveries during conversations. When the user corrects you, when something fails unexpectedly, or when you discover a project-specific pattern worth remembering — record it as a learning so future sessions benefit automatically.
When reviewing UI/UX for quality, consistency, and polish. Use when the user says 'review the design,' 'check the UI,' 'does this look good,' 'design audit,' 'UX review,' or 'polish the frontend.' Also use after implementing any user-facing feature to catch visual and interaction issues before shipping.
Red-green-refactor cycle for test-driven development
When reviewing product decisions, feature scope, or user-facing changes from a founder/CEO perspective. Use when the user says 'does this make sense,' 'should we build this,' 'review the product,' 'is this good enough,' 'founder review,' 'product sense check,' or before any significant launch. This is the strategic taste layer — not engineering quality, but product quality.
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
When reviewing code that involves architectural decisions, new modules, data flow changes, or system design. Use when the PR introduces new services, changes API boundaries, modifies database schemas, adds new dependencies, or restructures significant portions of the codebase. Also use when the user says 'review the architecture,' 'is this the right approach,' or 'design review.'
| name | twitter-workflow |
| description | When the user wants to draft tweets, plan threads, post to Twitter/X, or manage their Twitter presence |
Ensure twitter-cli is installed and authenticated:
# Install
uv tool install twitter-cli
# Auth via browser cookies (no API key needed)
# twitter-cli auto-extracts from Chrome/Arc/Firefox/Edge/Brave
twitter-cli timeline
If auth fails, the user needs to set TWITTER_AUTH_TOKEN and TWITTER_CT0 environment variables from their browser cookies.
Before posting anything, always draft and present to the user for approval:
twitter-cli tweet <id>), then add genuine value.Present the draft clearly:
📝 Draft tweet:
---
[tweet content here]
---
Post this? (y/n)
Never post without explicit user confirmation.
# Single tweet
twitter-cli post "Your tweet content here"
# Tweet with images (up to 4)
twitter-cli post "Check out these results" --image chart.png
# Quote tweet
twitter-cli post "My take on this:" --quote-url https://x.com/user/status/123
# Reply
twitter-cli post "Great point! Here's what I'd add..." --reply-to 123456789
After posting, check engagement:
# Check your recent tweets and their metrics
twitter-cli me --yaml
# Search for mentions or relevant conversations
twitter-cli search "keyword" --tab latest
# Check replies to your tweet
twitter-cli tweet <tweet-id>
Track what works:
Use twitter-cli me --yaml output to analyze patterns and inform the next content batch.