agentleFS
Sign inStart free
baofeng-techbaofeng-tech/agent-skills-so/aisa-twitter-command-center/SKILL.md

aisa-twitter-command-center

Skill0 starsChanged 7 months agoMITView on GitHub

Search X/Twitter profiles, tweets, trends, lists, communities, and Spaces through the AIsa relay, then support approved posting workflows with OAuth. Use when the user asks for Twitter research, monitoring, or posting without sharing passwords.

  • Reads credentials

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. About 0 are common, 11 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈11

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Search X/Twitter profiles, tweets, trends, lists, communities, and Spaces through the AIsa relay, then support approved posting workflows …

    line 19
  2. Very specific:

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

    line 46
  3. Distinctive:

    Read user data, timelines, mentions, followers, followings, and related profile information.

    line 50
  4. Distinctive:

    Search tweets and users, inspect replies, quotes, retweeters, thread context, trends, lists, communities, and Spaces.

    line 51
  5. Distinctive:

    When the user asks to send, publish, reply, or quote on X/Twitter:

    line 68
  6. Very specific:

    Check whether AISA_API_KEY is configured.

    line 70
  7. Distinctive:

    If the user intent is to publish, attempt the publish workflow.

    line 71
  8. Distinctive:

    If authorization has not been completed, return the OAuth authorization link first.

    line 72
  9. Very specific:

    Use --media-file only for user-provided local workspace files.

    line 73
  10. Distinctive:

    Do not claim the post succeeded until the publish command actually succeeds.

    line 74
  11. Distinctive:

    Do not ask for Twitter passwords or browser cookies.

    line 78
  12. Distinctive:

    Do not invent captions, tweet URLs, or attachment files.

    line 79
  13. Distinctive:

    Do not default to browser opening unless the user explicitly wants local browser launch.

    line 80
  14. Distinctive:

    Do not claim external posting succeeded until the API confirms success.

    line 81

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

AIsa Twitter Command Center

Search X/Twitter profiles, tweets, trends, lists, communities, and Spaces through the AIsa relay, then support approved posting workflows with OAuth.

When to use

  • The user wants Twitter/X research, monitoring, or content discovery.
  • The user wants to inspect profiles, timelines, mentions, trends, replies, quotes, lists, communities, or Spaces.
  • The user wants to draft or publish posts after explicit OAuth approval without sharing passwords.

When NOT to use

  • The user needs password-based login, cookie extraction, or browser credential scraping.
  • The workflow must avoid relay-based calls to api.aisa.one.
  • The request is for unsupported engagement actions not covered by this package.

Quick Reference

  • Required environment variable: AISA_API_KEY
  • Read client: scripts/twitter_client.py
  • OAuth and posting client: scripts/twitter_oauth_client.py
  • Posting guide: references/post_twitter.md

Setup

export AISA_API_KEY="your-key"

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

Capabilities

  • Read user data, timelines, mentions, followers, followings, and related profile information.
  • Search tweets and users, inspect replies, quotes, retweeters, thread context, trends, lists, communities, and Spaces.
  • Publish text, image, and video posts after explicit OAuth approval.
  • Return an authorization link when posting access has not been approved yet.

Common Commands

python3 scripts/twitter_client.py user-info --username elonmusk
python3 scripts/twitter_client.py search --query "AI agents" --type Latest
python3 scripts/twitter_client.py trends --woeid 1
python3 scripts/twitter_oauth_client.py status
python3 scripts/twitter_oauth_client.py authorize
python3 scripts/twitter_oauth_client.py post --text "Hello from AIsa"

Posting Workflow

When the user asks to send, publish, reply, or quote on X/Twitter:

  1. Check whether AISA_API_KEY is configured.
  2. If the user intent is to publish, attempt the publish workflow.
  3. If authorization has not been completed, return the OAuth authorization link first.
  4. Use --media-file only for user-provided local workspace files.
  5. Do not claim the post succeeded until the publish command actually succeeds.

Guardrails

  • Do not ask for Twitter passwords or browser cookies.
  • Do not invent captions, tweet URLs, or attachment files.
  • Do not default to browser opening unless the user explicitly wants local browser launch.
  • Do not claim external posting succeeded until the API confirms success.

Security Notes

  • The workflow is relay-based and sends API requests, OAuth requests, and approved media uploads to api.aisa.one.
  • Required secret: AISA_API_KEY.
  • This workflow does not require passwords, browser cookie extraction, or direct account credential sharing.

References

  • See references/post_twitter.md for detailed posting examples and OAuth guidance.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free