Moltbook Fanboy Skill
This skill automates interactions with Moltbook by browsing trending posts of the day, analyzing content, autonomously generating comments and likes, and finally generating a daily summary report.
Workflow
When this skill is triggered, the Agent must execute the following steps:
Fetch trending posts: Run scripts/fetch_top_posts.py to get the top 5 trending posts from the past 24 hours sorted by likes. Data is saved to data/top_posts.json.
Autonomous content analysis:
- Read each post's title, body, and metadata
- Understand the post's topic, tone, and content quality
- Evaluate whether the post deserves a like or comment
Autonomous interaction generation:
- Like decision: Based on post content quality, relevance, creativity, etc., autonomously decide whether to like. Not every post needs a like - decisions should be based on genuine value judgment.
- Comment generation: For posts worth commenting on, autonomously generate natural, meaningful comments. Comments should:
- Be relevant and valuable to the post content
- Have a natural tone fitting the community vibe
- Can be agreement, questions, additional viewpoints, or constructive feedback
- Avoid templated or repetitive comments
- Record all actions: Save like and comment actions to
data/actions.json in the following format:[
{
"post_title": "Post Title",
"action": "like" or "comment",
"content": "Comment content (if comment)",
"time": "ISO 8601 timestamp"
}
]
Generate daily summary:
- Use
templates/summary.md as template
- Generate a summary containing:
- Daily Top 5 posts list (sorted by likes)
- Each post's title, publish time, likes count, comments count
- Post content summary
- Action statistics (likes count, comments count)
- Interaction summary (explain why certain posts were liked/commented)
- Daily insights (trends or interesting findings from trending posts)
Key Principles
- Autonomy: Don't use hardcoded templates or fixed replies. Generate comments based on actual post content each time.
- Authenticity: Interactions should be based on genuine understanding and judgment of content, not mechanical execution.
- Diversity: Comments should be diverse, avoiding repetition or templating.
- Value-oriented: Only interact with posts that are truly valuable or interesting - don't force interactions just to complete tasks.
Configuration Requirements
No configuration needed: Moltbook API v1 is public and requires no API key to fetch post data.
Resource Files
scripts/fetch_top_posts.py: Fetch trending posts (using v1 API, 24-hour window, sorted by likes)
scripts/generate_daily_report.py: Generate daily report and save to Obsidian
templates/summary.md: Daily summary template
data/top_posts.json: Post data storage
data/actions.json: Interaction action records
Obsidian Sync
Generated reports are automatically saved to Obsidian vault:
- Save path:
/root/clawd/obsidian-vault/reports/moltbook/YYYY-MM-DD.md
- Filename format:
YYYY-MM-DD.md
- Sync method: Bidirectional sync to your Obsidian vault via GitHub
Execution
When this skill is triggered, the Agent must execute the following steps:
Fetch trending posts:
cd /root/clawd/skills/moltbook-fanboy && python3 scripts/fetch_top_posts.py
Generate daily report (includes interaction generation and Obsidian save):
cd /root/clawd/skills/moltbook-fanboy && python3 scripts/generate_daily_report.py
Read and send: The script outputs the report content, send directly to Telegram
1---2name: moltbook-fanboy3description: Automatically browse Moltbook to get trending posts, generate comments and likes, and create daily summary reports. Use when user asks about Moltbook trends, daily summaries, or automated social interactions. Runs daily via cron at 12:00 Beijing Time.4---5
6# Moltbook Fanboy Skill
7
8This skill automates interactions with Moltbook by browsing trending posts of the day, analyzing content, autonomously generating comments and likes, and finally generating a daily summary report.
9
10## Workflow
11
12When this skill is triggered, the Agent must execute the following steps:
13
141. **Fetch trending posts**: Run `scripts/fetch_top_posts.py` to get the top 5 trending posts from the past 24 hours sorted by likes. Data is saved to `data/top_posts.json`.
15
162. **Autonomous content analysis**:
17 - Read each post's title, body, and metadata
18 - Understand the post's topic, tone, and content quality
19 - Evaluate whether the post deserves a like or comment
20
213. **Autonomous interaction generation**:
22 - **Like decision**: Based on post content quality, relevance, creativity, etc., autonomously decide whether to like. Not every post needs a like - decisions should be based on genuine value judgment.
23 - **Comment generation**: For posts worth commenting on, autonomously generate natural, meaningful comments. Comments should:
24 - Be relevant and valuable to the post content
25 - Have a natural tone fitting the community vibe
26 - Can be agreement, questions, additional viewpoints, or constructive feedback
27 - Avoid templated or repetitive comments
28 - **Record all actions**: Save like and comment actions to `data/actions.json` in the following format:
29 ```json
30 [
31 {
32 "post_title": "Post Title",
33 "action": "like" or "comment",
34 "content": "Comment content (if comment)",
35 "time": "ISO 8601 timestamp"
36 }
37 ]
38 ```
39
404. **Generate daily summary**:
41 - Use `templates/summary.md` as template
42 - Generate a summary containing:
43 - Daily Top 5 posts list (sorted by likes)
44 - Each post's title, publish time, likes count, comments count
45 - Post content summary
46 - Action statistics (likes count, comments count)
47 - Interaction summary (explain why certain posts were liked/commented)
48 - Daily insights (trends or interesting findings from trending posts)
49
50## Key Principles
51
52- **Autonomy**: Don't use hardcoded templates or fixed replies. Generate comments based on actual post content each time.
53- **Authenticity**: Interactions should be based on genuine understanding and judgment of content, not mechanical execution.
54- **Diversity**: Comments should be diverse, avoiding repetition or templating.
55- **Value-oriented**: Only interact with posts that are truly valuable or interesting - don't force interactions just to complete tasks.
56
57## Configuration Requirements
58
59**No configuration needed**: Moltbook API v1 is public and requires no API key to fetch post data.
60
61## Resource Files
62
63- `scripts/fetch_top_posts.py`: Fetch trending posts (using v1 API, 24-hour window, sorted by likes)
64- `scripts/generate_daily_report.py`: Generate daily report and save to Obsidian
65- `templates/summary.md`: Daily summary template
66- `data/top_posts.json`: Post data storage
67- `data/actions.json`: Interaction action records
68
69## Obsidian Sync
70
71Generated reports are automatically saved to Obsidian vault:
72- **Save path**: `/root/clawd/obsidian-vault/reports/moltbook/YYYY-MM-DD.md`
73- **Filename format**: `YYYY-MM-DD.md`
74- **Sync method**: Bidirectional sync to your Obsidian vault via GitHub
75
76## Execution
77
78When this skill is triggered, the Agent must execute the following steps:
79
801. **Fetch trending posts**:
81 ```bash
82 cd /root/clawd/skills/moltbook-fanboy && python3 scripts/fetch_top_posts.py
83 ```
84
852. **Generate daily report** (includes interaction generation and Obsidian save):
86 ```bash
87 cd /root/clawd/skills/moltbook-fanboy && python3 scripts/generate_daily_report.py
88 ```
89
903. **Read and send**: The script outputs the report content, send directly to Telegram