agentleFS
maystudiosmaystudios/claude-skills/hermes-tweet/SKILL.md

hermes-tweet

Skill21 starsChanged 7 months agoMITView on GitHub

Use Hermes Tweet with Hermes Agent for X/Twitter endpoint discovery, public reads, private action-gated reads, audience analysis, thread planning, and guarded publishing. Use when a project needs Hermes-native social research or publishing workflows.

  • Reads credentials

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use tweet_explore to find the endpoint that matches the user's request.

    line 37
  2. Very specific:

    Use tweet_read for public timelines, profile reads, search, or analytics.

    line 38
  3. Very specific:

    Use tweet_action for connected-account state, private GET endpoints, action-marked endpoints, or publishing after clear user approval.

    line 39
  4. Distinctive:

    Keep all publishing actions explicit and reviewable.

    line 45
  5. Distinctive:

    Treat private account state as sensitive context.

    line 46
  6. Very specific:

    Do not enable tweet_action for unattended projects.

    line 47
  7. Distinctive:

    Do not store API keys, account data, or drafts in the repository.

    line 48

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

Hermes Tweet

Hermes Tweet is a Hermes Agent plugin for X/Twitter workflows. It keeps endpoint discovery separate from reads and requires explicit configuration before account data or publishing actions are available.

Install

hermes plugins install Xquik-dev/hermes-tweet --enable

Set XQUIK_API_KEY before using read or action tools. Set HERMES_TWEET_ENABLE_ACTIONS=true only for projects where publishing actions are intentionally enabled.

Tool Routes

  • tweet_explore: discover the bundled X/Twitter endpoint catalog without network access.
  • tweet_read: read public, read-only X/Twitter data from a cataloged GET endpoint when XQUIK_API_KEY is configured.
  • tweet_action: run private or action-marked GET endpoints, draft, schedule, or publish only when XQUIK_API_KEY is configured and HERMES_TWEET_ENABLE_ACTIONS=true.

Workflow

  1. Use tweet_explore to find the endpoint that matches the user's request.
  2. Use tweet_read for public timelines, profile reads, search, or analytics.
  3. Use tweet_action for connected-account state, private GET endpoints, action-marked endpoints, or publishing after clear user approval.
  4. Report what was read or drafted without exposing private account state.

Safety

  • Keep all publishing actions explicit and reviewable.
  • Treat private account state as sensitive context.
  • Do not enable tweet_action for unattended projects.
  • Do not store API keys, account data, or drafts in the repository.

Links

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.