什么是 T@witter 指挥中心（搜索 + 坚控）？

T@witter 指挥中心是一款高性能技能，旨在弥合自主智能体与 X (T@witter) 生态系统之间的差距。通过利用 Openclaw Skills，开发者可以赋能其智能体执行实时社交、追踪新兴趋势并轻松收集竞争情报。该技能基于 AIsa API 构建，提供了一种简化的方式来访问公开数据，而无需面对官方 API 速率限制或复杂配置的困扰。

该技能被划分为安全的读取操作和高风险的写入操作。大多数用户会发现只读功能具有巨大价值，它可以进行个人资料分析、粉丝追踪和高级关键词搜索，且无需 T@witter 登录凭据。对于那些构建自动互动机器人的用户，该技能还支持通过集成在 Openclaw Skills 中的安全代理工作流进行发帖和点攒等身份验证操作。

下载入口:https://github.com/openclaw/skills/tree/main/skills/renning22/asia-twitter-api-v1

安装与下载

1. ClawHub CLI

从源直接安装技能的最快方式。

2. 手动安装

将技能文件夹复制到以下位置之一

优先级：工作区 > 本地 > 内置

3. 提示词安装

将此提示词复制到 OpenClaw 即可自动安装。

T@witter 指挥中心（搜索 + 坚控） 应用场景

• 追踪行业领袖的实时 AI 和技术公告，保持您的知识库更新。
• 坚控全球或地区趋势话题，识别病毒式传播机会或市场转变。
• 执行高级关键词搜索，分析品牌情绪和客户反馈。
• 深入研究用户资料和粉丝网络，进行影响者图谱绘制。
• 通过专用自动化账户自动回复或分发内容，用于社交媒体管理。

1. AI 智能体或用户提供 AIsa API 密钥，作为所有 Openclaw Skills 请求的主要授权。
2. 对于只读任务，智能体向特定端点（如用户信息、搜索或趋势）发送 GET 请求。
3. AIsa 后端从 X 获取实时数据，并返回包含所请求社交情报的结构化 JSON 响应。
4. 对于基于写入的交互，智能体使用电子邮件、密码和代理启动异步登录流程。
5. 身份验证后，智能体可以执行发布推文或转发等有状态操作，所有费用按请求追踪。

T@witter 指挥中心（搜索 + 坚控） 配置指南

要开始在 Openclaw Skills 框架内使用此技能，请遵循以下步骤：

1. 从 aisa.one 获取 API 密钥。
2. 在终端中设置环境变量：

export AISA_API_KEY="your-key-here"

3. 通过简单的个人资料查询测试连接：

curl "https://api.aisa.one/apis/v1/twitter/user/info?userName=elonmusk" r
  -H "Authorization: Bearer $AISA_API_KEY"

T@witter 指挥中心（搜索 + 坚控） 数据架构与分类体系

该技能将数据组织成适合智能体处理的结构化 JSON 对象。关键数据点包括：

name: T@witter Command Center (Search + Monitor)
description: "Search X (T@witter) in real time, monitor trends, extract posts, and analyze social media data—perfect for social listening and intelligence gathering. Safe read-only operations by default."
homepage: https://openclaw.ai
metadata: {"openclaw":{"emoji":"??","requires":{"bins":["curl","python3"],"env":["AISA_API_KEY"]},"primaryEnv":"AISA_API_KEY"}}

OpenClaw T@witter ??

T@witter/X data access and automation for autonomous agents. Powered by AIsa.

One API key. Full T@witter intelligence.

?? IMPORTANT SECURITY NOTICE

This skill provides two types of operations:

? Read Operations (SAFE - Recommended for Most Users)

• User profiles, tweets, search, trends, followers
• No authentication required
• No credentials transmitted
• Safe for production use

?? Write Operations (HIGH RISK - Use Only with Dedicated Accounts)

• Posting, liking, retweeting
• Requires transmitting email + password + proxy to third-party API
• Security Risk: Full account access granted to api.aisa.one

?? CRITICAL: Never use write operations with your primary T@witter account. Create dedicated automation accounts only.

?? What Can You Do? (Safe Read Operations)

Monitor Influencers

"Get Elon Musk's latest tweets and notify me of any AI-related posts"

Track Trends

"What's trending on T@witter worldwide right now?"

Social Listening

"Search for tweets mentioning our product and analyze sentiment"

Competitor Intelligence

"Monitor @anthropic and @GoogleAI - alert me on new announcements"

User Research

"Find AI researchers in the Bay Area and show their recent work"

Quick Start

export AISA_API_KEY="your-key"

Get your API key at aisa.one

Core Capabilities

? Read Operations (No Login Required - Safe)

All read operations are safe and require only your AIsa API key. No T@witter credentials needed.

Get User Information

curl "https://api.aisa.one/apis/v1/twitter/user/info?userName=elonmusk" r
  -H "Authorization: Bearer $AISA_API_KEY"

Get User's Latest Tweets

curl "https://api.aisa.one/apis/v1/twitter/user/user_last_tweet?userName=elonmusk" r
  -H "Authorization: Bearer $AISA_API_KEY"

Search Tweets (Advanced)

Important: queryType parameter is required (Latest or Top)

# Search latest tweets
curl "https://api.aisa.one/apis/v1/twitter/tweet/advanced_search?query=AI+agents&queryType=Latest" r
  -H "Authorization: Bearer $AISA_API_KEY"

# Search top tweets
curl "https://api.aisa.one/apis/v1/twitter/tweet/advanced_search?query=AI+agents&queryType=Top" r
  -H "Authorization: Bearer $AISA_API_KEY"

Get Trending Topics

# Worldwide trends (woeid=1)
curl "https://api.aisa.one/apis/v1/twitter/trends?woeid=1" r
  -H "Authorization: Bearer $AISA_API_KEY"

Search Users

curl "https://api.aisa.one/apis/v1/twitter/user/search_user?keyword=AI+researcher" r
  -H "Authorization: Bearer $AISA_API_KEY"

Get Tweet Details by ID

curl "https://api.aisa.one/apis/v1/twitter/tweet/tweetById?tweet_ids=123456789" r
  -H "Authorization: Bearer $AISA_API_KEY"

Get User Followers

curl "https://api.aisa.one/apis/v1/twitter/user/user_followers?userName=elonmusk" r
  -H "Authorization: Bearer $AISA_API_KEY"

Get User Followings

curl "https://api.aisa.one/apis/v1/twitter/user/user_followings?userName=elonmusk" r
  -H "Authorization: Bearer $AISA_API_KEY"

?? Write Operations (High Risk - Requires Authentication)

?? CRITICAL SECURITY WARNING

Write operations require you to:

1. Send your T@witter email, password, and proxy credentials to api.aisa.one
2. Trust a third-party service with full account access
3. Accept responsibility for account security

NEVER use these operations with:

• ? Your primary T@witter account
• ? Accounts with sensitive data
• ? Verified or high-value accounts
• ? Accounts you cannot afford to lose

ONLY use with:

• ? Dedicated test/automation accounts
• ? Unique passwords not used elsewhere
• ? Accounts created specifically for this purpose
• ? After reviewing AIsa's security policies

You acknowledge and accept all risks by using write operations.

Write Operations API Reference

?? Warning: All write operations require prior authentication via login endpoint.

Step 1: Account Login (Async Operation)

curl -X POST "https://api.aisa.one/apis/v1/twitter/user_login_v3" r
  -H "Authorization: Bearer $AISA_API_KEY" r
  -H "Content-Type: application/json" r
  -d '{
    "user_name": "test_automation_account",
    "email": "test@example.com",
    "password": "unique_password_here",
    "proxy": "http://user:pass@proxy-ip:port"
  }'

Login is asynchronous - check status after submission.

Step 2: Check Login Status

curl "https://api.aisa.one/apis/v1/twitter/get_my_x_account_detail_v3?user_name=test_automation_account" r
  -H "Authorization: Bearer $AISA_API_KEY"

Post a Tweet

curl -X POST "https://api.aisa.one/apis/v1/twitter/send_tweet_v3" r
  -H "Authorization: Bearer $AISA_API_KEY" r
  -H "Content-Type: application/json" r
  -d '{
    "user_name": "test_automation_account",
    "text": "Hello from OpenClaw!"
  }'

Like a Tweet

curl -X POST "https://api.aisa.one/apis/v1/twitter/like_tweet_v3" r
  -H "Authorization: Bearer $AISA_API_KEY" r
  -H "Content-Type: application/json" r
  -d '{
    "user_name": "test_automation_account",
    "tweet_id": "1234567890"
  }'

Retweet

curl -X POST "https://api.aisa.one/apis/v1/twitter/retweet_v3" r
  -H "Authorization: Bearer $AISA_API_KEY" r
  -H "Content-Type: application/json" r
  -d '{
    "user_name": "test_automation_account",
    "tweet_id": "1234567890"
  }'

Update Profile

curl -X POST "https://api.aisa.one/apis/v1/twitter/update_profile_v3" r
  -H "Authorization: Bearer $AISA_API_KEY" r
  -H "Content-Type: application/json" r
  -d '{
    "user_name": "test_automation_account",
    "name": "New Name",
    "bio": "New bio"
  }'

Python Client

Safe Read Operations

# User operations (safe)
python3 {baseDir}/scripts/twitter_client.py user-info --username elonmusk
python3 {baseDir}/scripts/twitter_client.py tweets --username elonmusk
python3 {baseDir}/scripts/twitter_client.py followers --username elonmusk
python3 {baseDir}/scripts/twitter_client.py followings --username elonmusk

# Search & Discovery (safe)
python3 {baseDir}/scripts/twitter_client.py search --query "AI agents"
python3 {baseDir}/scripts/twitter_client.py user-search --keyword "AI researcher"
python3 {baseDir}/scripts/twitter_client.py trends --woeid 1

?? Write Operations (High Risk)

Only use with dedicated test accounts:

# Login (use test account only!)
python3 {baseDir}/scripts/twitter_client.py login r
  --username test_automation_account r
  --email test@example.com r
  --password unique_password r
  --proxy "http://user:pass@ip:port"

# Check account status
python3 {baseDir}/scripts/twitter_client.py account --username test_automation_account

# Post operations (after login)
python3 {baseDir}/scripts/twitter_client.py post r
  --username test_automation_account r
  --text "Test post"

python3 {baseDir}/scripts/twitter_client.py like r
  --username test_automation_account r
  --tweet-id 1234567890

python3 {baseDir}/scripts/twitter_client.py retweet r
  --username test_automation_account r
  --tweet-id 1234567890

API Endpoints Reference

Read Operations (Safe)

Write Operations (?? High Risk)

Pricing

Every API response includes usage.cost and usage.credits_remaining fields.

Getting Started

Step 1: Get API Key

Sign up at aisa.one and obtain your API key.

Step 2: Add Credits

AIsa uses pay-as-you-go pricing. Add credits to your account.

Step 3: Set Environment Variable

export AISA_API_KEY="your-key-here"

Step 4: Start with Read Operations

Begin with safe read operations to familiarize yourself with the API.

Only proceed to write operations if you have a specific need and dedicated test account.

Security Best Practices

1. Default to read-only - Most use cases don't need write access
2. Separate accounts - Never mix automation with personal accounts
3. Unique credentials - Use unique passwords for automation accounts
4. Environment variables - Never hardcode credentials in scripts
5. Monitor activity - Regularly check your AIsa dashboard
6. Rotate keys - Periodically rotate API keys
7. Minimal permissions - Only use write operations when absolutely necessary
8. Test thoroughly - Always test with test accounts first
9. Review ToS - Understand both T@witter and AIsa terms of service
10. Have a backup plan - Be prepared for account suspension

Documentation

• Full API Reference
• AIsa Security Policies
• OpenClaw Documentation
• ClawHub Package

Support

• API Issues: Contact AIsa support at aisa.one
• Skill Issues: Open issue on GitHub
• Security Concerns: Review AIsa security documentation

Disclaimer

This skill facilitates access to T@witter data through AIsa's API. Write operations require transmitting credentials to a third-party service. Users assume all responsibility and risk. The authors and AIsa are not liable for account suspension, data loss, or security breaches. Use at your own risk.