I prepared a small docs-only change that adds TweetClaw as a concrete OpenClaw plugin example in the plugin command reference. The branch is here:
https://github.com/kriptoburak/explain-openclaw/tree/codex/add-tweetclaw-openclaw-example
Compare:
master...kriptoburak:explain-openclaw:codex/add-tweetclaw-openclaw-example
The edit documents:
openclaw plugins install @xquik/tweetclaw
- runtime verification with
openclaw plugins inspect tweetclaw --runtime and openclaw skills info tweetclaw
- explicit
tools.alsoAllow for explore and tweetclaw when the default tool profile hides plugin tools
- ClawHub-first install behavior, review-before-credentials guidance, and OpenClaw
>=2026.5.4 compatibility
I checked repo content plus open/closed issue and PR listings for existing TweetClaw/Xquik mentions and did not find a duplicate. git diff --check passes. I tried opening this as a PR first, but GitHub rejected PR creation from my authenticated API path, so I am leaving the prepared branch here for maintainer review.
I prepared a small docs-only change that adds TweetClaw as a concrete OpenClaw plugin example in the plugin command reference. The branch is here:
https://github.com/kriptoburak/explain-openclaw/tree/codex/add-tweetclaw-openclaw-example
Compare:
master...kriptoburak:explain-openclaw:codex/add-tweetclaw-openclaw-example
The edit documents:
openclaw plugins install @xquik/tweetclawopenclaw plugins inspect tweetclaw --runtimeandopenclaw skills info tweetclawtools.alsoAllowforexploreandtweetclawwhen the default tool profile hides plugin tools>=2026.5.4compatibilityI checked repo content plus open/closed issue and PR listings for existing TweetClaw/Xquik mentions and did not find a duplicate.
git diff --checkpasses. I tried opening this as a PR first, but GitHub rejected PR creation from my authenticated API path, so I am leaving the prepared branch here for maintainer review.