Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Twitter/X All-in-One — Search, Monitor & Publish Text & Media Posts
v2.0.3Searches and reads X (Twitter): profiles, timelines, mentions, followers, tweet search, trends, lists, communities, and Spaces. Publishes posts, likes/unlike...
⭐ 1· 137·0 current·0 all-time
byAIsa@aisadocs
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Suspicious
high confidencePurpose & Capability
The name/description (Twitter/X read, monitor, post, engage) aligns with the included scripts and workflows which call aisa.one relay endpoints; requiring curl and python3 is reasonable. The design relies on a single third-party API key (AISA_API_KEY) and a relay service rather than direct Twitter credentials, which is coherent for a proxy-based implementation.
Instruction Scope
Runtime instructions and the Python clients instruct the agent to upload local workspace attachments and publish posts via api.aisa.one. That means user-provided media and content are transmitted to a third-party relay (aisa.one). The code also spreads the AISA_API_KEY into POST bodies (body.setdefault('aisa_api_key', self.api_key)) in addition to the Authorization header, increasing exposure of the key. Scripts allow overriding the relay base URL via TWITTER_RELAY_BASE_URL (not declared), which could redirect uploads/credentials to another host if set.
Install Mechanism
No external installers or downloaded archives; the skill is distributed as Python scripts and docs. There is no install step that fetches code from arbitrary URLs. Execution requires python3 and curl already present.
Credentials
The declared required env var is only AISA_API_KEY (primaryEnv). However the code reads additional environment variables (e.g., TWITTER_RELAY_BASE_URL, TWITTER_RELAY_TIMEOUT) not listed in requires.env or primaryEnv. The single AISA_API_KEY is powerful for this skill (authorizes many read and relay actions) and is placed in request bodies by the client code, increasing the risk of accidental disclosure. The skill does not require direct Twitter credentials (by design), but you must trust the relay operator with OAuth flows and uploaded media.
Persistence & Privilege
The skill is not always-enabled and does not request elevated platform privileges in the manifest. It does not modify other skills or system settings. Autonomous invocation is allowed (default) but not an additional flagged privilege here.
What to consider before installing
This skill uses a proxy/relay service (api.aisa.one) to perform all Twitter reads, OAuth posting, and media uploads. Before installing, understand and accept that: (1) your AISA_API_KEY authorizes the skill to call the relay on your behalf and is sent in headers and sometimes in request bodies — treat it like a sensitive credential; (2) any files you put in the OpenClaw workspace will be uploaded to the relay to publish media — do not place sensitive files there; (3) the scripts can be configured via TWITTER_RELAY_BASE_URL and other env vars (which are not listed in the manifest) — do not set those to untrusted endpoints, and prefer the default aisa.one endpoints unless you control the alternative; (4) consider using a limited/disposable AISA_API_KEY and review the included Python scripts yourself if you have concerns. If you need stronger assurance, ask the publisher for a security/privacy policy or host a vetted relay you control.Like a lobster shell, security has layers — review code before you run it.
latestvk974ax1za29jdgyfen21gbtvyh84cr1r
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🐦 Clawdis
Binscurl, python3
EnvAISA_API_KEY
Primary envAISA_API_KEY