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

aisa-twitter-post-engage

Skill0 starsChanged 7 months agoMITView on GitHub

Search X/Twitter profiles, tweets, trends, and approved engagement actions through the AIsa relay. Use when the user asks for Twitter/X research, posting, likes, follows, or related workflows 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

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 5 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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, and approved engagement actions through the AIsa relay.

    line 19
  2. Very specific:

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

    line 47
  3. Distinctive:

    Read user, tweet, trend, list, community, and Spaces data.

    line 51
  4. Very specific:

    Use references/post_twitter.md for post, reply, quote, and media-upload actions.

    line 67
  5. Very specific:

    Use references/engage_twitter.md for likes, unlikes, follows, and unfollows.

    line 68
  6. Distinctive:

    Do not ask for passwords, browser cookies, or undocumented secrets.

    line 73
  7. Distinctive:

    Do not guess target accounts or tweet IDs when multiple candidates exist.

    line 74
  8. Distinctive:

    Do not claim engagement or posting succeeded unless the relay request returns success.

    line 75

≈ “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 Post Engage

Search X/Twitter profiles, tweets, trends, and approved engagement actions 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 environment variable: 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.

Common Commands

python3 scripts/twitter_client.py search --query "AI agents" --type Latest
python3 scripts/twitter_oauth_client.py authorize
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"

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.

Guardrails

  • Do not ask for passwords, browser cookies, or undocumented secrets.
  • Do not guess target accounts or tweet IDs when multiple candidates exist.
  • Do not claim engagement or posting succeeded unless the relay request returns success.

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