docs: add TweetClaw OpenClaw GTM path

[kriptoburak]

Summary

• Add TweetClaw as the OpenClaw native option for the Twitter GTM Find skill.
• Keep Apify as the default discovery path and Hermes Tweet as the Hermes Agent option.
• Update the root README, skill README, registry metadata, and SKILL.md wording for tweet search, reply search, user lookup, follower export, monitors, and webhooks.

Duplicate Checks

• Searched issues and PRs for TweetClaw, @xquik/tweetclaw, Xquik-dev/tweetclaw, xquik/tweetclaw, and x-twitter-scraper.
• Existing PR docs: add Hermes Tweet GTM discovery path #22 only covers Hermes Tweet, not TweetClaw.
• GitHub code search for tweetclaw in Varnan-Tech/opendirectory returned no matches before this branch.

Validation

• pnpm install with frozen lockfile
• pnpm exec tsx scripts/validate-skill-descriptions.ts
• pnpm exec tsx scripts/validate-pr.ts
• pnpm exec tsx scripts/build-registry.ts
• pnpm exec tsx scripts/update-readme.ts
• pnpm exec tsx scripts/update-contributing.ts
• packages/cli build
• packages/cli e2e test
• git diff check
• README and skill link check
• npm view @xquik/tweetclaw version returned 1.6.31

[greptile-apps]

Greptile Summary

This PR adds TweetClaw (@xquik/tweetclaw) as an optional OpenClaw-native discovery path alongside the existing Apify default and Hermes Tweet option for the twitter-GTM-find-skill, updating descriptions consistently across four documentation files.

• Root README.md and registry.json — description strings refreshed to mention TweetClaw and Hermes Tweet as alternative paths; registry.json also gains a missing end-of-file newline.
• Skill README.md — new "For OpenClaw users" sub-section added with install command, XQUIK_API_KEY setup note, and explore/tweetclaw command guidance.
• SKILL.md — parallel TweetClaw block inserted before the Hermes Tweet block; section heading renamed to "Optional Native X/Twitter Plugin Inputs".

Confidence Score: 4/5

Documentation-only change; no executable code paths are modified and all three discovery paths converge on the same unchanged ICP validation step.

The TweetClaw install command, GitHub URL, and npm package name are internally consistent and the PR author confirmed the package exists. The only gap is that XQUIK_API_KEY is referenced in the new TweetClaw section but absent from both .env setup blocks, which could cause friction for first-time users.

Both skills/twitter-GTM-find-skill/README.md and skills/twitter-GTM-find-skill/twitter-GTM-find/SKILL.md are missing XQUIK_API_KEY from their env-var setup checklists.

Important Files Changed

Filename	Overview
README.md	Two description strings for twitter-GTM-find-skill updated to mention TweetClaw; both replacements are accurate and consistent with the skill README.
packages/cli/registry.json	Description updated to mention TweetClaw/Hermes Tweet options; also fixes missing newline at end of file.
skills/twitter-GTM-find-skill/README.md	New TweetClaw section added with install command and usage notes; XQUIK_API_KEY is referenced but not listed in the .env setup block in the Usage section.
skills/twitter-GTM-find-skill/twitter-GTM-find/SKILL.md	TweetClaw plugin instructions added to the Optional Plugin Inputs section; XQUIK_API_KEY still absent from the Requirements env-var list.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Start: Twitter GTM Find Skill] --> B{Discovery Path}
    B -->|Default| C[Apify Scraper\nAPIFY_API_TOKEN]
    B -->|OpenClaw users| D[TweetClaw Plugin\nopenclaw plugins install @xquik/tweetclaw\nXQUIK_API_KEY]
    B -->|Hermes Agent users| E[Hermes Tweet Plugin\nhermes plugins install Xquik-dev/hermes-tweet\nXQUIK_API_KEY]
    C --> F[Raw candidates\nradar-jobs.json]
    D --> F
    E --> F
    F --> G[ICP Validation\nGemini Search Grounding\nGEMINI_API_KEY]
    G --> H[Validated leads\nopenclaw-icp-jobs.json]

Loading

Comments Outside Diff (2)

1. skills/twitter-GTM-find-skill/twitter-GTM-find/SKILL.md, line 22-24 (link)

   The Requirements block lists only APIFY_API_TOKEN, GEMINI_API_KEY, and MAX_POSTS, but the new TweetClaw section (and the pre-existing Hermes Tweet section) both reference XQUIK_API_KEY. A reader setting up the TweetClaw path will have to hunt for that key name; adding it here keeps the setup checklist complete.

2. skills/twitter-GTM-find-skill/README.md, line 54-58 (link)

   The Usage section's .env block lists only the three Apify/Gemini variables, but the new TweetClaw path (and the existing Hermes Tweet path) both need XQUIK_API_KEY. Adding it here as an optional entry keeps the setup block in sync with the plugin documentation above.

   env
   APIFY_API_TOKEN=your_apify_token
   GEMINI_API_KEY=your_gemini_api_key
   MAX_POSTS=20
   XQUIK_API_KEY=your_xquik_api_key # Required for TweetClaw / Hermes Tweet paths

_{Reviews (1): Last reviewed commit: "docs: add TweetClaw OpenClaw GTM path" | Re-trigger Greptile}