agentleFS
Sign inStart free
QuixiAIQuixiAI/Hexis/skills/installed/twitter-x-actions/SKILL.md

twitter-x-actions

Skill623 starsChanged 10 months agoMITView on GitHub

Create Twitter/X posts, reply to posts, and send DMs with explicit action authorization

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this only after Twitter/X is connected and the user asks for an outward X action: post, reply, or send a DM.

    line 13
  2. Distinctive:

    Keep posts and replies short, literal, and aligned with the user's stated intent.

    line 20

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

Twitter/X Actions

Use this only after Twitter/X is connected and the user asks for an outward X action: post, reply, or send a DM.

Principles

  • A connected X account is not permission to act. Posting is public and effectively irreversible once seen — hold outward X actions to at least the outreach bar: new, wanted, timely.
  • One-off chat actions still need a clear user request in the current conversation.
  • Heartbeat actions require a matching DB-owned connector action policy; if none exists, do not improvise. Use connector-action-authorization to establish one.
  • Keep posts and replies short, literal, and aligned with the user's stated intent. Do not escalate a narrow request ("reply to this thread") into broader posting.
  • Personal matters belong in DMs, never public posts.

Flow

  1. For a new post, call twitter_x_post with the exact text the user approved.
  2. For a reply, call twitter_x_reply with reply_to_tweet_id and the text.
  3. For a direct message, call twitter_x_dm_send with the participant_id and text.
  4. Report what was posted or sent, quoting the final text.

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