[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A7CJJQJ8Z0EB3FD6GVXM94":3,"skill-same:01M7A7CJJQJ8Z0EB3FD6GVXM94":60},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":14,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7A7CJJQJ8Z0EB3FD6GVXM94","hermes-tweet",null,"Install and operate Hermes Tweet, a Hermes Agent plugin for X\u002FTwitter research, timeline reading, tweet analysis, and approval-gated private or state-changing operations. Use this skill when installing Hermes Tweet, researching X\u002FTwitter accounts, monitoring launch signals, investigating mentions, auditing giveaways, or preparing gated X operations. Use proactively when a Hermes Agent workflow needs current X\u002FTwitter context. Requires XQUIK_API_KEY for read and action tools.","NeelakshSaxena\u002FVayu","NeelakshSaxena","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F87892838?v=4","01M7A3B9YFS6F6N9DD1787DT86","Neelaksh Saxena","01M7A3B9ZKBT09MNMPX2XN69BY",0,"MIT","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fhermes-tweet\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"Install and operate Hermes Tweet, a Hermes Agent plugin for X\u002FTwitter research, timeline reading, tweet analysis, and approval-gated private or state-changing operations. Use this skill when installing Hermes Tweet, researching X\u002FTwitter accounts, monitoring launch signals, investigating mentions, auditing giveaways, or preparing gated X operations. Use proactively when a Hermes Agent workflow needs current X\u002FTwitter context. Requires XQUIK_API_KEY for read and action tools.\\n\"\nlicense: \"MIT\"\nmetadata: {\"version\":\"0.1.13\",\"source\":\"https:\u002F\u002Fgithub.com\u002FXquik-dev\u002Fhermes-tweet\",\"homepage\":\"https:\u002F\u002Fgithub.com\u002FXquik-dev\u002Fhermes-tweet#readme\"}\n---\n# Hermes Tweet\n\nHermes Tweet adds an X\u002FTwitter toolset to Hermes Agent. It is useful for social\nlistening, account research, launch monitoring, support triage, giveaway audits,\nand controlled workflows where private or state-changing operations stay\nexplicit.\n\n## When to Use This Skill\n\nUse this skill when the user wants to:\n\n- Install Hermes Tweet into a Hermes Agent runtime\n- Discover available X\u002FTwitter read and action routes\n- Read X\u002FTwitter account, tweet, trend, monitor, or search data\n- Summarize public signal before drafting responses or campaigns\n- Keep private and state-changing operations gated behind explicit operator intent\n\n## Setup\n\nInstall and enable the plugin through Hermes:\n\n```bash\nhermes plugins install Xquik-dev\u002Fhermes-tweet --enable\n```\n\nHermes scans plugins during installation and updates. Review each warning.\nA dangerous verdict blocks installation or disables an update.\n\nSet the API key on the Hermes runtime host:\n\n```bash\nexport XQUIK_API_KEY=\"\u003Cyour-key>\"\nexport HERMES_TWEET_ENABLE_ACTIONS=\"false\"\n```\n\nKeep `HERMES_TWEET_ENABLE_ACTIONS` false for read-first sessions. Set it to\n`true` only for an approved private read, write, monitor, webhook, extraction,\ndraw, or media operation.\n\n## Inputs\n\nAsk for these inputs before selecting routes:\n\n- Objective: research, monitoring, support triage, giveaway audit, or action prep\n- Target: account handle, tweet URL, keyword, list, monitor, or trend\n- Time window and freshness needs\n- Whether any private or state-changing operation is in scope\n- Confirmation that the Hermes runtime has `XQUIK_API_KEY`\n\n## Workflow\n\n1. Search the bundled endpoint catalog with `tweet_explore` to find matching routes.\n2. Read public X\u002FTwitter data through `tweet_read` after selecting a catalog route.\n3. Use `tweet_action` for private or state-changing routes only after explicit approval.\n4. Keep API keys in environment variables or the Hermes runtime env file.\n5. Do not paste credentials into prompts, issues, PR comments, or tool inputs.\n6. Load [workflow patterns](references\u002Fworkflows.md) when the user asks for a\n   campaign, monitor, support, or giveaway workflow instead of a single read.\n\n## Tool Model\n\n| Tool | Purpose |\n| --- | --- |\n| `tweet_explore` | Search the bundled endpoint catalog without using the API key. |\n| `tweet_read` | Call catalog-listed public read-only endpoints when `XQUIK_API_KEY` is set. |\n| `tweet_action` | Call private reads, writes, monitors, webhooks, extractions, draws, and media operations only when action gating is enabled. |\n\n## Output Format\n\nReturn concise operational output:\n\n```text\nSummary:\n- What was checked and why\n\nRead routes:\n- Catalog path, input, and result summary\n\nAction plan:\n- Proposed private or state-changing operations, each awaiting explicit approval\n\nNext check:\n- Follow-up route or monitoring cadence when useful\n```\n\n## Usage Examples\n\nResearch an account before drafting a reply:\n\n```text\nUse Hermes Tweet to inspect recent public context for @example before drafting a reply.\nKeep actions disabled.\n```\n\nMonitor a launch keyword:\n\n```text\nTrack X\u002FTwitter mentions for \"Example Launch\" today.\nSummarize themes and notable accounts. Do not post.\n```\n\nPrepare a guarded post:\n\n```text\nDraft a launch tweet and list the exact tweet_action call you would use.\nWait for approval before any action route.\n```\n\nCapture structured route notes:\n\n```json\n{\n  \"objective\": \"support-triage\",\n  \"route\": \"\u002Fapi\u002Fv1\u002Fx\u002Fsearch\",\n  \"action_gate\": \"disabled\",\n  \"approval_required\": true\n}\n```\n\n## Troubleshooting\n\n- If only `tweet_explore` appears, configure `XQUIK_API_KEY` on the Hermes runtime\n  host and reload or restart the active Hermes session.\n- If action routes are unavailable, keep public reads separate. Set\n  `HERMES_TWEET_ENABLE_ACTIONS=true` only for an approved private or\n  state-changing operation.\n- If a route does not match, use `tweet_explore` again and choose a catalog-listed\n  path instead of guessing endpoints.\n\n## Best Practices\n\n- Treat Hermes Tweet as the Hermes-native X\u002FTwitter layer, not a generic API wrapper.\n- Keep research read-only by default. Require approval before creating or\n  changing monitors.\n- Use Desktop or gateway operator review before private or state-changing calls.\n- Validate the exact catalog path before calling `tweet_read` or `tweet_action`.\n- Restart gateway, cron, or long-running Hermes sessions after env changes.\n\n## See Also\n\nThe social-publishing plugin complements Hermes Tweet for broad multi-platform\npublishing. Hermes Tweet is focused on the Hermes Agent X\u002FTwitter toolset and its\nread-first, approval-gated operating model.\n\nSee [the endpoint and approval contract](references\u002Fendpoint-contract.md) when a\nroute boundary is unclear. See the official guide at\nhttps:\u002F\u002Fgithub.com\u002FXquik-dev\u002Fhermes-tweet#readme.\n","# Hermes Tweet\n\nHermes Tweet adds an X\u002FTwitter toolset to Hermes Agent. It is useful for social\nlistening, account research, launch monitoring, support triage, giveaway audits,\nand controlled workflows where private or state-changing operations stay\nexplicit.\n\n## When to Use This Skill\n\nUse this skill when the user wants to:\n\n- Install Hermes Tweet into a Hermes Agent runtime\n- Discover available X\u002FTwitter read and action routes\n- Read X\u002FTwitter account, tweet, trend, monitor, or search data\n- Summarize public signal before drafting responses or campaigns\n- Keep private and state-changing operations gated behind explicit operator intent\n\n## Setup\n\nInstall and enable the plugin through Hermes:\n\n```bash\nhermes plugins install Xquik-dev\u002Fhermes-tweet --enable\n```\n\nHermes scans plugins during installation and updates. Review each warning.\nA dangerous verdict blocks installation or disables an update.\n\nSet the API key on the Hermes runtime host:\n\n```bash\nexport XQUIK_API_KEY=\"\u003Cyour-key>\"\nexport HERMES_TWEET_ENABLE_ACTIONS=\"false\"\n```\n\nKeep `HERMES_TWEET_ENABLE_ACTIONS` false for read-first sessions. Set it to\n`true` only for an approved private read, write, monitor, webhook, extraction,\ndraw, or media operation.\n\n## Inputs\n\nAsk for these inputs before selecting routes:\n\n- Objective: research, monitoring, support triage, giveaway audit, or action prep\n- Target: account handle, tweet URL, keyword, list, monitor, or trend\n- Time window and freshness needs\n- Whether any private or state-changing operation is in scope\n- Confirmation that the Hermes runtime has `XQUIK_API_KEY`\n\n## Workflow\n\n1. Search the bundled endpoint catalog with `tweet_explore` to find matching routes.\n2. Read public X\u002FTwitter data through `tweet_read` after selecting a catalog route.\n3. Use `tweet_action` for private or state-changing routes only after explicit approval.\n4. Keep API keys in environment variables or the Hermes runtime env file.\n5. Do not paste credentials into prompts, issues, PR comments, or tool inputs.\n6. Load [workflow patterns](references\u002Fworkflows.md) when the user asks for a\n   campaign, monitor, support, or giveaway workflow instead of a single read.\n\n## Tool Model\n\n| Tool | Purpose |\n| --- | --- |\n| `tweet_explore` | Search the bundled endpoint catalog without using the API key. |\n| `tweet_read` | Call catalog-listed public read-only endpoints when `XQUIK_API_KEY` is set. |\n| `tweet_action` | Call private reads, writes, monitors, webhooks, extractions, draws, and media operations only when action gating is enabled. |\n\n## Output Format\n\nReturn concise operational output:\n\n```text\nSummary:\n- What was checked and why\n\nRead routes:\n- Catalog path, input, and result summary\n\nAction plan:\n- Proposed private or state-changing operations, each awaiting explicit approval\n\nNext check:\n- Follow-up route or monitoring cadence when useful\n```\n\n## Usage Examples\n\nResearch an account before drafting a reply:\n\n```text\nUse Hermes Tweet to inspect recent public context for @example before drafting a reply.\nKeep actions disabled.\n```\n\nMonitor a launch keyword:\n\n```text\nTrack X\u002FTwitter mentions for \"Example Launch\" today.\nSummarize themes and notable accounts. Do not post.\n```\n\nPrepare a guarded post:\n\n```text\nDraft a launch tweet and list the exact tweet_action call you would use.\nWait for approval before any action route.\n```\n\nCapture structured route notes:\n\n```json\n{\n  \"objective\": \"support-triage\",\n  \"route\": \"\u002Fapi\u002Fv1\u002Fx\u002Fsearch\",\n  \"action_gate\": \"disabled\",\n  \"approval_required\": true\n}\n```\n\n## Troubleshooting\n\n- If only `tweet_explore` appears, configure `XQUIK_API_KEY` on the Hermes runtime\n  host and reload or restart the active Hermes session.\n- If action routes are unavailable, keep public reads separate. Set\n  `HERMES_TWEET_ENABLE_ACTIONS=true` only for an approved private or\n  state-changing operation.\n- If a route does not match, use `tweet_explore` again and choose a catalog-listed\n  path instead of guessing endpoints.\n\n## Best Practices\n\n- Treat Hermes Tweet as the Hermes-native X\u002FTwitter layer, not a generic API wrapper.\n- Keep research read-only by default. Require approval before creating or\n  changing monitors.\n- Use Desktop or gateway operator review before private or state-changing calls.\n- Validate the exact catalog path before calling `tweet_read` or `tweet_action`.\n- Restart gateway, cron, or long-running Hermes sessions after env changes.\n\n## See Also\n\nThe social-publishing plugin complements Hermes Tweet for broad multi-platform\npublishing. Hermes Tweet is focused on the Hermes Agent X\u002FTwitter toolset and its\nread-first, approval-gated operating model.\n\nSee [the endpoint and approval contract](references\u002Fendpoint-contract.md) when a\nroute boundary is unclear. See the official guide at\nhttps:\u002F\u002Fgithub.com\u002FXquik-dev\u002Fhermes-tweet#readme.\n",{"license":15,"metadata":24,"description":28},{"source":25,"version":26,"homepage":27},"https:\u002F\u002Fgithub.com\u002FXquik-dev\u002Fhermes-tweet","0.1.13","https:\u002F\u002Fgithub.com\u002FXquik-dev\u002Fhermes-tweet#readme","Install and operate Hermes Tweet, a Hermes Agent plugin for X\u002FTwitter research, timeline reading, tweet analysis, and approval-gated private or state-changing operations. Use this skill when installing Hermes Tweet, researching X\u002FTwitter accounts, monitoring launch signals, investigating mentions, auditing giveaways, or preparing gated X operations. Use proactively when a Hermes Agent workflow needs current X\u002FTwitter context. Requires XQUIK_API_KEY for read and action tools.\n","main","7540bbccf0c1ded6156a467b02c95b61ad62413f",".agents\u002Fskills\u002Fhermes-tweet","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena","Currently exploring the intersection of tech","2026-09-11 03:02:31",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add NeelakshSaxena\u002FVayu --skill hermes-tweet",{"tool":42,"command":43},"bunx","bunx skills add NeelakshSaxena\u002FVayu --skill hermes-tweet",{"tool":45,"command":46},"pnpm","pnpm dlx skills add NeelakshSaxena\u002FVayu --skill hermes-tweet","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fhermes-tweet\u002FSKILL.md",true,[50,56],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fendpoint-contract.md","REFERENCE","参考文档",1631,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fhermes-tweet\u002Freferences\u002Fendpoint-contract.md",{"path":57,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fworkflows.md",1393,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fhermes-tweet\u002Freferences\u002Fworkflows.md",[61,69,76,83,90,97],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":65,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7ACCCVNCFKMA9X6D15X6G98","runpodctl","Runpod CLI for managing GPU\u002FCPU workloads from the terminal — pods, serverless endpoints, templates, network volumes, Hub deploys, models, SSH, and file transfer (send\u002Freceive). Use for terminal\u002FCI\u002Fscripting, Hub browse\u002Fdeploy, SSH setup, `doctor`, or when the Runpod MCP tools are not connected. For structured tool calls in an MCP-enabled session, prefer runpod-mcp.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpodctl\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":65,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7ACC63SRHEA5KMCHSMZK2TC","runpod","Start here for any Runpod task — running GPU\u002FCPU pods, deploying serverless endpoints, templates, network volumes, building images, or understanding how Runpod works. Routes to the right skill (runpod-mcp, runpodctl, flash, companion-clis, runpod-usage, runpod-templates, runpod-migrate) and indexes two dozen live-verified end-to-end examples (golden paths) — use it when the lane is unclear, and for any multi-step or provisioning task even when it is not.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":65,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7ACC0Q1C89N9BZBV91CTQTF","runpod-usage","How Runpod works and how to work it — pods vs serverless, GPU\u002FVRAM selection, storage, building a container, networking, plus the agentic pod development loop (provision → ssh-exec → set up → poll readiness) and on-pod install hygiene (uv\u002Fapt). Use to answer \"how does X work\", \"which GPU\", \"how do I build a container\", or \"how do I stand up a workload on a pod\". Guidance, not a tool — execute with runpodctl, runpod-mcp, or flash.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-usage\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":65,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7ACBRPE345GF5GM5B8P8RRC","runpod-templates","Runpod's official prebuilt pod templates (ComfyUI, PyTorch, and others): what each image ships, which ports and paths it uses, how to pick one, how to pin a version, and what is missing on first boot. Use when a task says \"run \u003CX> on a pod\" and an official template already covers it, instead of building an image — and when a user needs help with or wants to fix something about a Runpod template they are already running (won't boot, can't reach the UI, missing models, wrong CUDA line, broken ComfyUI workflow metadata on imported workflows): start here and route onward. Deploy with runpodctl or runpod-mcp; end-to-end walkthroughs live in the runpod router's golden paths.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-templates\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":65,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M7ACBJATHKVX1TWES2F44GY8","runpod-migrate","Migrate a codebase from the Runpod GraphQL API or REST v1 to REST v2 — inventory which parts use which API version, rewrite the call sites, flag breaking changes, and verify. Use when someone asks to move to v2, asks what v2 would change, or asks which Runpod API their code is on. For managing infrastructure rather than migrating code, use runpod-mcp or runpodctl.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-migrate\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":65,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M7ACBC7GHVH6T9YEAPCG2AP8","runpod-mcp","Manage Runpod infrastructure — pods, serverless endpoints, jobs, templates, network volumes, container-registry auth, GPU\u002FCPU catalog, and billing — via the Runpod MCP server's structured tool calls. Use when the Runpod MCP tools (create-pod, list-endpoints, …) are connected in this session, or to connect them (hosted OAuth or local npx). Prefer this over runpodctl for plain infra CRUD when MCP is available; use runpodctl for the terminal, file transfer, or SSH setup.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-mcp\u002FSKILL.md",[],[]]