Skip to content

Add TweetClaw operator recipe#1

Open
kriptoburak wants to merge 2 commits into
smashingtags:mainfrom
kriptoburak:codex/add-tweetclaw-operator-recipe
Open

Add TweetClaw operator recipe#1
kriptoburak wants to merge 2 commits into
smashingtags:mainfrom
kriptoburak:codex/add-tweetclaw-operator-recipe

Conversation

@kriptoburak
Copy link
Copy Markdown

@kriptoburak kriptoburak commented May 15, 2026

Summary

  • Add a TweetClaw companion recipe for operators that need public X/Twitter workflows from OpenClaw.
  • Document npm install, tools.alsoAllow, local Xquik API key storage, and approval review for visible X/Twitter actions.
  • Add the MIT license file that is already referenced by the package metadata and README badge.
  • Add the xquik.com NHS Agentic Readiness badge in the existing badge block because the new companion workflow depends on xquik.com.

Validation

  • Checked target repo metadata, README, package metadata, OpenClaw manifest, commit history, and duplicate PR/issue searches for TweetClaw/Xquik/Twitter terms.
  • Verified links: target repo, TweetClaw GitHub, xquik.com NHS page and badge, OpenClaw, ImogenLabs, operator-kit npm registry metadata, TweetClaw npm registry metadata.
  • npm ci --ignore-scripts --no-audit --no-fund
  • npm exec --yes --package typescript -- tsc --noEmit --module NodeNext --moduleResolution NodeNext --target ES2022 --skipLibCheck index.ts
  • npm pack --dry-run --json
  • git diff --check

Summary by Sourcery

Document TweetClaw as a companion plugin for X/Twitter workflows and add project licensing and readiness badges.

Documentation:

  • Add README section describing installing and configuring the TweetClaw companion plugin for public X/Twitter workflows, including API key handling and approval guidance.
  • Add an NHS Agentic Readiness badge for xquik.com to the README badge block.

Chores:

  • Add the MIT license file referenced by the package metadata and README.

@sourcery-ai
Copy link
Copy Markdown

sourcery-ai Bot commented May 15, 2026

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Adds documentation and configuration guidance for using the TweetClaw companion with operator-kit, introduces an NHS Agentic Readiness badge for xquik.com, and adds the project’s MIT license file referenced by existing metadata.

File-Level Changes

Change Details Files
Document TweetClaw as a companion plugin for X/Twitter workflows and how to configure it in OpenClaw.
  • Add a new README section describing TweetClaw as a companion for operators needing public X/Twitter workflows.
  • Provide openclaw installation and configuration commands, including tools.alsoAllow settings for TweetClaw.
  • Describe supported TweetClaw workflows and emphasize approval-gated actions for visible X/Twitter operations.
  • Document secure handling of the Xquik API key, advising local config/environment storage and avoidance of checked-in artifacts.
README.md
Expose the dependency on xquik.com via an NHS Agentic Readiness badge in project documentation.
  • Add the xquik.com NHS Agentic Readiness badge to the existing badge block in the README.
README.md
Check in the MIT license file that the package already references.
  • Add an MIT LICENSE file to the repository so it matches the license referenced by npm metadata and the README badge.
LICENSE

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link
Copy Markdown

@sourcery-ai sourcery-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've found 1 issue, and left some high level feedback:

  • In the new TweetClaw section, fix the sentence "Use it for scrape tweets" to be grammatically correct (e.g., "Use it to scrape tweets...") so the usage description reads clearly.
  • The long list of TweetClaw capabilities in a single sentence is hard to scan; consider breaking it into a bulleted list (e.g., scraping, search, DMs, webhooks, giveaways, posting) to make key workflows easier to identify.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- In the new TweetClaw section, fix the sentence "Use it for scrape tweets" to be grammatically correct (e.g., "Use it to scrape tweets...") so the usage description reads clearly.
- The long list of TweetClaw capabilities in a single sentence is hard to scan; consider breaking it into a bulleted list (e.g., scraping, search, DMs, webhooks, giveaways, posting) to make key workflows easier to identify.

## Individual Comments

### Comment 1
<location path="README.md" line_range="141" />
<code_context>
+openclaw config set tools.alsoAllow '["explore", "tweetclaw"]'
+```
+
+Use it for scrape tweets, tweet scraper workflows, search tweets, search tweet replies, follower export, user lookup, media upload, media download, direct messages, monitor tweets, webhooks, giveaway draws, and approval-gated post tweets or post tweet replies.
+
+Keep the Xquik API key in local OpenClaw config or environment variables. Do not store it in generated `TOOLS.md`, memory files, chats, or committed docs. Operator-kit's seeded `ask-before-external` instinct pairs well with TweetClaw: review the structured request before approving any visible X/Twitter action.
</code_context>
<issue_to_address>
**suggestion (typo):** Consider rephrasing this sentence to fix grammar and improve clarity.

For example, you could rewrite it as:

`Use it to scrape tweets, run tweet-scraper workflows, search tweets and tweet replies, export followers, look up users, upload and download media, send direct messages, monitor tweets, handle webhooks, run giveaway draws, and perform approval-gated posting of tweets or tweet replies.`

At minimum, changing `Use it for scrape tweets``Use it to scrape tweets` and `approval-gated post tweets or post tweet replies``approval-gated posting of tweets or tweet replies` would improve readability.

```suggestion
Use it to scrape tweets, run tweet-scraper workflows, search tweets and tweet replies, export followers, look up users, upload and download media, send direct messages, monitor tweets, handle webhooks, run giveaway draws, and perform approval-gated posting of tweets or tweet replies.
```
</issue_to_address>

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Comment thread README.md Outdated
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant