ClawHub

AIsa Twitter Research Engage

v1.0.0

Search X/Twitter profiles, tweets, trends, and OAuth-gated posting through AIsa. Use when: the user needs Twitter research, monitoring, or engagement workflo...

⭐ 0· 18·0 current·0 all-time
byAIsa@aisadocs

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for aisadocs/aisa-twitter-research-engage.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "AIsa Twitter Research Engage" (aisadocs/aisa-twitter-research-engage) from ClawHub.
Skill page: https://clawhub.ai/aisadocs/aisa-twitter-research-engage
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required env vars: AISA_API_KEY
Required binaries: python3
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

Canonical install target

openclaw skills install aisadocs/aisa-twitter-research-engage

ClawHub CLI

Package manager switcher

npx clawhub@latest install aisa-twitter-research-engage
Security Scan
Capability signals
Requires OAuth tokenRequires sensitive credentialsPosts externally
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description match the implementation: bundled Python clients implement read/search, engagement (like/follow) relay actions, and OAuth-backed posting. Required binary (python3) and primary environment variable (AISA_API_KEY) are proportional to the stated purpose.
ℹ
Instruction Scope
SKILL.md and reference docs instruct the agent to run the included scripts and to not ask for passwords or cookie-based credentials. The scripts will upload local workspace media and send posting/engagement requests to an external relay (default base URL: https://api.aisa.one). This behavior is coherent with the described workflow but means user content, attached files, and the AISA_API_KEY are transmitted to that external service.
✓
Install Mechanism
There is no network-based install step or external download; the skill is instruction + local Python scripts and requires only python3. No extracted archives or third-party package installs are present in the manifest.
ℹ
Credentials
Only AISA_API_KEY is required by the skill (and optionally environment overrides such as TWITTER_RELAY_BASE_URL and TWITTER_RELAY_TIMEOUT). Requesting a single API key is proportionate, but that key is used as Bearer auth and is also inserted into POST bodies; users should be aware the key is sent to the relay service and will enable that service to act on their behalf.
✓
Persistence & Privilege
The skill does not request always:true, does not modify other skills, and contains no install that persists across the system. It runs local scripts on demand and may optionally open a browser (when --open-browser is used), consistent with an OAuth flow.
Assessment
This skill appears to do what it says: run local Python scripts that call an external relay (default https://api.aisa.one) to search, monitor, like/follow, and post on X/Twitter. Before installing or running it: - Understand that your AISA_API_KEY will be sent to the relay service (in Authorization headers and POST bodies). Only install/use this skill if you trust api.aisa.one (or you set TWITTER_RELAY_BASE_URL to a relay you control). - Attached media files from the agent workspace will be uploaded to the relay for publishing. Treat attachments as being transmitted to that third party. - Prefer running the scripts in an isolated environment (e.g., sandbox or separate account) the first time to verify behavior. Review the three Python scripts in this package yourself — they are readable and use urllib; there is no obfuscated or downloaded code. - Require explicit user approval before posting (SKILL.md endorses this) and confirm which account will be used. If you suspect the key was exposed, rotate/revoke it. - If you need tighter control, set TWITTER_RELAY_BASE_URL to a relay you operate or request the vendor's privacy/security documentation and token scoping options. Overall: technically coherent and consistent with its description, but it relies on a third-party relay and transmits your API key and media to that service — assess trust accordingly.

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

Runtime requirements

🐦 Clawdis
Binspython3
EnvAISA_API_KEY
Primary envAISA_API_KEY
latestvk97bqfyffwkghx96ng26n8wdt985ffc4
18downloads
0stars
1versions
Updated 4h ago
v1.0.0
MIT-0
AIsa@aisadocs
latest
Download

AIsa Twitter Research Engage

Search X/Twitter profiles, tweets, trends, and OAuth-gated posting through AIsa. Use when: the user needs Twitter research, monitoring, or engagement workflows. Supports search, monitoring, and approved posting.

When to use

  • The user needs Twitter/X research, monitoring, posting, or engagement workflows.
  • The user wants profiles, timelines, trends, lists, communities, or Spaces.
  • The user wants approved posting without sharing passwords.

High-Intent Workflows

  • Research an account or conversation thread.
  • Monitor a keyword, trend, or competitor.
  • Authorize and publish a post after explicit approval.

Quick Reference

  • python3 scripts/twitter_client.py --help
  • python3 scripts/twitter_engagement_client.py --help
  • python3 scripts/twitter_oauth_client.py --help

Setup

  • AISA_API_KEY is required for AIsa-backed API access.
  • Use repo-relative scripts/ paths from the shipped package.
  • Prefer explicit CLI auth flags when a script exposes them.

Example Requests

  • Research recent AI agent conversations on X
  • Search how users are reacting to a product launch on Twitter
  • Authorize and publish a short product update post

Guardrails

  • Do not ask for passwords, cookies, or browser credentials.
  • Do not claim posting succeeded until the API confirms it.
  • Return authorization links instead of relying on auto-open behavior.

Comments

Loading comments...