aisa-twitter-engagement-suite

name	aisa-twitter-engagement-suite
description	Research Twitter/X profiles, tweets, and trends, then run approved engagement and posting actions through the AIsa relay. Use when: the user needs Twitter/X research plus likes, follows, unfollows, posting, or post-action follow-through without sharing passwords. Supports relay-based reads, OAuth-approved writes, and media-capable posting flows.
version	1.0.3
license	MIT-0
metadata	{"aisa":{"emoji":"🛠","requires":{"bins":["python3"],"env":["AISA_API_KEY"]},"primaryEnv":"AISA_API_KEY","compatibility":["openclaw","claude-code","hermes"]},"hermes":{"tags":["communication","twitter","x","search","research","aisa"],"related_skills":["aisa-twitter-command-center","aisa-twitter-post-engage"]}}
required_environment_variables	[{"name":"AISA_API_KEY","prompt":"AIsa API key","help":"Get your key from https://aisa.one or the AIsa marketplace account panel.","required_for":"AIsa-backed API access"}]

aisa-twitter-engagement-suite

Research Twitter/X profiles, tweets, and trends, then run approved engagement and posting actions through the AIsa relay. Use when: the user needs Twitter/X research plus likes, follows, unfollows, posting, or post-action follow-through without sharing passwords. Supports relay-based reads, OAuth-approved writes, and media-capable posting flows.

When to Use

• Use this release when the user needs the runtime packaged under scripts/.
• Prefer the bundled Python or shell entrypoints instead of copying raw API examples into the chat.
• For Hermes community installs, keep setup explicit and review the command help text before the first run.

Setup

• Review README.md for the release-specific summary and structure.
• Use repo-relative paths under scripts/.
• Prefer explicit CLI auth flags such as --api-key or --aisa-api-key when a script exposes them.

Quick Reference

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

Verification

• Confirm the command returns structured output or a successful API response.
• If the workflow stores local state, verify it writes under a repo-local data directory rather than a home-directory default.