AIsa Twitter Engagement Suite
ReviewAudited by ClawScan on May 10, 2026.
Overview
This is a coherent Twitter/X integration, but it can post, upload selected media, like, follow, and use OAuth-authorized account access through the AIsa relay.
Before installing, make sure you trust the AIsa relay with your API key, OAuth-authorized Twitter/X actions, and any media files you choose to upload. Use it for explicit posting or engagement requests, and review targets and content carefully before allowing account-changing actions.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If invoked for a posting or engagement task, the agent may create tweets or like/follow/unfollow accounts using the authorized Twitter/X account.
The skill exposes tools that can publish public content and change account engagement state. This matches the stated purpose, but users should recognize the impact of these actions.
Publish text, image, and video posts after explicit OAuth approval. Like, unlike, follow, and unfollow after authorization exists.
Use this only for clearly requested Twitter/X actions, review the content and target account before authorizing actions, and avoid broad or ambiguous engagement requests.
Anyone with access to the configured environment and authorized session may be able to perform the skill's Twitter/X actions through the relay.
The skill requires an AIsa API key and OAuth authorization, which are delegated credentials for relay-backed Twitter/X operations. This is expected for the integration and is disclosed.
Required environment variable: `AISA_API_KEY` ... The task can use a Python client with `AISA_API_KEY` and explicit OAuth approval.
Store the AISA_API_KEY securely, authorize only the intended Twitter/X account, and revoke or rotate access if it is no longer needed.
Any file passed with --media-file will be uploaded outside the local workspace to support the Twitter/X post.
Selected local media files are transmitted to the AIsa relay and then to Twitter/X. The destination and purpose are disclosed and scoped to user-provided attachments.
The Python client reads the local file and sends it to the relay backend as `multipart/form-data`. The relay backend uploads the media to Twitter/X and then publishes the tweet.
Only attach files you intend to publish, and verify the file path before running media-post commands.