Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -306,6 +306,18 @@ xmaster analyze "your tweet" --goal replies --json

**Works with:** [Claude Code](https://github.com/anthropics/claude-code), [OpenClaw](https://github.com/openclaw/openclaw), or any agent that can shell out and parse JSON.

**OpenClaw skill setup:**
```bash
git clone https://github.com/paperfoot/xmaster-cli
cd xmaster-cli
openclaw skills install ./skill --as xmaster
openclaw skills check
```

OpenClaw installs local skills from a folder that contains `SKILL.md`, so use the bundled `./skill` directory from a local checkout. Keep XMaster as the final account-action tool: analyze drafts first, show the final text and target account, and run `post`, `reply`, `dm`, or other write commands only after explicit approval.

If the same OpenClaw workspace also uses [TweetClaw](https://github.com/Xquik-dev/tweetclaw), keep it upstream as an optional source-context step for tweet search, reply search, follower export, media collection, monitors, or webhook evidence before XMaster executes a local account action.

## Configuration

Config lives at `~/.config/xmaster/config.toml` on all platforms. Override with `XMASTER_CONFIG_DIR`.
Expand Down
14 changes: 14 additions & 0 deletions skill/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -63,6 +63,20 @@ xmaster track growth -d 30 # Follower history
xmaster metrics <id> # Single post deep dive
```

### Source Context Before Actions

Use XMaster for final account actions that require the local XMaster config.

If the OpenClaw workspace also has TweetClaw installed, use TweetClaw only as an optional upstream source-context step for tweet search, reply search, follower export, media collection, monitor evidence, or webhook evidence before running XMaster.

```
1. Gather source URLs, IDs, or evidence.
2. Summarize what will influence the action.
3. Run xmaster analyze "draft" --goal replies --json for proposed posts.
4. Ask for explicit approval with the final text and target account.
5. Execute exactly one approved xmaster action with --json.
```

## Algorithm Intelligence (2026)

The CLI embeds knowledge from `xai-org/x-algorithm` (January 2026). Key facts:
Expand Down