X Impact Checker
Analyze X posts for viral potential based on the open-source recommendation algorithm (19-element scoring system).
Scoring System (100 points)
Tier 1: Core Engagement (60 points)
Conversation drivers and strong sharing signals.
| Factor |
Max |
Scoring Guide |
| Reply Potential |
22 |
22: Direct question/debatable claim, 12: Invites response, 4: Statement only |
| Retweet Potential |
16 |
16: Actionable insight/surprising fact, 8: Interesting but niche, 0: No share value |
| Favorite Potential |
12 |
12: Emotionally resonant/personal story, 6: Useful reference, 0: Low appeal |
| Quote Potential |
10 |
10: Strong opinion inviting commentary, 5: Thought-provoking, 0: No quote value |
Tier 2: Extended Engagement (25 points)
Media interactions and sustained attention metrics.
| Factor |
Max |
Scoring Guide |
| Dwell Time |
6 |
6: Long-form/detailed content, 3: Medium depth, 0: Skimmable |
| Continuous Dwell Time |
4 |
4: Thread/story arc requiring sustained attention, 2: Medium complexity, 0: Quick read |
| Click Potential |
5 |
5: Compelling link with clear CTA, 3: Link with context, 1: Bare URL, 0: No link |
| Photo Expand Potential |
4 |
4: Multiple images/visual storytelling, 2: Single image reference, 0: No visual content |
| Video View Potential |
3 |
3: Long-form video with hook (>5s), 2: Short clip, 0: No video |
| Quoted Click Potential |
3 |
3: Bold claim inviting verification, 2: Interesting claim, 0: Self-contained |
Tier 3: Relationship Building (15 points)
Author discovery and long-term value signals.
| Factor |
Max |
Scoring Guide |
| Profile Click |
5 |
5: Creates author curiosity, 3: Shows expertise, 0: Generic voice |
| Follow Potential |
4 |
4: Demonstrates ongoing value, 2: Shows potential, 0: One-off content |
| Share Potential |
2 |
2: General sharing value, 1: Limited appeal, 0: No value |
| Share via DM |
2 |
2: Personal/relatable "send to friend" content, 1: Somewhat relatable, 0: Generic |
| Share via Copy Link |
2 |
2: Reference/bookmark worthy, 1: Useful but not evergreen, 0: Ephemeral |
Penalties (subtract from total)
| Risk |
Range |
Trigger |
| Not Interested |
-5 to -15 |
Clickbait, irrelevant content |
| Mute Risk |
-5 to -15 |
Repetitive, annoying patterns |
| Block Risk |
-10 to -25 |
Offensive, aggressive tone |
| Report Risk |
-15 to -30 |
Policy violations, spam signals |
Grades
| Score |
Grade |
| 90-100 |
S (Exceptional) |
| 75-89 |
A (Strong) |
| 60-74 |
B (Good) |
| 45-59 |
C (Average) |
| 30-44 |
D (Below average) |
| 0-29 |
F (Low potential) |
Output Format
Use emojis throughout the report for better visual clarity and engagement.
Progress Tracking
Use TodoWrite tool to show analysis progress with these tasks:
Analyzing post content (in_progress → completed)
- activeForm: "Analyzing post content"
- content: "Analyze post content"
Calculating scores across all elements (in_progress → completed)
- activeForm: "Calculating scores across all elements"
- content: "Calculate scores across all elements"
Generating top 5 priority improvements (in_progress → completed)
- activeForm: "Generating top 5 priority improvements"
- content: "Generate top 5 priority improvements"
Creating optimized version (in_progress → completed)
- activeForm: "Creating optimized version"
- content: "Create optimized version"
Mark each task as completed immediately after finishing that step.
Report Structure
Score: 🎯 XX/100 (Grade: X)
Breakdown Table:
| Category | Factor | Score | Max | Assessment |
|----------|--------|-------|-----|------------|
| **💬 Core Engagement** | | | 60 | |
| | 💭 Reply Potential | X/22 | 22 | [reason] |
| | 🔄 Retweet Potential | X/16 | 16 | [reason] |
| | ❤️ Favorite Potential | X/12 | 12 | [reason] |
| | 💬 Quote Potential | X/10 | 10 | [reason] |
| **⏱️ Extended Engagement** | | | 25 | |
| | 👀 Dwell Time | X/6 | 6 | [reason] |
| | ⏳ Continuous Dwell Time | X/4 | 4 | [reason] |
| | 🔗 Click Potential | X/5 | 5 | [reason] |
| | 🖼️ Photo Expand | X/4 | 4 | [reason] |
| | 🎥 Video View | X/3 | 3 | [reason] |
| | 🔍 Quoted Click | X/3 | 3 | [reason] |
| **🤝 Relationship Building** | | | 15 | |
| | 👤 Profile Click | X/5 | 5 | [reason] |
| | ➕ Follow Potential | X/4 | 4 | [reason] |
| | 📤 Share Potential | X/2 | 2 | [reason] |
| | 💌 Share via DM | X/2 | 2 | [reason] |
| | 📋 Share via Link | X/2 | 2 | [reason] |
| **⚠️ Negative Signals** | | | | |
| | 😐 Not Interested Risk | -X | 0 to -15 | [reason] |
| | 🔇 Mute Risk | -X | 0 to -15 | [reason] |
| | 🚫 Block Risk | -X | 0 to -25 | [reason] |
| | 🚨 Report Risk | -X | 0 to -30 | [reason] |
| **🏆 TOTAL** | | **XX/100** | | **Grade: X** |
📈 Top 5 Priority Improvements: Specific, actionable suggestions across different categories
- Use emojis like ✅, 💡, 🎯 to highlight key improvements
✨ Optimized Version: Rewritten post with improvements applied (in original language)
Detailed Scoring Criteria & Improvement Strategies
Tier 1: Core Engagement
Reply Potential (22 points)
Evaluation Criteria:
- Direct questions: "What do you think?", "How would you solve this?"
- Debatable claims: "X is better than Y"
- Opinion invitations: "Agree or disagree?"
- Open-ended prompts
- Controversial but thoughtful statements
Improvement Strategies:
- ❌ Bad: "Just shipped a new feature."
- ⚠️ Better: "Just shipped a new feature. Thoughts?"
- ✅ Best: "Should features ship fast but buggy, or slow but stable? We chose speed—was it the right call?"
Retweet Potential (16 points)
Evaluation Criteria:
- Actionable insights: "Here's how..."
- Surprising facts: "X% of developers don't know..."
- Numbered lists: "3 ways to...", "10 lessons from..."
- Data-driven content
- Shareable takeaways
- Universal truths
Improvement Strategies:
- ❌ Bad: "I learned something today."
- ⚠️ Better: "I learned React hooks can reduce bundle size by 30%."
- ✅ Best: "🧵 3 React patterns that cut my bundle size by 30%:\n\n1. Lazy loading hooks\n2. Code splitting by route\n3. Tree-shaking unused exports"
Favorite Potential (12 points)
Evaluation Criteria:
- Emotional resonance: joy, frustration, triumph
- Personal stories: "When I was..."
- Relatable moments: "We've all been there..."
- Inspirational content
- Vulnerability and authenticity
- Useful references worth saving
Improvement Strategies:
- ❌ Bad: "Debugging is hard."
- ⚠️ Better: "Spent 3 hours debugging a typo."
- ✅ Best: "Spent 3 hours debugging a production issue. The fix? A missing semicolon I added during 'quick cleanup' at 2am. Never touching working code past midnight again 😅"
Quote Potential (10 points)
Evaluation Criteria:
- Strong opinions: "X is dead", "Y is overrated"
- Challenges conventional wisdom
- Invites commentary and counter-arguments
- Takes clear stance on controversial topics
- Thought-provoking perspectives
Improvement Strategies:
- ❌ Bad: "TypeScript is useful."
- ⚠️ Better: "TypeScript prevents bugs."
- ✅ Best: "TypeScript's biggest value isn't catching bugs—it's documentation. The type errors are just a bonus. Fight me."
Tier 2: Extended Engagement
Dwell Time (6 points)
Evaluation Criteria:
- Long-form content requiring reading time
- Detailed explanations with examples
- Technical depth
- Multi-paragraph structure
- Educational content
Improvement Strategies:
- Add concrete examples: "For instance, when building X..."
- Include numbers and data: "This reduced latency from 200ms to 50ms"
- Structure with clear sections
Continuous Dwell Time (4 points)
Evaluation Criteria:
- Thread indicators: "🧵", "Thread:", "1/", numbered series
- Narrative structure: beginning, middle, end
- Complexity requiring re-reading
- Educational depth with layers
- Story arcs that unfold
- "And then..." structures
Difference from Dwell Time:
- Dwell Time: Initial reading duration (how long to read once)
- Continuous Dwell Time: Sustained attention (re-reading, contemplation, multi-part consumption)
Improvement Strategies:
- ❌ Bad: "Here's how I built X. [long explanation]"
- ⚠️ Better: "🧵 How I built X in 30 days"
- ✅ Best: "🧵 How I went from idea to $10k MRR in 30 days (1/8)\n\nDay 1-7: Validation\nDays 8-14: MVP\nDays 15-30: Launch\n\nHere's what nobody tells you..."
Click Potential (5 points)
Evaluation Criteria:
- Link presence and context quality
- Call-to-action strength: "Read more", "Discover", "Learn how"
- Preview/teaser effectiveness
- Curiosity gap creation: "The results were shocking..."
- Clear value proposition
Improvement Strategies:
- ❌ Bad: "https://example.com/article"
- ⚠️ Better: "Read more here: [link]"
- ✅ Best: "How I 10xed revenue in 3 months (full breakdown with screenshots): [link]"
Photo Expand Potential (4 points)
Evaluation Criteria:
- Image markers: [photo], [image], "pic.twitter.com"
- Visual language: "see", "look", "view", "check this out"
- Emojis suggesting visuals: 📸, 🎨, 👀, 📷, 🖼️
- Before/after comparisons
- Multiple image storytelling: "Swipe through..."
- Visual evidence: "Here's proof 👇"
Improvement Strategies:
- ❌ Bad: "My dashboard looks great now."
- ⚠️ Better: "Check out my new dashboard design."
- ✅ Best: "Before/after of my analytics dashboard redesign 👇\n\nWent from cluttered mess to clean insights in 2 days.\n\n[visual indicators suggest images present]"
Video View Potential (3 points)
Evaluation Criteria:
- Video markers: [video], "▶️", "watch", "tutorial", "demo"
- Duration hints: "2-min", "quick demo", "full walkthrough"
- Content preview describing what viewers will see
- Timestamp highlights: "Skip to 1:30 for..."
- Hook/teaser: "Wait for the ending..."
VQV Eligibility (Conditional):
Full scoring (3 points) applies only if video appears to be >5 seconds (long-form).
Inferred from: "full tutorial", "in-depth", "complete guide" vs "quick clip", "snippet"
Improvement Strategies:
- ❌ Bad: "Made a video."
- ⚠️ Better: "Watch my new tutorial ▶️"
- ✅ Best: "Full 8-minute breakdown: How to build this UI in Next.js ▶️\n\n0:00 Setup\n2:15 Components\n5:30 Animations\n\nBest part at 6:45"
Quoted Click Potential (3 points)
Evaluation Criteria:
- Provocative but incomplete statements
- Statistics or claims needing verification
- Hot takes inviting source investigation: "80% of startups fail because..."
- "Wait, what?" factor creating curiosity
- Source credibility questions
- Bold claims: "This changes everything"
Improvement Strategies:
- ❌ Bad: "Read this interesting study about developer productivity."
- ⚠️ Better: "New study shows remote developers are 20% more productive."
- ✅ Best: "New Stanford study: Remote developers write 35% more code but with 50% fewer bugs.\n\nThis destroys the 'office collaboration' myth."
Tier 3: Relationship Building
Profile Click (5 points)
Evaluation Criteria:
- Creates author curiosity: "Who is this person?"
- Demonstrates expertise: "I built X at Y company"
- Shows unique perspective or background
- Credibility signals: credentials, experience
- Intriguing bio-worthy content
Improvement Strategies:
- ❌ Bad: "I think React is good."
- ⚠️ Better: "After 5 years with React, I think it's good."
- ✅ Best: "After architecting React apps for Airbnb, Netflix, and 50+ startups, here's what I wish I knew on day one:"
Follow Potential (4 points)
Evaluation Criteria:
- Demonstrates ongoing value: "I ship weekly tutorials on..."
- Shows consistent expertise
- Promises future content: "More on this tomorrow"
- Establishes content cadence
- Creates expectation of quality
Improvement Strategies:
- ❌ Bad: "Here's a React tip."
- ⚠️ Better: "Here's a React tip. I post these daily."
- ✅ Best: "React tip #47: [insight]\n\nI break down advanced React patterns every Monday. Following along? Tomorrow's is about suspense boundaries."
Share Potential (2 points)
Evaluation Criteria:
- General sharing value to broader audience
- Universal relevance
- Broad appeal across communities
Improvement Strategies:
- Make universally relevant, not niche-specific
- Focus on common problems everyone faces
Share via DM (2 points)
Evaluation Criteria:
- Personal relevance: "Tag someone who...", "Send this to..."
- Inside jokes or shared experiences
- Emotional resonance for 1-on-1 sharing: "This is so you 😂"
- Relatable scenarios: "We all have that friend..."
- "You need to see this" quality
Improvement Strategies:
- ❌ Bad: "Debugging is frustrating."
- ⚠️ Better: "Debugging production issues is stressful."
- ✅ Best: "Tag your developer friend who 'just quickly fixes' production on Friday at 5pm and breaks everything 😂"
Share via Copy Link (2 points)
Evaluation Criteria:
- Reference value: guides, lists, frameworks, cheatsheets
- Evergreen quality (not time-sensitive)
- Professional sharing context (Slack, email, bookmarks)
- "Save this" or "Bookmark" language
- Educational/tutorial content
- Resource library worthy
Improvement Strategies:
- ❌ Bad: "Here are some Git commands I use."
- ⚠️ Better: "Useful Git commands for daily work."
- ✅ Best: "📌 Bookmark this: 15 Git commands that saved me 100+ hours this year\n\n[Well-structured list with examples]\n\nPrint this and keep it next to your monitor."
Score Normalization
The algorithm applies normalization to balance positive and negative signals:
Final Score = Base Score (0-100) + Penalties (-75 to 0)
Normalized Score = max(0, min(100, Final Score))
Penalty Capping:
- Total penalties ≤ -20: Applied at full weight
- Total penalties > -20: Gradual dampening begins
- Total penalties > -75: Hard cap at -75 to prevent over-penalization
This prevents a single negative signal from completely dominating the score while maintaining their importance in the algorithm.
Text Analysis Limitations
This skill performs heuristic text-based analysis, not ML prediction.
What This Skill Cannot Detect
Missing Metadata:
- Actual media presence (photos, videos)
- Real video duration or quality
- Actual click-through rates
- True engagement metrics
- Author reputation/follower count
- Tweet timestamps or virality history
Cannot Access:
- Phoenix ML model predictions
- User interaction history
- Network graph relationships
- Real-time engagement signals
What This Skill Infers From
Text-Based Heuristics:
- Language patterns and structure
- Content formatting (threads, lists, etc.)
- Emotional tone and style
- Visual indicators (emojis, markdown)
- Call-to-action strength
- Question vs. statement structure
Scoring Approach:
- Conservative: Unknown elements get baseline scores
- Pattern-Based: Detects language cues (e.g., 📸 for photos, 🧵 for threads)
- Optimization-Focused: Best used for pre-publishing content improvement
Best Use Case
Pre-publishing optimization to maximize engagement potential, not post-hoc analytics or prediction of actual engagement numbers.
Language Handling
Detect input language. Respond in same language. Keep optimized version in original language.
Bilingual Display for Category and Factor Names
When input is in Japanese:
- Display Category and Factor names as:
日本語訳(English Original)
- Examples:
- Category:
コアエンゲージメント(Core Engagement)
- Factor:
返信潜在力(Reply Potential)
- Factor:
リツイート潜在力(Retweet Potential)
When input is in English:
- Display Category and Factor names in English only
- Examples:
- Category:
Core Engagement
- Factor:
Reply Potential
Japanese translations with emojis for reference:
- 💬 Core Engagement → コアエンゲージメント
- ⏱️ Extended Engagement → 拡張エンゲージメント
- 🤝 Relationship Building → 関係構築
- ⚠️ Negative Signals → ネガティブシグナル
- 💭 Reply Potential → 返信潜在力
- 🔄 Retweet Potential → リツイート潜在力
- ❤️ Favorite Potential → いいね潜在力
- 💬 Quote Potential → 引用潜在力
- 👀 Dwell Time → 滞在時間
- ⏳ Continuous Dwell Time → 継続滞在時間
- 🔗 Click Potential → クリック潜在力
- 🖼️ Photo Expand → 写真展開潜在力
- 🎥 Video View → 動画視聴潜在力
- 🔍 Quoted Click → 引用クリック潜在力
- 👤 Profile Click → プロフィールクリック
- ➕ Follow Potential → フォロー潜在力
- 📤 Share Potential → 共有潜在力
- 💌 Share via DM → DM経由共有
- 📋 Share via Link → リンクコピー共有
- 😐 Not Interested Risk → 興味なしリスク
- 🔇 Mute Risk → ミュートリスク
- 🚫 Block Risk → ブロックリスク
- 🚨 Report Risk → 報告リスク
Algorithm Reference
See references/algorithm-weights.md for complete weight details from X's open-source algorithm (19-element system).
1---2name: x-impact-checker3description: Analyze X (Twitter) posts for viral potential using the actual recommendation algorithm. Use when user wants to: (1) Check if a post will go viral, (2) Optimize a tweet for engagement, (3) Improve post performance. Triggers: "Check if this will go viral", "Make this post buzz", "Will this tweet perform well?", "Optimize my tweet", "How can I make this viral?", "バズるかチェックして", "Xでバズる投稿にして", "伸びるかチェックして", "この投稿を伸ばして", "投稿を改善して", "ツイートを最適化して"4---5
6# X Impact Checker
7
8Analyze X posts for viral potential based on the open-source recommendation algorithm (19-element scoring system).
9
10## Scoring System (100 points)
11
12### Tier 1: Core Engagement (60 points)
13
14Conversation drivers and strong sharing signals.
15
16| Factor | Max | Scoring Guide |
17|--------|-----|---------------|
18| Reply Potential | 22 | 22: Direct question/debatable claim, 12: Invites response, 4: Statement only |
19| Retweet Potential | 16 | 16: Actionable insight/surprising fact, 8: Interesting but niche, 0: No share value |
20| Favorite Potential | 12 | 12: Emotionally resonant/personal story, 6: Useful reference, 0: Low appeal |
21| Quote Potential | 10 | 10: Strong opinion inviting commentary, 5: Thought-provoking, 0: No quote value |
22
23### Tier 2: Extended Engagement (25 points)
24
25Media interactions and sustained attention metrics.
26
27| Factor | Max | Scoring Guide |
28|--------|-----|---------------|
29| Dwell Time | 6 | 6: Long-form/detailed content, 3: Medium depth, 0: Skimmable |
30| Continuous Dwell Time | 4 | 4: Thread/story arc requiring sustained attention, 2: Medium complexity, 0: Quick read |
31| Click Potential | 5 | 5: Compelling link with clear CTA, 3: Link with context, 1: Bare URL, 0: No link |
32| Photo Expand Potential | 4 | 4: Multiple images/visual storytelling, 2: Single image reference, 0: No visual content |
33| Video View Potential | 3 | 3: Long-form video with hook (>5s), 2: Short clip, 0: No video |
34| Quoted Click Potential | 3 | 3: Bold claim inviting verification, 2: Interesting claim, 0: Self-contained |
35
36### Tier 3: Relationship Building (15 points)
37
38Author discovery and long-term value signals.
39
40| Factor | Max | Scoring Guide |
41|--------|-----|---------------|
42| Profile Click | 5 | 5: Creates author curiosity, 3: Shows expertise, 0: Generic voice |
43| Follow Potential | 4 | 4: Demonstrates ongoing value, 2: Shows potential, 0: One-off content |
44| Share Potential | 2 | 2: General sharing value, 1: Limited appeal, 0: No value |
45| Share via DM | 2 | 2: Personal/relatable "send to friend" content, 1: Somewhat relatable, 0: Generic |
46| Share via Copy Link | 2 | 2: Reference/bookmark worthy, 1: Useful but not evergreen, 0: Ephemeral |
47
48### Penalties (subtract from total)
49
50| Risk | Range | Trigger |
51|------|-------|---------|
52| Not Interested | -5 to -15 | Clickbait, irrelevant content |
53| Mute Risk | -5 to -15 | Repetitive, annoying patterns |
54| Block Risk | -10 to -25 | Offensive, aggressive tone |
55| Report Risk | -15 to -30 | Policy violations, spam signals |
56
57## Grades
58
59| Score | Grade |
60|-------|-------|
61| 90-100 | S (Exceptional) |
62| 75-89 | A (Strong) |
63| 60-74 | B (Good) |
64| 45-59 | C (Average) |
65| 30-44 | D (Below average) |
66| 0-29 | F (Low potential) |
67
68## Output Format
69
70Use emojis throughout the report for better visual clarity and engagement.
71
72### Progress Tracking
73
74Use TodoWrite tool to show analysis progress with these tasks:
75
761. **Analyzing post content** (in_progress → completed)
77 - activeForm: "Analyzing post content"
78 - content: "Analyze post content"
79
802. **Calculating scores across all elements** (in_progress → completed)
81 - activeForm: "Calculating scores across all elements"
82 - content: "Calculate scores across all elements"
83
843. **Generating top 5 priority improvements** (in_progress → completed)
85 - activeForm: "Generating top 5 priority improvements"
86 - content: "Generate top 5 priority improvements"
87
884. **Creating optimized version** (in_progress → completed)
89 - activeForm: "Creating optimized version"
90 - content: "Create optimized version"
91
92Mark each task as completed immediately after finishing that step.
93
94### Report Structure
95
961. **Score**: `🎯 XX/100 (Grade: X)`
97
982. **Breakdown Table**:
99```
100| Category | Factor | Score | Max | Assessment |
101|----------|--------|-------|-----|------------|
102| **💬 Core Engagement** | | | 60 | |
103| | 💭 Reply Potential | X/22 | 22 | [reason] |
104| | 🔄 Retweet Potential | X/16 | 16 | [reason] |
105| | ❤️ Favorite Potential | X/12 | 12 | [reason] |
106| | 💬 Quote Potential | X/10 | 10 | [reason] |
107| **⏱️ Extended Engagement** | | | 25 | |
108| | 👀 Dwell Time | X/6 | 6 | [reason] |
109| | ⏳ Continuous Dwell Time | X/4 | 4 | [reason] |
110| | 🔗 Click Potential | X/5 | 5 | [reason] |
111| | 🖼️ Photo Expand | X/4 | 4 | [reason] |
112| | 🎥 Video View | X/3 | 3 | [reason] |
113| | 🔍 Quoted Click | X/3 | 3 | [reason] |
114| **🤝 Relationship Building** | | | 15 | |
115| | 👤 Profile Click | X/5 | 5 | [reason] |
116| | ➕ Follow Potential | X/4 | 4 | [reason] |
117| | 📤 Share Potential | X/2 | 2 | [reason] |
118| | 💌 Share via DM | X/2 | 2 | [reason] |
119| | 📋 Share via Link | X/2 | 2 | [reason] |
120| **⚠️ Negative Signals** | | | | |
121| | 😐 Not Interested Risk | -X | 0 to -15 | [reason] |
122| | 🔇 Mute Risk | -X | 0 to -15 | [reason] |
123| | 🚫 Block Risk | -X | 0 to -25 | [reason] |
124| | 🚨 Report Risk | -X | 0 to -30 | [reason] |
125| **🏆 TOTAL** | | **XX/100** | | **Grade: X** |
126```
127
1283. **📈 Top 5 Priority Improvements**: Specific, actionable suggestions across different categories
129 - Use emojis like ✅, 💡, 🎯 to highlight key improvements
130
1314. **✨ Optimized Version**: Rewritten post with improvements applied (in original language)
132
133## Detailed Scoring Criteria & Improvement Strategies
134
135### Tier 1: Core Engagement
136
137#### Reply Potential (22 points)
138
139**Evaluation Criteria:**
140- Direct questions: "What do you think?", "How would you solve this?"
141- Debatable claims: "X is better than Y"
142- Opinion invitations: "Agree or disagree?"
143- Open-ended prompts
144- Controversial but thoughtful statements
145
146**Improvement Strategies:**
147- ❌ Bad: "Just shipped a new feature."
148- ⚠️ Better: "Just shipped a new feature. Thoughts?"
149- ✅ Best: "Should features ship fast but buggy, or slow but stable? We chose speed—was it the right call?"
150
151#### Retweet Potential (16 points)
152
153**Evaluation Criteria:**
154- Actionable insights: "Here's how..."
155- Surprising facts: "X% of developers don't know..."
156- Numbered lists: "3 ways to...", "10 lessons from..."
157- Data-driven content
158- Shareable takeaways
159- Universal truths
160
161**Improvement Strategies:**
162- ❌ Bad: "I learned something today."
163- ⚠️ Better: "I learned React hooks can reduce bundle size by 30%."
164- ✅ Best: "🧵 3 React patterns that cut my bundle size by 30%:\n\n1. Lazy loading hooks\n2. Code splitting by route\n3. Tree-shaking unused exports"
165
166#### Favorite Potential (12 points)
167
168**Evaluation Criteria:**
169- Emotional resonance: joy, frustration, triumph
170- Personal stories: "When I was..."
171- Relatable moments: "We've all been there..."
172- Inspirational content
173- Vulnerability and authenticity
174- Useful references worth saving
175
176**Improvement Strategies:**
177- ❌ Bad: "Debugging is hard."
178- ⚠️ Better: "Spent 3 hours debugging a typo."
179- ✅ Best: "Spent 3 hours debugging a production issue. The fix? A missing semicolon I added during 'quick cleanup' at 2am. Never touching working code past midnight again 😅"
180
181#### Quote Potential (10 points)
182
183**Evaluation Criteria:**
184- Strong opinions: "X is dead", "Y is overrated"
185- Challenges conventional wisdom
186- Invites commentary and counter-arguments
187- Takes clear stance on controversial topics
188- Thought-provoking perspectives
189
190**Improvement Strategies:**
191- ❌ Bad: "TypeScript is useful."
192- ⚠️ Better: "TypeScript prevents bugs."
193- ✅ Best: "TypeScript's biggest value isn't catching bugs—it's documentation. The type errors are just a bonus. Fight me."
194
195---
196
197### Tier 2: Extended Engagement
198
199#### Dwell Time (6 points)
200
201**Evaluation Criteria:**
202- Long-form content requiring reading time
203- Detailed explanations with examples
204- Technical depth
205- Multi-paragraph structure
206- Educational content
207
208**Improvement Strategies:**
209- Add concrete examples: "For instance, when building X..."
210- Include numbers and data: "This reduced latency from 200ms to 50ms"
211- Structure with clear sections
212
213#### Continuous Dwell Time (4 points)
214
215**Evaluation Criteria:**
216- Thread indicators: "🧵", "Thread:", "1/", numbered series
217- Narrative structure: beginning, middle, end
218- Complexity requiring re-reading
219- Educational depth with layers
220- Story arcs that unfold
221- "And then..." structures
222
223**Difference from Dwell Time:**
224- **Dwell Time**: Initial reading duration (how long to read once)
225- **Continuous Dwell Time**: Sustained attention (re-reading, contemplation, multi-part consumption)
226
227**Improvement Strategies:**
228- ❌ Bad: "Here's how I built X. [long explanation]"
229- ⚠️ Better: "🧵 How I built X in 30 days"
230- ✅ Best: "🧵 How I went from idea to $10k MRR in 30 days (1/8)\n\nDay 1-7: Validation\nDays 8-14: MVP\nDays 15-30: Launch\n\nHere's what nobody tells you..."
231
232#### Click Potential (5 points)
233
234**Evaluation Criteria:**
235- Link presence and context quality
236- Call-to-action strength: "Read more", "Discover", "Learn how"
237- Preview/teaser effectiveness
238- Curiosity gap creation: "The results were shocking..."
239- Clear value proposition
240
241**Improvement Strategies:**
242- ❌ Bad: "https://example.com/article"
243- ⚠️ Better: "Read more here: [link]"
244- ✅ Best: "How I 10xed revenue in 3 months (full breakdown with screenshots): [link]"
245
246#### Photo Expand Potential (4 points)
247
248**Evaluation Criteria:**
249- Image markers: [photo], [image], "pic.twitter.com"
250- Visual language: "see", "look", "view", "check this out"
251- Emojis suggesting visuals: 📸, 🎨, 👀, 📷, 🖼️
252- Before/after comparisons
253- Multiple image storytelling: "Swipe through..."
254- Visual evidence: "Here's proof 👇"
255
256**Improvement Strategies:**
257- ❌ Bad: "My dashboard looks great now."
258- ⚠️ Better: "Check out my new dashboard design."
259- ✅ Best: "Before/after of my analytics dashboard redesign 👇\n\nWent from cluttered mess to clean insights in 2 days.\n\n[visual indicators suggest images present]"
260
261#### Video View Potential (3 points)
262
263**Evaluation Criteria:**
264- Video markers: [video], "▶️", "watch", "tutorial", "demo"
265- Duration hints: "2-min", "quick demo", "full walkthrough"
266- Content preview describing what viewers will see
267- Timestamp highlights: "Skip to 1:30 for..."
268- Hook/teaser: "Wait for the ending..."
269
270**VQV Eligibility (Conditional):**
271Full scoring (3 points) applies only if video appears to be >5 seconds (long-form).
272Inferred from: "full tutorial", "in-depth", "complete guide" vs "quick clip", "snippet"
273
274**Improvement Strategies:**
275- ❌ Bad: "Made a video."
276- ⚠️ Better: "Watch my new tutorial ▶️"
277- ✅ Best: "Full 8-minute breakdown: How to build this UI in Next.js ▶️\n\n0:00 Setup\n2:15 Components\n5:30 Animations\n\nBest part at 6:45"
278
279#### Quoted Click Potential (3 points)
280
281**Evaluation Criteria:**
282- Provocative but incomplete statements
283- Statistics or claims needing verification
284- Hot takes inviting source investigation: "80% of startups fail because..."
285- "Wait, what?" factor creating curiosity
286- Source credibility questions
287- Bold claims: "This changes everything"
288
289**Improvement Strategies:**
290- ❌ Bad: "Read this interesting study about developer productivity."
291- ⚠️ Better: "New study shows remote developers are 20% more productive."
292- ✅ Best: "New Stanford study: Remote developers write 35% more code but with 50% fewer bugs.\n\nThis destroys the 'office collaboration' myth."
293
294---
295
296### Tier 3: Relationship Building
297
298#### Profile Click (5 points)
299
300**Evaluation Criteria:**
301- Creates author curiosity: "Who is this person?"
302- Demonstrates expertise: "I built X at Y company"
303- Shows unique perspective or background
304- Credibility signals: credentials, experience
305- Intriguing bio-worthy content
306
307**Improvement Strategies:**
308- ❌ Bad: "I think React is good."
309- ⚠️ Better: "After 5 years with React, I think it's good."
310- ✅ Best: "After architecting React apps for Airbnb, Netflix, and 50+ startups, here's what I wish I knew on day one:"
311
312#### Follow Potential (4 points)
313
314**Evaluation Criteria:**
315- Demonstrates ongoing value: "I ship weekly tutorials on..."
316- Shows consistent expertise
317- Promises future content: "More on this tomorrow"
318- Establishes content cadence
319- Creates expectation of quality
320
321**Improvement Strategies:**
322- ❌ Bad: "Here's a React tip."
323- ⚠️ Better: "Here's a React tip. I post these daily."
324- ✅ Best: "React tip #47: [insight]\n\nI break down advanced React patterns every Monday. Following along? Tomorrow's is about suspense boundaries."
325
326#### Share Potential (2 points)
327
328**Evaluation Criteria:**
329- General sharing value to broader audience
330- Universal relevance
331- Broad appeal across communities
332
333**Improvement Strategies:**
334- Make universally relevant, not niche-specific
335- Focus on common problems everyone faces
336
337#### Share via DM (2 points)
338
339**Evaluation Criteria:**
340- Personal relevance: "Tag someone who...", "Send this to..."
341- Inside jokes or shared experiences
342- Emotional resonance for 1-on-1 sharing: "This is so you 😂"
343- Relatable scenarios: "We all have that friend..."
344- "You need to see this" quality
345
346**Improvement Strategies:**
347- ❌ Bad: "Debugging is frustrating."
348- ⚠️ Better: "Debugging production issues is stressful."
349- ✅ Best: "Tag your developer friend who 'just quickly fixes' production on Friday at 5pm and breaks everything 😂"
350
351#### Share via Copy Link (2 points)
352
353**Evaluation Criteria:**
354- Reference value: guides, lists, frameworks, cheatsheets
355- Evergreen quality (not time-sensitive)
356- Professional sharing context (Slack, email, bookmarks)
357- "Save this" or "Bookmark" language
358- Educational/tutorial content
359- Resource library worthy
360
361**Improvement Strategies:**
362- ❌ Bad: "Here are some Git commands I use."
363- ⚠️ Better: "Useful Git commands for daily work."
364- ✅ Best: "📌 Bookmark this: 15 Git commands that saved me 100+ hours this year\n\n[Well-structured list with examples]\n\nPrint this and keep it next to your monitor."
365
366---
367
368## Score Normalization
369
370The algorithm applies normalization to balance positive and negative signals:
371
372```
373Final Score = Base Score (0-100) + Penalties (-75 to 0)
374Normalized Score = max(0, min(100, Final Score))
375```
376
377**Penalty Capping:**
378- Total penalties ≤ -20: Applied at full weight
379- Total penalties > -20: Gradual dampening begins
380- Total penalties > -75: Hard cap at -75 to prevent over-penalization
381
382This prevents a single negative signal from completely dominating the score while maintaining their importance in the algorithm.
383
384---
385
386## Text Analysis Limitations
387
388This skill performs heuristic text-based analysis, not ML prediction.
389
390### What This Skill Cannot Detect
391
392**Missing Metadata:**
393- Actual media presence (photos, videos)
394- Real video duration or quality
395- Actual click-through rates
396- True engagement metrics
397- Author reputation/follower count
398- Tweet timestamps or virality history
399
400**Cannot Access:**
401- Phoenix ML model predictions
402- User interaction history
403- Network graph relationships
404- Real-time engagement signals
405
406### What This Skill Infers From
407
408**Text-Based Heuristics:**
409- Language patterns and structure
410- Content formatting (threads, lists, etc.)
411- Emotional tone and style
412- Visual indicators (emojis, markdown)
413- Call-to-action strength
414- Question vs. statement structure
415
416**Scoring Approach:**
417- **Conservative**: Unknown elements get baseline scores
418- **Pattern-Based**: Detects language cues (e.g., 📸 for photos, 🧵 for threads)
419- **Optimization-Focused**: Best used for pre-publishing content improvement
420
421### Best Use Case
422
423Pre-publishing optimization to maximize engagement potential, not post-hoc analytics or prediction of actual engagement numbers.
424
425---
426
427## Language Handling
428
429Detect input language. Respond in same language. Keep optimized version in original language.
430
431### Bilingual Display for Category and Factor Names
432
433**When input is in Japanese:**
434- Display Category and Factor names as: `日本語訳(English Original)`
435- Examples:
436 - Category: `コアエンゲージメント(Core Engagement)`
437 - Factor: `返信潜在力(Reply Potential)`
438 - Factor: `リツイート潜在力(Retweet Potential)`
439
440**When input is in English:**
441- Display Category and Factor names in English only
442- Examples:
443 - Category: `Core Engagement`
444 - Factor: `Reply Potential`
445
446**Japanese translations with emojis for reference:**
447- 💬 Core Engagement → コアエンゲージメント
448- ⏱️ Extended Engagement → 拡張エンゲージメント
449- 🤝 Relationship Building → 関係構築
450- ⚠️ Negative Signals → ネガティブシグナル
451- 💭 Reply Potential → 返信潜在力
452- 🔄 Retweet Potential → リツイート潜在力
453- ❤️ Favorite Potential → いいね潜在力
454- 💬 Quote Potential → 引用潜在力
455- 👀 Dwell Time → 滞在時間
456- ⏳ Continuous Dwell Time → 継続滞在時間
457- 🔗 Click Potential → クリック潜在力
458- 🖼️ Photo Expand → 写真展開潜在力
459- 🎥 Video View → 動画視聴潜在力
460- 🔍 Quoted Click → 引用クリック潜在力
461- 👤 Profile Click → プロフィールクリック
462- ➕ Follow Potential → フォロー潜在力
463- 📤 Share Potential → 共有潜在力
464- 💌 Share via DM → DM経由共有
465- 📋 Share via Link → リンクコピー共有
466- 😐 Not Interested Risk → 興味なしリスク
467- 🔇 Mute Risk → ミュートリスク
468- 🚫 Block Risk → ブロックリスク
469- 🚨 Report Risk → 報告リスク
470
471## Algorithm Reference
472
473See [references/algorithm-weights.md](references/algorithm-weights.md) for complete weight details from X's open-source algorithm (19-element system).