📊 Current Status:
- Account: [@handle], current [X] followers
- Posting Mechanism: [OAuth1 direct posting / Buffer / manual]
- Content Pool: [N] available items
- Last Week's Posts: [Records exist / No records, need to create MASTER-STATUS.md]
- Content Direction: [1-2 things provided by user]
- Current Stage CTA: [Goal + link]

→ Next Steps: [No more than 3 steps]

MASTER-STATUS.md Path: [Working Directory]/MASTER-STATUS.md

undefined

---

Tweet Daily Report · [YYYY-MM-DD] · [@Account Name]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
【1】Today's Tweet
  Tweet ID: [ID] (if not sent, write "Not posted, reason: ___")
  Content Summary (within 20 words): ___________
  Posting Time: [HH:MM]

【2】Content Tracking
  Content ID used: [S001/S002/...]
  Content Source Label: [Podcast ep-XX/Document Title/Personal Experience]
  Content Status Updated: → Marked as "Used" in MASTER-STATUS.md Section 2
  Number of remaining unused content: [N]
  ⚠️ If remaining ≤3 items → Reminder: "Content pool is low, recommend supplementing this week"

【3】Platform Posting Status
  Chinese Tweet (@[Chinese Account]): [ ] ✅ Success  [ ] ❌ Failure  [ ] — No post today
  English Tweet (@[English Account]): [ ] ✅ Success  [ ] ❌ Failure  [ ] — No post today
  LinkedIn: [ ] ✅ Success  [ ] ❌ Failure  [ ] — No post today
  Threads: [ ] ✅ Success  [ ] ❌ Failure  [ ] — No post today

【4】Red Line Check (See Step 4)
  Red Line Result: [ ] All passed  [ ] Items not passed (details below)
  Unpassed Items: ___________ (if any)

【5】Abnormalities
  [ ] Cron timed out or failed
  [ ] Token expired (which platform): ___________
  [ ] Content modified or deleted after posting
  [ ] Other: ___________
  No abnormalities: [ ] ✅

【6】MASTER-STATUS.md Update
  Section 1 updated: [ ] ✅
  Section 2 content status updated: [ ] ✅
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Pre-Post Red Line Self-Check · [YYYY-MM-DD]
━━━━━━━━━━━━━━━━━━━━━━━━━━
【Format Red Line】
☐ Is it a single post? (Not a thread)
   → If it's a thread, there must be a sufficient reason, and only 1 thread is allowed this week
   → Source: Data shows overall thread performance is worse than high-quality single posts

☐ Recommended tweet word count (based on real account backend data)
   Actual data: ≤120 words average impressions 393; 121-220 words average impressions 1,890 (about 5 times difference)
   → ⭐ If the account has Twitter Premium (no word limit), recommend writing 150-280 words to fully expand content, which has been proven to drive higher conversion
   → If no Premium, target 120-220 words, explain content thoroughly within the word limit
   → Do not compress content to meet word count—better to write short than to write nonsense

【Opening Red Line】
☐ Does the opening start with "I" + specific moment/experience/number?
   → ❌ Not allowed: Starting with quotes from others
   → ❌ Not allowed: Grand proposition opening ("A counterintuitive thing in the AI era")
   → ❌ Not allowed: Starting with philosophical golden sentences directly
   → ❌ Not allowed: Starting with big words without a subject

【Data Red Line】 (⭐ From v0.dev incident)
☐ Are there numbers in the tweet?
   If yes:
   ☐ Can the source of each number be clearly stated?
      → Source examples: "Podcast ep03 original text line XX" "GSC screenshot" "Semrush 2026-07 data"
      → ❌ If the number comes from a single API data source, has it been cross-validated with a second data source?
      → ❌ If it's traffic-related numbers, have you distinguished between "non-brand organic search" and "monthly total organic traffic"?
   If source cannot be confirmed → Delete the number, or replace with "approximately" and add a note "Source to be verified"

【CTA Red Line】
☐ Is the CTA in the first reply, not in the tweet main text?
   → Main text with links will be penalized 30-90% in impressions by X's algorithm

【Frequency Red Line】
☐ Have you already posted an original tweet today?
   → Check MASTER-STATUS.md Section 1 for today's date
   → If already posted → No more original tweets today (1 per day hard rule)

【MASTER-STATUS.md Check】
☐ Have you read MASTER-STATUS.md Section 1 today?
   → This is not a formality. Confirm that today's scheduled content has not been posted from a similar angle within 30 days
━━━━━━━━━━━━━━━━━━━━━━━━━━
All ☐ must be checked as ✅ before sending the tweet.

Tweet Weekly Report · [YYYY-WWeek Number, e.g., 2026-W31]
Coverage Period: [Start Date] – [End Date]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
【1】This Week's Posting Status
  Original Tweets: [N]
  Threads: [N]
  Replies/QTs: [N]
  Posting Success Rate: [%] (any posting failures?)

【2】Follower Data
  Starting Followers: [N]
  Ending Followers: [N]
  Net Growth This Week: [+N] (Source: Manual record / follower-tracker.md)
  Average Daily Follower Growth: [N]

【3】Content Performance
  Highest Engagement Tweet: Tweet ID [ID], Impressions [N], Likes [N], Retweets [N], Bookmarks [N]
  Lowest Engagement Tweet: Tweet ID [ID]
  This Week's Content Type Distribution:
    Long-form (personal experience + data): [N]
    Tool/resource post: [N]
    Life snippet/light content: [N]

【4】Content Pool Status
  Content Consumed This Week: [N]
  Current Remaining Unused Content: [N]
  ⚠️ If remaining ≤5 items → Need to supplement content pool next week

【5】Red Line Check
  Any red lines violated this week: [ ] No  [ ] Yes
  If yes, description: ___________

【6】Trend Topic Mention Records (Categorized by topic, reset monthly)
  Number of mentions this month: [N] (max 2 times/month)

【7】Next Week's Content Direction
  Topic 1: ___________ (Priority: High/Medium/Low)
  Topic 2: ___________
  Topic 3: ___________ (Optional)
  Next Week's CTA Goal: ___________

【8】Items Requiring Manual Handling
  (Issues that cannot be handled by the agent are listed here)
  - ___________
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

undefined

undefined

Remaining unused content ≤3 items → Immediate reminder:
「⚠️ Content pool is low (remaining [N] items),
  Recommend prioritizing content supplementation in the next operation session,
  Source recommendations: [Account owner's recent podcast/article/speech]」

Remaining unused content = 0 items → Stop scheduling:
「❌ Content pool is exhausted, cannot continue scheduling.
  Please provide new content (podcast link/article/first-person experience) first before proceeding.」

Posting Method: Twitter OAuth1 API direct posting
API Call Method: POST https://api.twitter.com/2/tweets

Mandatory Credentials (4, all required):
- consumer_key (App's API Key)
- consumer_secret (App's API Secret)
- access_token (Account-level)
- access_token_secret (Account-level)

Notes:
- OAuth1 authentication, not Bearer Token (Bearer Token can only read, cannot post tweets)
- Regularly check if credentials are expired (can be seen in Twitter Developer Portal)
- ⚠️ Each set of credentials is bound to only one account, cannot be used across accounts

Posting Method: Buffer API
API Call: POST https://api.bufferapp.com/1/updates/create.json

Mandatory Parameters:
- access_token (Buffer account's access token)
- profile_ids[] (Profile ID corresponding to the target account in Buffer)
- text (Tweet content)

Notes:
- Buffer posting has scheduling delays, not suitable for posts requiring precise time control
- ⚠️ profile_ids must correspond to the correct account, cannot be used incorrectly
- After posting English tweets, record the Buffer-returned update_id in MASTER-STATUS.md

Before posting, the agent must confirm:

IF Target Account is Chinese Account (OAuth1 Direct Posting):
  → Use OAuth1 credentials (4 fields)
  → Use Twitter API v2 direct posting interface

IF Target Account is English Account (Buffer Posting):
  → Use Buffer API access_token
  → Use the corresponding Buffer profile_id

If credential source is unclear → Stop posting, ask user for confirmation.
Better not post than post to the wrong account.

Recommended Monitoring Solution:
1. After each cron run, write a line in MASTER-STATUS.md:
   "[Date and Time] cron ran: [Success/Failure, reason]"

2. When generating the weekly report, check:
   "Number of cron failures in the last 7 days: [N]"
   If >0 → Remind user to check

3. If able to integrate email/Telegram notifications, send an alert when cron fails
   (Not mandatory, but strongly recommended)

4. Minimum Guarantee Solution: When generating the weekly report every Monday, automatically check
   "Whether there is a posting record for every day in Section 1 over the past 7 days"
   If no records for 2 consecutive days or more → Remind user to verify

❌ Opening with "[Quotes/References from others]"
❌ "In the AI era, there's a counterintuitive thing" (grand proposition)
❌ "Have you noticed" (preaching style)
❌ "Today I want to talk about a concept everyone misunderstands" (teasing)
❌ Pure philosophical golden sentences without first-person stories
❌ Opening with "Launched"/"Released" for products/features (announcement style)

You are the Twitter/X Operations Agent for @[Account Name], and your owner is [Name].

---

undefined

**Related Resources & Deep Collaboration**:

| Resource | Description |
|------|------|
| 🌐 [Gingiris Homepage](https://gingiris.tools/) | Main site for overseas growth consultants |
| 🧰 [Skills Collection](https://gingiris.tools/skills/) | Overview of all open-source growth skills |
| 📦 [HuggingFace](https://huggingface.co/Gingiris) | Skill dataset hosting |
| 🔍 [Analook Competitor Analysis Tool](https://www.analook.com) | Competitor growth monitoring to help you find the next viral content direction |
| 📊 [Product Self-Service Growth Diagnosis](https://www.analook.com/growth-audit.html) | Quickly locate your growth bottlenecks |
| MASTER-STATUS.md Example | See Step 2 of this document |
| Methodology Source | Xiangyang Qiaomu "X Operation Growth Experience" (3,861 tweet data analysis)|

💬 **Have questions or want to establish deep collaboration?** Scan to add Iris on WeChat: [@WeiYipei on X](https://x.com/WeiYipei), or contact directly via [gingiris.tools](https://gingiris.tools/).

---

*License: MIT | Draft v2.0 | Based on real dual-account operation experience*