← Back to Skills Marketplace
AIsa Twitter Post Engage
by
baofeng-tech
· GitHub ↗
· v1.0.2
· MIT-0
121
Downloads
0
Stars
0
Active Installs
3
Versions
Install in OpenClaw
/install aisa-twitter-post-engage
Description
Run Twitter/X post-launch follow-through through AIsa. Use when: the user already has a draft, launch tweet, or reply target and needs one skill to publish a...
README (SKILL.md)
AIsa Twitter Post-Launch Follow-Through
Run Twitter/X post-launch follow-through through AIsa. Use when: the user already has a draft, launch tweet, or reply target and needs one skill to publish and then manage early interactions. Supports posting, reply context, and lightweight engagement.
When to use
- The user already has a draft, launch tweet, campaign, or reply target.
- The user needs one workflow to publish first and then handle the earliest follow-through actions.
- The user wants approved posting and lightweight engagement without sharing passwords.
High-Intent Workflows
- Publish a confirmed update and handle the first wave of reactions.
- Move from a draft or launch tweet into reply and follow-through actions.
- Use one workflow for post-launch context, posting, and lightweight engagement.
Quick Reference
python3 scripts/twitter_client.py --helppython3 scripts/twitter_engagement_client.py --helppython3 scripts/twitter_oauth_client.py --help
Setup
AISA_API_KEYis 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.
- Optional: set
TWITTER_RELAY_BASE_URLto override the default relayhttps://api.aisa.one/apis/v1/twitter. - Optional: set
TWITTER_RELAY_TIMEOUTto tune relay request timeouts in seconds. - OAuth requests and any user-approved media uploads use the configured AIsa relay and default to
https://api.aisa.one/apis/v1/twitter. - Provide only
AISA_API_KEY; do not use passwords, cookies, or browser credential export.
Example Requests
- Authorize a product update post and handle the first follow-up actions
- Publish a launch tweet and then review or reply to early reactions
- Start from a draft and move into post-launch engagement
Guardrails
- Do not market this package as a long-running social-growth control tower.
- Do not ask for passwords, cookies, or browser credentials.
- Do not claim posting or engagement succeeded until the API confirms it.
- Only upload local files the user explicitly attached, and make it clear those files are sent to the configured AIsa relay first.
Usage Guidance
This package looks internally consistent with its stated purpose: it uses the AISA_API_KEY to communicate with an AIsa relay (default https://api.aisa.one) to publish and engage on X/Twitter and to upload user-provided media. Before installing, confirm you trust the AIsa relay operator (api.aisa.one) because media and posts will be proxied through that service. Be aware that the agent can be configured to act autonomously (default model invocation allowed) so ensure you only provide an AISA_API_KEY with the minimal scope you are comfortable granting. If you do not trust the relay, do not set AISA_API_KEY or override TWITTER_RELAY_BASE_URL to an untrusted host. If you want extra assurance, review the included Python scripts locally (they are in the package) and test with a low-permission / throwaway API key first.
Capability Analysis
Type: OpenClaw Skill
Name: aisa-twitter-post-engage
Version: 1.0.2
The skill bundle provides a legitimate interface for interacting with Twitter/X via the AIsa API relay (api.aisa.one). It includes Python scripts (twitter_client.py, twitter_engagement_client.py, twitter_oauth_client.py) for reading user data, performing engagement actions like following or liking, and publishing tweets with media support. The code uses standard Python libraries, implements character-weight threading for long posts, and includes explicit guardrails in SKILL.md and the scripts to prevent the collection of sensitive credentials like passwords or cookies. While it reads local files for media uploads, it validates MIME types to ensure only images and videos are processed, and its behavior is entirely consistent with its stated purpose.
Capability Tags
Capability Assessment
Purpose & Capability
Name/description ask for publishing and engagement on X/Twitter and the package requires python3 and AISA_API_KEY only. The included scripts call a relay (default https://api.aisa.one) and provide posting, engagement, and OAuth flows — which match the declared purpose.
Instruction Scope
SKILL.md instructs the agent to use the shipped scripts, to rely on AISA_API_KEY and the AIsa relay, to not request passwords or cookies, and to only upload user-attached local files. The scripts only reference the declared env vars and workspace file paths for media; they do not attempt to read other system credentials or unexpected paths.
Install Mechanism
No install spec is provided (instruction-only runtime plus bundled scripts). No remote downloads or archive extraction are performed by an installer — the package contains Python scripts meant to run directly, which is a low-risk install mechanism.
Credentials
Only AISA_API_KEY is required (with optional TWITTER_RELAY_BASE_URL and TWITTER_RELAY_TIMEOUT). That is proportionate: the relay-based design explains why the relay API key is needed and no Twitter passwords or other unrelated secrets are requested.
Persistence & Privilege
The skill is not set to always:true and does not attempt to modify other skills or system-wide configs. Model invocation is allowed (default), which is expected for an agent skill; combine this with normal caution about granting posting permissions to any automated agent.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install aisa-twitter-post-engage - After installation, invoke the skill by name or use
/aisa-twitter-post-engage - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.2
- Bumped version to 1.0.2.
- Minor content or metadata updates for documentation and scripts.
- No user-facing feature changes or major new functionality.
v1.0.1
Version 1.0.1
- Updated focus to "post-launch follow-through" workflows for Twitter/X.
- Revised description and usage to emphasize publishing and managing early interactions, not broad research or monitoring.
- Added support for optional environment variables: TWITTER_RELAY_BASE_URL and TWITTER_RELAY_TIMEOUT.
- Enhanced guardrails and setup instructions for safer file upload and relay configuration.
- Clarified that long-term monitoring or full social control is out of scope.
v1.0.0
Initial release of aisa-twitter-post-engage.
- Search X/Twitter profiles, tweets, and trends through AIsa.
- Monitor keywords, trends, accounts, and competitors.
- Publish posts via OAuth and explicit user approval (no password sharing).
- Supports user-invocable workflows for X/Twitter research, monitoring, and engagement.
- Guides for setup, usage, and safety included.
Metadata
Frequently Asked Questions
What is AIsa Twitter Post Engage?
Run Twitter/X post-launch follow-through through AIsa. Use when: the user already has a draft, launch tweet, or reply target and needs one skill to publish a... It is an AI Agent Skill for Claude Code / OpenClaw, with 121 downloads so far.
How do I install AIsa Twitter Post Engage?
Run "/install aisa-twitter-post-engage" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is AIsa Twitter Post Engage free?
Yes, AIsa Twitter Post Engage is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does AIsa Twitter Post Engage support?
AIsa Twitter Post Engage is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created AIsa Twitter Post Engage?
It is built and maintained by baofeng-tech (@baofeng-tech); the current version is v1.0.2.
More Skills