From ea1cc5b1d8c60806a555f02d64cca65eb7e86148 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Burak=20Bay=C4=B1r?= <burakbayir1@gmail.com>
Date: Mon, 29 Jun 2026 11:16:19 +0300
Subject: [PATCH] Add Hermes Tweet agent skill

Signed-off-by: kriptoburak <kriptoburak@users.noreply.github.com>
---
 hermes-tweet/SKILL.md | 78 +++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 78 insertions(+)
 create mode 100644 hermes-tweet/SKILL.md

diff --git a/hermes-tweet/SKILL.md b/hermes-tweet/SKILL.md
new file mode 100644
index 0000000..68064ec
--- /dev/null
+++ b/hermes-tweet/SKILL.md
@@ -0,0 +1,78 @@
+---
+name: hermes-tweet
+description: Use Hermes Tweet from Hermes Agent for read-first X/Twitter workflows and approval-gated actions
+author: Xquik-dev
+version: "1.0"
+tags:
+  - hermes
+  - x
+  - twitter
+  - social
+  - automation
+---
+
+# Hermes Tweet
+
+## Purpose
+
+Use this skill when a Hermes Agent session needs X/Twitter search, account
+reads, trend checks, support triage, launch monitoring, or controlled publishing
+through the Hermes Tweet plugin.
+
+Source package: <https://github.com/Xquik-dev/hermes-tweet>
+
+## Preconditions
+
+- Hermes Agent is installed.
+- Hermes Tweet is installed and enabled:
+  `hermes plugins install Xquik-dev/hermes-tweet --enable`
+- `XQUIK_API_KEY` is configured only where the Hermes runtime executes plugin
+  tools, such as the runtime environment or `~/.hermes/.env`.
+- `HERMES_TWEET_ENABLE_ACTIONS=true` is set only for sessions where the user has
+  explicitly requested write-like actions.
+
+## Tool Boundaries
+
+- Use `tweet_explore` first to discover supported endpoints. It does not need
+  `XQUIK_API_KEY`.
+- Use `tweet_read` only for catalog-listed read-only endpoints.
+- Use `tweet_action` only for writes, private reads, monitors, webhooks,
+  extraction jobs, or draws after the user approves the exact action.
+- If `tweet_action` is unavailable, keep the workflow read-only instead of
+  inventing a fallback.
+
+## Workflow
+
+1. Restate the X/Twitter task and identify whether it is read-only or
+   write-like.
+2. Call `tweet_explore` with a short capability or endpoint query.
+3. Choose only endpoints returned by the catalog.
+4. Call `tweet_read` for public, read-only work.
+5. For posting, replies, likes, follows, DMs, monitors, webhooks, extraction
+   jobs, or draws, show the endpoint and payload first.
+6. Call `tweet_action` only after the user approves that exact endpoint and
+   payload.
+7. Summarize the result, including whether the task stayed read-only or used an
+   approved action.
+
+## Safety Rules
+
+- Do not pass credentials, cookies, tokens, or account secrets as tool
+  arguments.
+- Do not guess endpoint paths. Use the catalog from `tweet_explore`.
+- Do not treat plugin installation as action authorization.
+- Do not enable action mode for monitoring, support triage, trend reads, or
+  account reads unless the user explicitly asks for a write-like operation.
+- In Hermes Desktop with a remote gateway profile, configure Hermes Tweet on the
+  remote Hermes host because that is where plugin tools run.
+
+## Verification
+
+After installation or upgrade:
+
+- [ ] `hermes plugins list` shows `hermes-tweet` installed and enabled.
+- [ ] `tweet_explore` is available without `XQUIK_API_KEY`.
+- [ ] `tweet_read` appears after `XQUIK_API_KEY` is configured and Hermes is
+      reloaded or restarted.
+- [ ] `tweet_action` stays hidden or disabled unless
+      `HERMES_TWEET_ENABLE_ACTIONS=true`.