Monitor X posts
Scanned@vmathur
npx machina-cli add skill @vmathur/x-monitor --openclawX Monitor
Automated Twitter/X monitoring with intelligent filtering for high-value content.
Setup
1. X API Credentials
Save your X API credentials to ~/.openclaw/workspace/x-monitor/credentials.json:
{
"bearer_token": "YOUR_BEARER_TOKEN_HERE"
}
2. Handles to Monitor
Configure accounts in ~/.openclaw/workspace/x-monitor/handles.json:
{
"handles": [
"naval",
"paul_graham",
"balajis",
"vitalikbuterin"
]
}
Limit: 10-20 handles recommended for API quota management.
3. Schedule Configuration
Configure check frequency in ~/.openclaw/workspace/skills/x-monitor/config/schedule.json:
{
"timezone": "America/Los_Angeles",
"check_times": ["08:00", "12:00", "16:00", "20:00"],
"enabled": true
}
Options:
timezone: IANA timezone string (e.g., "America/New_York", "Europe/London", "Asia/Tokyo")check_times: Array of 24-hour times for daily checks (e.g., ["09:00", "18:00"] for twice daily)enabled: Set to false to pause scheduled checks
Common schedules:
- 4x daily (default):
["08:00", "12:00", "16:00", "20:00"] - 3x daily:
["09:00", "14:00", "20:00"] - 2x daily:
["09:00", "18:00"] - 1x daily:
["09:00"]
4. Setup Cron Jobs
After configuring your schedule, ask the agent to set up the cron jobs:
- "set up x monitor cron jobs" — creates cron jobs based on your schedule.json
- "update x monitor schedule" — updates cron jobs after changing schedule.json
5. Noteworthy Criteria
Edit ~/.openclaw/workspace/x-monitor/noteworthy-criteria.md to customize what gets surfaced.
Scheduled Reports
Reports run at the times specified in config/schedule.json. Each report includes:
- Executive summary — high-level overview of noteworthy items
- Filtered tweets — chronological list with author, content, metrics
Commands
Manage handles:
- "add @username to x monitor" — add a new handle
- "remove @username from x monitor" — remove a handle
- "show x monitor handles" — list current handles
Manual check:
- "check x now" — run immediate report
Schedule management:
- "show x monitor schedule" — display current schedule config
- "set x monitor to check at 9am and 6pm" — update check times
- "set x monitor timezone to America/New_York" — update timezone
- "set up x monitor cron jobs" — create/update cron jobs from schedule.json
Update criteria:
- "show noteworthy criteria" — display current filter rules
- "update noteworthy criteria" — help edit the criteria
What Counts as Noteworthy (Default)
Include:
- Insights on technology trends, AI, crypto, product design
- First-person experiences building/shipping
- Novel frameworks, metaphors, or mental models
- Data-driven observations with concrete examples
- Contrarian but well-argued takes
Exclude:
- Political rage bait or partisan content
- Generic motivational quotes
- Pure engagement farming
API Details
Uses X API v2 tweets/search/recent endpoint:
- Max results: 10 per handle per check
- Fields:
created_at,public_metrics,author_id,lang - Expansions:
author_idfor full user info - Query pattern:
from:{handle}
Storage
- Credentials:
~/.openclaw/workspace/x-monitor/credentials.json - Handles:
~/.openclaw/workspace/x-monitor/handles.json - Schedule:
~/.openclaw/workspace/skills/x-monitor/config/schedule.json - Criteria:
~/.openclaw/workspace/x-monitor/noteworthy-criteria.md - Last check:
~/.openclaw/workspace/x-monitor/last-check.json(timestamp tracking)
Cron Job Setup
When setting up cron jobs, the agent will:
- Read
config/schedule.jsonfor timezone and times - Create isolated cron jobs using
agentTurnpayloads - Each job runs: fetch tweets → filter for noteworthy → deliver summary
Example cron expression for 8am in America/Los_Angeles:
{
"schedule": { "kind": "cron", "expr": "0 8 * * *", "tz": "America/Los_Angeles" },
"payload": { "kind": "agentTurn", "message": "Run x-monitor check and report noteworthy tweets" }
}
Error Handling
- Rate limits: Backs off and logs warning
- Invalid handles: Skips and reports
- API errors: Logs and continues with remaining handles
Overview
X Monitor automates Twitter/X monitoring for selected accounts on a configurable schedule. It surfaces noteworthy tweets about technology and trends while excluding political rage bait, helping you manage accounts, run manual checks, or refine filtering criteria.
How This Skill Works
The skill authenticates with X API credentials stored at ~/.openclaw/workspace/x-monitor/credentials.json and reads monitored handles from ~/.openclaw/workspace/x-monitor/handles.json and schedule from schedule.json. It queries the X API v2 tweets/recent endpoint (max 10 results per handle per check), enriches results with author details, and surfaces items that match the noteworthy criteria (noteworthy-criteria.md).
When to Use It
- When you want to manage your X account list by adding or removing handles in handles.json.
- When you want to run a manual check and generate an immediate report with 'check x now'.
- When you want to update or tune the filtering rules in noteworthy-criteria.md.
- When you want scheduled, automated digests at configured times from schedule.json.
- When you want to surface technology trends, AI, crypto, or product-design insights from influential accounts.
Quick Start
- Step 1: Save credentials at ~/.openclaw/workspace/x-monitor/credentials.json and populate handles.json with accounts to monitor.
- Step 2: Configure schedule.json (timezone and check_times) and enable cron jobs, then run 'set up x monitor cron jobs' for automation.
- Step 3: Run a manual check with 'check x now' to generate the first report and validate results.
Best Practices
- Keep handles.json within a practical quota (10-20 handles) to respect API quota limits.
- Regularly update noteworthy-criteria.md to refine what gets surfaced.
- Test changes with a manual check before depending on cron-generated reports.
- Use the executive summary to quickly grasp core insights in each report.
- Review surfaced items for balance and avoid including political rage bait.
Example Use Cases
- Monitor high-profile tech accounts like naval, paul_graham, balajis, and vitalikbuterin to surface daily tech-trend tweets.
- Perform a manual check after adjusting noteworthy criteria to validate new signals.
- Generate a concise executive summary highlighting data-driven observations with concrete examples.
- Capture insights on novel frameworks or mental models from the surfaced tweets.
- Use cron-driven reports to maintain a consistent, time-weighted view of tech discourse without political content.