Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

X Topic Tweet

v1.1.2

Research a user-provided topic across the web and current social conversation, then publish one X post in the user's voice. Use when the user gives a topic,...

0· 188·0 current·0 all-time
byDishant Sharma@dishant0406

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for dishant0406/x-topic-tweet.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "X Topic Tweet" (dishant0406/x-topic-tweet) from ClawHub.
Skill page: https://clawhub.ai/dishant0406/x-topic-tweet
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install x-topic-tweet

ClawHub CLI

Package manager switcher

npx clawhub@latest install x-topic-tweet
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
Name/description ask for researching a topic and publishing one X post; SKILL.md instructs precisely that flow (research, draft, open managed browser, context pass, post, verify). No unrelated env vars, binaries, or installs are requested.
Instruction Scope
Instructions are explicit about browsing, reading social posts, drafting, and posting. That matches the purpose, but several rigid 'CRITICAL NON-NEGOTIABLE' rules (always open with `openclaw browser start`, always use the For You tab, never refresh) are unusual and prescriptive; they don't appear malicious but are arbitrary and grant the skill strict control over browsing behavior. The skill also assumes it can operate in a browser session that is able to post as the user (no auth described).
Install Mechanism
Instruction-only skill with no install spec, no downloads, and no code files — lowest-risk installation footprint.
Credentials
No environment variables, credentials, or config paths are requested. The skill expects browser access to publish the post but does not request unrelated secrets or keys.
Persistence & Privilege
always is false and the skill is user-invocable. It does not request permanent/automatic inclusion or system-wide modifications.
Assessment
This skill is internally consistent: it tells the agent how to research and publish a single X post using a managed browser and asks for no credentials or installs. Before enabling or using it, confirm you trust the OpenClaw-managed browser flow (the skill expects to operate in whatever browser session can post to X) and review drafts before publishing. Be cautious about allowing any automation to post from your account—verify that 'openclaw browser start' opens an environment you control, and avoid granting other skills (e.g., a twitter-humanizer) broad permissions without review. If you need stronger assurance, ask the skill to only produce a draft (not publish) so you can post manually.

Like a lobster shell, security has layers — review code before you run it.

latestvk974xw5c8h14xfncehwfq8r3k985bq40
188downloads
0stars
12versions
Updated 5d ago
v1.1.2
MIT-0

X Topic Tweet

Use this skill for a manual, one-off X post. It assumes browser access, web access, and works best when a twitter-humanizer skill is also available.

Do not convert this flow into a cron, loop, or background task. Do not use this skill to evade platform enforcement, mimic human activity for detection avoidance, or hide automation. A short context pass before posting is for situational awareness only.

If the user did not provide a topic, ask for one.

Inputs to infer

  • Topic or event
  • Desired angle or opinion
  • Optional link to include
  • Freshness requirement
  • Any hard constraints on tone, length, or mentions

Workflow

  1. Research before opening X.
    • Use the web for current facts, dates, names, launches, or claims.
    • Prefer official sources first. Use Reddit, X, or other social sources only as supporting sentiment checks, not as the only source of truth.
    • Pull 3 to 5 concrete notes: one fact, one implication, one contrarian or interesting angle, and one detail worth naming.
    • Read references/research-checklist.md.
  2. Draft the post offline.
    • If the twitter-humanizer skill is available, use it to turn the notes into 2 or 3 short candidate tweets in the user's voice.
    • Pick one final tweet. Do not copy wording from source posts.
    • If the topic is time-sensitive, make sure the draft names the right product, company, or date.
  3. Run openclaw browser start to open the openclaw managed browser only after the draft is ready. CRITICAL NON-NEGOTIABLE: always use this command. Never open a browser any other way. Then navigate to X.
  4. Do a brief context pass on X.
    • Land on the home feed and select the For You tab.
    • CRITICAL NON-NEGOTIABLE: always use the For You tab. Never use Following or any other tab.
    • CRITICAL NON-NEGOTIABLE: once on the feed, never refresh or reload the page for any reason. Use back navigation only if you open any posts during the context pass.
    • Scroll the feed first, open a few relevant posts or threads one by one, then return.
    • Read a few posts or one relevant thread so the post fits the current conversation.
    • Do not rush straight to compose unless the user explicitly asked for speed over context.
    • Read references/post-workflow.md.
  5. Compose and post.
    • Keep the post tight, specific, and in first person if that fits the user's usual voice.
    • Include a link only if it improves the post.
    • Avoid hashtags unless the user asked for them or the topic clearly needs one.
  6. Verify the post published correctly.
    • Confirm the final text matches the draft.
    • If a link was included, confirm it rendered properly.
  7. CRITICAL NON-NEGOTIABLE: close every x.com tab immediately after the run is complete. Do not leave any tab open.

Quality bar

  • Sound like a person with an opinion, not a scheduler.
  • Prefer one sharp point over a list of points.
  • CRITICAL NON-NEGOTIABLE: keep the tweet to 1 or 2 short sentences.
  • CRITICAL NON-NEGOTIABLE: never avoid, relax, or reinterpret this limit unless the user explicitly asks for a longer format.
  • Avoid generic hype, marketing filler, or copy that reads AI-generated.
  • Do not force a product mention unless the user asked for it.
  • If the topic has weak evidence or conflicting reports, say less and keep the post safer.

CRITICAL NON-NEGOTIABLE: do not jump between drafting and multiple open threads. CRITICAL NON-NEGOTIABLE: finish the context pass, then compose, then publish in that order.

Completion report

At the end, report:

  • Topic covered
  • Final posted tweet text
  • Sources used for research
  • Whether a link was included
  • Confirmation that all x.com tabs were closed

Comments

Loading comments...