x-keyword-comment
X (Twitter) keyword-based reply posting: search tweets by keyword, read each tweet's content, generate contextual replies from a configured brand persona, and post replies to the reply area. Use when user wants to batch reply to X tweets by keyword, auto-comment on X topic tweets, drive traffic via X comments, X comment outreach, search X tweets and leave comments, bulk reply to Twitter search results, keyword comment on Twitter, post replies on X search page, Twitter keyword comment marketing, X reply campaign, engage with X discussions, or comment on tweets matching a topic.
npx skills add browser-act/skills --skill x-keyword-comment --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# X — Keyword Comment > keyword + reply intent → search X tweets → read tweet content → generate contextual replies → post to reply area ## Language All process output to user (progress updates, process notifications) follows the user's language. ## Objective Search X by keyword, read each tweet's content, generate contextual replies based on a configured brand persona, and post them — all within a browser-act session. ## Prerequisites - `config/keyword-comment-config.json` has been filled in with actual product, persona, and tone values (all `YOUR_*` placeholders replaced before first run) ## Session Rule `{SESSION}` is a temporary, per-run session name used in all `browser-act --session {SESSION}` commands below. It is generated at execution start (e.g., `xkc-{timestamp}`) and not persisted across runs. ## Pre-execution Checks ### 1. Tool Readiness If browser-act has been confirmed available in the current conversation → skip this step. Invoke `browser-act` via Skill tool to load usage. If installation or configuration issues arise, follow its guidance to resolve then retry. ### 2. Load Config ```bash python -c " import json, pathlib, sys for base in ['.claude/skills/x-keyword-co
- Language
- Objective
- Prerequisites
- Session Rule
- Pre-execution Checks
- 1. Tool Readiness
- 2. Load Config
- 3. Browser Selection
- 4. Open Session
- 5. Login Verification
- Capability Components
- AI Workflow: Pre-reply Warmup
- DOM: Scan Replyable Tweets on Current Page
- DOM: Click Reply Button (Open Editor)
python -c "
import json, pathlib, sys
for base in ['.claude/skills/x-keyword-comment', 'output/x-keyword-comment']:
cfg = pathlib.Path(base) / 'config/keyword-comment-config.json'
if cfg.exists():
browser-act browser list
browser-act --session {SESSION} browser open {BROWSER_ID} https://x.com/ --headed
browser-act session list
browser-act --session {SESSION} navigate "https://x.com/notifications"
browser-act --session {SESSION} wait stableWhat does the x-keyword-comment skill do?
X (Twitter) keyword-based reply posting: search tweets by keyword, read each tweet's content, generate contextual replies from a configured brand persona, and post replies to the reply area. Use when user wants to batch reply to X tweets by keyword, auto-comment on X topic tweets, drive traffic via X comments, X comment outreach, search X tweets and leave comments, bulk reply to Twitter search results, keyword comment on Twitter, post replies on X search page, Twitter keyword comment marketing, X reply campaign, engage with X discussions, or comment on tweets matching a topic.
How do I install it?
Run `npx skills add browser-act/skills --skill x-keyword-comment --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From browser-act/skills, a repository with 5,160 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.