Twitter Post Engage

Runtime-focused release bundle for Twitter/X search, posting, and engagement through the AISA relay.

When to use

• The user wants Twitter/X research plus posting, liking, unliking, following, or unfollowing workflows.
• The task can use a Python client with AISA_API_KEY and explicit OAuth approval.
• The workflow needs a single package that covers read, post, and engagement actions.

When NOT to use

• The user needs cookie extraction, password login, or a fully local Twitter client.
• The workflow must avoid relay-based network calls or media upload through api.aisa.one.
• The task needs undocumented secrets or browser-derived auth values.

Quick Reference

• Required env: AISA_API_KEY
• Read client: ./scripts/twitter_client.py
• Post client: ./scripts/twitter_oauth_client.py
• Engage client: ./scripts/twitter_engagement_client.py
• References: ./references/post_twitter.md, ./references/engage_twitter.md

Setup

export AISA_API_KEY="your-key"

All network calls go to https://api.aisa.one/apis/v1/....

Capabilities

• Read user, tweet, trend, list, community, and Spaces data.
• Publish text, image, and video posts after explicit OAuth approval.
• Like, unlike, follow, and unfollow through the engagement client once authorization exists.
• Reuse the current conversation context instead of local file-based conversation persistence.

Common Commands

python3 scripts/twitter_client.py search --query "AI agents" --type Latest
python3 scripts/twitter_oauth_client.py authorize
# After the user approves the final confirmation artifact:
python3 scripts/twitter_oauth_client.py post --text "Hello from AIsa"
python3 scripts/twitter_engagement_client.py like-latest --user "@elonmusk"
python3 scripts/twitter_engagement_client.py follow-user --user "@elonmusk"

Posting and Engagement Workflow

• Use ./references/post_twitter.md for post, reply, quote, and media-upload actions.
• Use ./references/engage_twitter.md for likes, unlikes, follows, and unfollows.
• Obtain OAuth authorization before any write action.
• Before posting, liking, following, or uploading media, produce a final confirmation artifact that names the exact action, target account or tweet, text/media payload, and approval status. Do not execute the write action until the user explicitly approves that artifact.

ClawHub Suspicious Review Notes

These points summarize the common reasons similar skills are marked Suspicious and how this release addresses them:

• The package is relay-based: read calls, OAuth requests, engagement actions, and approved media uploads go to api.aisa.one.
• The package is API-key-first: it requires AISA_API_KEY and does not ask for passwords, cookies, CT0, or other legacy secrets.
• Write and engagement actions require a user-approved confirmation artifact that records the final action, target, payload, and OAuth approval state before execution.
• The release bundle is runtime-only: it keeps SKILL.md, scripts/, and the required references, while omitting non-runtime files such as README.md and _meta.json.
• The package does not include cache sync, self-install logic, home-directory persistence, browser-cookie extraction, or external agent CLI wrappers.
• Browser opening is optional and not the default workflow; returning the authorization link is the preferred path for this release.

Release Bundle Notes

• scripts/twitter_client.py preserves the read API surface from the original bundle.
• scripts/twitter_oauth_client.py preserves OAuth and posting behavior from the original bundle.
• scripts/twitter_engagement_client.py preserves like, unlike, follow, and unfollow behavior from the original bundle.
• This package is optimized for publication metadata and upload safety, not for changing runtime logic.