← Back to Skills Marketplace
1431
Downloads
0
Stars
9
Active Installs
1
Versions
Install in OpenClaw
/install x-monitor
Description
Monitor specific X/Twitter accounts and surface noteworthy tweets on a configurable schedule. Filters for high-value content about technology and trends, excluding political rage bait. Use when user wants to manage their X account list, run a manual check, or update filtering criteria.
Usage Guidance
This skill appears to implement X monitoring but has a few issues you should resolve before installing: (1) Fix the path inconsistency — SKILL.md and scripts use two different base paths (~/.openclaw/workspace/x-monitor vs ~/.openclaw/workspace/skills/x-monitor). Confirm where credentials, handles, schedule, and last-check files will live. (2) The skill stores your X bearer token in plaintext under your home directory; restrict file permissions (chmod 600), consider using a secrets manager or environment-secret instead, and rotate the token if shared. (3) The agent will create cron jobs that schedule future agentTurn runs — review exactly what the scheduled payloads do and ensure you want recurring autonomous checks. (4) Test a manual run ('check x now') and inspect outputs and logs before enabling the schedule. If you want higher assurance, ask the author to correct the path inconsistencies and to document where scheduled jobs will run and which account identity they use.
Capability Analysis
Type: OpenClaw Skill
Name: x-monitor
Version: 1.0.0
The OpenClaw AgentSkills bundle 'x-monitor' is classified as benign. All files (SKILL.md, scripts/setup-crons.sh, scripts/fetch-tweets.py, config/schedule.json, _meta.json) align with the stated purpose of monitoring X/Twitter accounts. The `SKILL.md` instructions for setting up cron jobs specify using an `agentTurn` payload, which is a message for the agent to interpret, rather than a direct shell command, mitigating prompt injection risks. The Python script (`fetch-tweets.py`) correctly uses the X API, reads credentials from a designated workspace file, and stores data within the skill's workspace, showing no signs of unauthorized data exfiltration, malicious execution, or persistence mechanisms.
Capability Assessment
Purpose & Capability
The code and SKILL.md implement the described purpose (fetching tweets, filtering, scheduling). However there's a clear path inconsistency: fetch-tweets.py reads credentials/handles from ~/.openclaw/workspace/x-monitor/, while the cron setup and schedule.json locations in SKILL.md use ~/.openclaw/workspace/skills/x-monitor/config/schedule.json. This mismatch means scheduled jobs may not find credentials/handles or the script may not read the intended schedule, which is an incoherent design choice.
Instruction Scope
Instructions are generally scoped to the skill's purpose (store bearer token, list handles, configure schedule, create cron jobs). But the SKILL.md asks the agent to create cron jobs that post 'agentTurn' payloads (i.e., schedule future autonomous agent actions). That grants the skill recurring autonomous execution via the platform scheduler — expected for a monitor but worth noting. Also several paths in the docs differ (see purpose_capability), which could cause the agent to read/write unexpected locations or fail silently.
Install Mechanism
No install spec; the skill is instruction + scripts. There are no remote downloads or obscure installers. The Python script uses requests and local JSON files; the bash script only prints cron expressions. This is low risk from an install mechanism perspective.
Credentials
The only credential the skill needs is the X bearer token, which the SKILL.md asks you to store in a local credentials.json. The registry metadata lists no required env vars — consistent with file-based credentials. Storing a bearer token in plaintext under your home directory is functional but a security/privacy risk (consider file permissions or using a secrets store). There are no other unrelated credentials requested.
Persistence & Privilege
always:false and normal autonomous invocation are set. The skill instructs creating cron jobs that schedule agentTurn payloads, giving it persistent, recurring execution capability. This is reasonable for a monitor but increases the blast radius if the skill behaved unexpectedly; ensure you understand/approve the scheduled payloads before enabling them.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install x-monitor - After installation, invoke the skill by name or use
/x-monitor - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release of x-monitor: an automated tool for tracking high-value technology and trend tweets from selected X/Twitter accounts.
- Monitors specific X/Twitter handles and filters for noteworthy, non-political content.
- Configurable schedules via JSON (timezone, check times, enable/disable).
- Supports up to 10–20 handles; easy add/remove/list commands.
- Scheduled and manual reports include executive summaries and filtered tweet details.
- Criteria for noteworthy content customizable via markdown file.
- Cron jobs set up and updated based on schedule configuration.
- Handles API errors, rate limits, and invalid accounts gracefully.
Metadata
Frequently Asked Questions
What is Monitor X posts?
Monitor specific X/Twitter accounts and surface noteworthy tweets on a configurable schedule. Filters for high-value content about technology and trends, excluding political rage bait. Use when user wants to manage their X account list, run a manual check, or update filtering criteria. It is an AI Agent Skill for Claude Code / OpenClaw, with 1431 downloads so far.
How do I install Monitor X posts?
Run "/install x-monitor" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Monitor X posts free?
Yes, Monitor X posts is completely free (open-source). You can download, install and use it at no cost.
Which platforms does Monitor X posts support?
Monitor X posts is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Monitor X posts?
It is built and maintained by vmathur (@vmathur); the current version is v1.0.0.
More Skills