[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MDSWFGVND1JQY9DETGAFZR":3,"skill-same:01M6MDSWFGVND1JQY9DETGAFZR":127},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":94,"commitSha":95,"skillDirectory":96,"forksCount":97,"repositoryHtmlUrl":98,"repositoryHomepageUrl":99,"ownerHtmlUrl":100,"ownerBlogUrl":101,"ownerDescription":102,"updatedAt":103,"install":104,"resources":116},"01M6MDSWFGVND1JQY9DETGAFZR","hermes-tweet",null,"Use Xquik in Hermes Agent for public X research, monitoring, thread summaries, creator discovery & approved actions. Not affiliated with X Corp. Use when the user requests X data or a named action. Trigger with \"search X\", \"monitor X\", \"post tweet\", or \"X trends\".","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FXquik-dev\u002Fhermes-tweet\u002Fskills\u002Fhermes-tweet\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"hermes tweet","hermes","explore","for","at","project","local","call","search x","read","MCP","discovery","Media","actions","server","monitoring","search","dev","registry","create","2026-11-10 10:12:30",false,"---\nname: hermes-tweet\ndescription: 'Use Xquik in Hermes Agent for public X research, monitoring, thread summaries, creator discovery & approved actions. Not affiliated with X Corp. Use when the user requests X data or a named action. Trigger with \"search X\", \"monitor X\", \"post tweet\", or \"X trends\".'\nallowed-tools:\n  - tweet_explore\n  - tweet_read\n  - tweet_action\nversion: 0.1.16\nauthor: Burak Bayır (@burak-bayir), Xquik\nlicense: MIT\ncompatibility: Requires Hermes Agent plugin support and Xquik API access.\nargument-hint: \"[X task, endpoint, or approved action]\"\nrepo: https:\u002F\u002Fgithub.com\u002FXquik-dev\u002Fhermes-tweet\nhomepage: https:\u002F\u002Fgithub.com\u002FXquik-dev\u002Fhermes-tweet#readme\ncommit: c6ebdd7060965dd16a89e8cc12675ff834b5cc94\nlanguages:\n  - en\ntags:\n  - hermes-agent\n  - xquik\n  - twitter\n  - x\n  - social-media\n  - automation\nmetadata:\n  version: 0.1.16\n  author: Xquik\n  tags:\n    - hermes-agent\n    - xquik\n    - twitter\n    - x\n    - social-media\n    - automation\nrequired_environment_variables:\n  - name: XQUIK_API_KEY\n    prompt: Xquik API key\n    help: Create an API key at https:\u002F\u002Fdashboard.xquik.com\n    required_for: tweet_read, \u002Fxstatus, \u002Fxtrends, and authenticated Xquik API calls\ncapabilities:\n  shell:\n    required: false\n    justification: Optional Hermes CLI checks are used only for installation and registry diagnostics.\n  network:\n    required: true\n    justification: Hermes Tweet tools call Xquik API routes for X\u002FTwitter reads and approved actions.\n  files:\n    required: false\n    justification: Normal use does not require local file reads or writes.\n  environment:\n    required: true\n    variables:\n      - XQUIK_API_KEY\n      - HERMES_TWEET_ENABLE_ACTIONS\n      - HERMES_ENABLE_PROJECT_PLUGINS\n    justification: Runtime configuration controls authenticated reads, gated actions, and trusted project-local plugin loading.\n  mcp:\n    required: false\n    justification: No MCP server access is required.\n  tools:\n    - tweet_explore\n    - tweet_read\n    - tweet_action\n---\n\n# Hermes Tweet\n\n## Overview\n\nDiscover catalog-listed Xquik routes and run authenticated reads without guessed endpoints.\nPrivate or state-changing operations require the action gate and user approval.\nEnable `tweet_action` only after the user approves its endpoint, payload, account, and effects.\n\n## When to use Hermes Tweet\n\nUse this Skill for X\u002FTwitter research, social listening, monitoring, support triage,\ncreator research, giveaway audits, community audits, and controlled publishing.\n\nUse `tweet_explore` first when the user asks for a capability, endpoint, route,\nor Xquik API route. Use `tweet_read` only after a read-only endpoint is known.\nUse `tweet_action` only after the user requests a write, private read, monitor,\nwebhook, extraction job, giveaway draw, or media operation that requires action\npermissions.\n\n## Prerequisites\n\n- Install and enable the plugin with\n  `hermes plugins install Xquik-dev\u002Fhermes-tweet --enable`.\n- Review Hermes security-scan warnings. Dangerous plugins are blocked.\n- Configure `XQUIK_API_KEY` on the Hermes runtime host for authenticated reads.\n  `tweet_explore` remains available without the key or network access.\n- Leave `HERMES_TWEET_ENABLE_ACTIONS` unset or false unless the workflow needs\n  an approved write-like or private operation.\n- For project-local plugins, set `HERMES_ENABLE_PROJECT_PLUGINS=true` only in a\n  trusted repository.\n- Restart a gateway after environment changes and start a new session. Active\n  CLI sessions can use `\u002Freload`.\n\n## Permissions and capabilities\n\n- Use `tweet_explore`, `tweet_read`, and `tweet_action` only through the enabled\n  Hermes Tweet toolset.\n- Network access is limited to catalog-listed Xquik API routes reached by those\n  tools. Do not create direct HTTP fallbacks.\n- Shell access is not part of normal operation. Use Hermes CLI commands only for\n  the install and registry checks listed in Testing.\n- Local file access is not part of normal operation. Do not write reports,\n  credentials, logs, screenshots, or cached API payloads unless the user asks\n  for an explicit export workflow.\n- Environment access is limited to configuration presence checks for\n  `XQUIK_API_KEY`, `HERMES_TWEET_ENABLE_ACTIONS`, and\n  `HERMES_ENABLE_PROJECT_PLUGINS`. Never request or echo their values.\n- MCP access is not required.\n\n## Instructions\n\n1. Confirm the plugin is enabled with `hermes plugins list` and confirm tool\n   registration with `hermes tools list`.\n2. Use `tweet_explore` to find the catalog endpoint and method.\n3. Use `tweet_read` for public read-only endpoints after the API key is\n   configured.\n4. Before `tweet_action`, state the exact endpoint, payload, account, reason,\n   and expected side effects, then get explicit approval.\n5. Verify the tool response. Report policy, authentication, validation, or\n   account errors without retrying through alternate routes.\n\n## Choose a tool\n\n- For endpoint discovery, call `tweet_explore` with a short query.\n- For catalog-listed `GET` routes, call `tweet_read`.\n- For private or write-like routes, require enabled actions and user approval.\n- When `tweet_action` is disabled, explain the environment gate.\n- When `XQUIK_API_KEY` is missing, ask the user to configure it.\n- Never request the key value in chat.\n- When Hermes shows `not enabled`, run `hermes plugins enable hermes-tweet`.\n- Project-local plugins require `HERMES_ENABLE_PROJECT_PLUGINS=true` in trusted\n  repositories.\n- For unattended work, prefer `tweet_read` and keep actions disabled.\n- Remote Desktop profiles run tools on the remote Hermes host.\n- Keep dashboard-managed secrets in the runtime environment.\n\n## Safety\n\n- Never ask for or reveal API keys, signing keys, passwords, cookies, or TOTP secrets.\n- Never pass credentials in tool arguments.\n- Use only catalog-listed `\u002Fapi\u002Fv1\u002F...` endpoints.\n- Copied endpoint URLs are accepted only when they resolve to catalog-listed paths.\n- Do not use account connection, re-authentication, API key, billing, credit top-up, or support-ticket endpoints.\n- For posting, deleting, following, DMs, profile changes, monitors, webhooks, extraction jobs, and draws, summarize the action before calling `tweet_action`.\n\n## Known risks and mitigations\n\n- **Broad requests.** Start with `tweet_explore` and prefer `tweet_read`.\n  Require an approved endpoint and payload before `tweet_action`.\n- **Exposed secrets.** Ask only whether environment configuration exists.\n  Never request key values or pass credentials as tool arguments.\n- **Guessed endpoints.** Accept only catalog-listed `\u002Fapi\u002Fv1\u002F...` paths.\n  Never create a direct HTTP fallback.\n- **Account changes.** Keep `HERMES_TWEET_ENABLE_ACTIONS=false` by default.\n  Summarize each account-changing call before approval.\n\n## Output\n\n- Return endpoint choices, result summaries, action previews, and fixes.\n- Use concise Markdown and JSON-like Hermes Tweet payloads.\n- `tweet_explore` does not call the API.\n- `tweet_read` performs authenticated reads.\n- `tweet_action` can change state only after explicit approval.\n\n## Error handling\n\nUse the narrowest recovery step that preserves the read-first and action-gated\ncontract.\n\n- **Missing tool.** Confirm the plugin is enabled. Run `hermes tools list`.\n- **Missing API key.** Configure `XQUIK_API_KEY` on the runtime host without pasting\n  its value into chat, then run `\u002Freload` in an active CLI session or run\n  `hermes gateway restart` and start a new gateway session.\n- **Unknown endpoint.** Call `tweet_explore` again. Never guess paths or create a\n  direct HTTP fallback.\n- **Disabled action.** Keep it blocked unless the user requested it and\n  `HERMES_TWEET_ENABLE_ACTIONS=true` is intentionally configured.\n- **Request failure.** Return the sanitized error and corrective step.\n  Do not retry through another route.\n- **Missing slash command.** Verify registration in an active Hermes session.\n  Prompt text does not prove registration.\n- **Secret in input.** Stop and ask the user to rotate it.\n\n## Examples\n\n**Search tweets.**\n\n```json\n{\"query\":\"tweet search\",\"method\":\"GET\"}\n```\n\nThen call `tweet_read` with this payload.\n\n```json\n{\"path\":\"\u002Fapi\u002Fv1\u002Fx\u002Ftweets\u002Fsearch\",\"query\":{\"q\":\"AI agents\",\"limit\":25}}\n```\n\n**Inspect trends.**\n\nRun `\u002Fxtrends` in an active Hermes session. Use `tweet_explore` when the task\nneeds a catalog endpoint or structured response instead of the slash command.\n\n**Post a tweet.**\n\n```json\n{\"query\":\"post tweet\",\"include_actions\":true}\n```\n\nThen call `tweet_action` with this payload.\n\n```json\n{\"path\":\"\u002Fapi\u002Fv1\u002Fx\u002Ftweets\",\"method\":\"POST\",\"body\":{\"account\":\"@example\",\"text\":\"Hello from Hermes Tweet\"},\"reason\":\"Post the user-approved tweet.\"}\n```\n\n## Testing\n\nRun these checks after you install or upgrade the plugin in Hermes Agent.\n\n1. Run `hermes plugins enable hermes-tweet` unless the install used `--enable`.\n2. Run `hermes plugins list` and confirm the plugin is `enabled`.\n3. Run `hermes tools list` and confirm the `hermes-tweet` toolset is enabled.\n4. Confirm `tweet_explore` is available without `XQUIK_API_KEY`.\n5. Confirm `tweet_read` appears only when `XQUIK_API_KEY` is configured.\n6. Confirm `tweet_action` stays hidden or disabled unless `HERMES_TWEET_ENABLE_ACTIONS=true`.\n\nUse these CLI checks.\n\n```bash\nhermes plugins enable hermes-tweet\nhermes tools list\n```\n\n## Release trust gate\n\nComplete these steps before you present this skill as NVIDIA-verified. Do the\nsame before you call it ready for broad enterprise deployment.\n\n1. Run SkillSpector against the complete skill directory and resolve critical or\n   high findings.\n2. Complete `skill-card.md` with owner, license, use case, deployment\n   geography, risks, references, output shape, and release version.\n3. Include Tier-3 eval data and `BENCHMARK.md` for the reviewed release.\n4. Sign the exact reviewed skill directory and publish `skill.oms.sig`.\n5. Verify the published directory with the expected certificate chain.\n\nDo not claim NVIDIA verification when those release artifacts are absent.\n\n## Resources\n\n- [Endpoint and approval contract](references\u002Fendpoint-contract.md)\n- [Skill card](skill-card.md)\n- [Hermes Tweet repository](https:\u002F\u002Fgithub.com\u002FXquik-dev\u002Fhermes-tweet)\n- [Hermes Agent plugin guide](https:\u002F\u002Fgithub.com\u002FNousResearch\u002Fhermes-agent\u002Fblob\u002Fmain\u002Fwebsite\u002Fdocs\u002Fuser-guide\u002Ffeatures\u002Fplugins.md)\n- [Xquik Hermes Tweet guide](https:\u002F\u002Fdocs.xquik.com\u002Fguides\u002Fhermes-tweet)\n","# Hermes Tweet\n\n## Overview\n\nDiscover catalog-listed Xquik routes and run authenticated reads without guessed endpoints.\nPrivate or state-changing operations require the action gate and user approval.\nEnable `tweet_action` only after the user approves its endpoint, payload, account, and effects.\n\n## When to use Hermes Tweet\n\nUse this Skill for X\u002FTwitter research, social listening, monitoring, support triage,\ncreator research, giveaway audits, community audits, and controlled publishing.\n\nUse `tweet_explore` first when the user asks for a capability, endpoint, route,\nor Xquik API route. Use `tweet_read` only after a read-only endpoint is known.\nUse `tweet_action` only after the user requests a write, private read, monitor,\nwebhook, extraction job, giveaway draw, or media operation that requires action\npermissions.\n\n## Prerequisites\n\n- Install and enable the plugin with\n  `hermes plugins install Xquik-dev\u002Fhermes-tweet --enable`.\n- Review Hermes security-scan warnings. Dangerous plugins are blocked.\n- Configure `XQUIK_API_KEY` on the Hermes runtime host for authenticated reads.\n  `tweet_explore` remains available without the key or network access.\n- Leave `HERMES_TWEET_ENABLE_ACTIONS` unset or false unless the workflow needs\n  an approved write-like or private operation.\n- For project-local plugins, set `HERMES_ENABLE_PROJECT_PLUGINS=true` only in a\n  trusted repository.\n- Restart a gateway after environment changes and start a new session. Active\n  CLI sessions can use `\u002Freload`.\n\n## Permissions and capabilities\n\n- Use `tweet_explore`, `tweet_read`, and `tweet_action` only through the enabled\n  Hermes Tweet toolset.\n- Network access is limited to catalog-listed Xquik API routes reached by those\n  tools. Do not create direct HTTP fallbacks.\n- Shell access is not part of normal operation. Use Hermes CLI commands only for\n  the install and registry checks listed in Testing.\n- Local file access is not part of normal operation. Do not write reports,\n  credentials, logs, screenshots, or cached API payloads unless the user asks\n  for an explicit export workflow.\n- Environment access is limited to configuration presence checks for\n  `XQUIK_API_KEY`, `HERMES_TWEET_ENABLE_ACTIONS`, and\n  `HERMES_ENABLE_PROJECT_PLUGINS`. Never request or echo their values.\n- MCP access is not required.\n\n## Instructions\n\n1. Confirm the plugin is enabled with `hermes plugins list` and confirm tool\n   registration with `hermes tools list`.\n2. Use `tweet_explore` to find the catalog endpoint and method.\n3. Use `tweet_read` for public read-only endpoints after the API key is\n   configured.\n4. Before `tweet_action`, state the exact endpoint, payload, account, reason,\n   and expected side effects, then get explicit approval.\n5. Verify the tool response. Report policy, authentication, validation, or\n   account errors without retrying through alternate routes.\n\n## Choose a tool\n\n- For endpoint discovery, call `tweet_explore` with a short query.\n- For catalog-listed `GET` routes, call `tweet_read`.\n- For private or write-like routes, require enabled actions and user approval.\n- When `tweet_action` is disabled, explain the environment gate.\n- When `XQUIK_API_KEY` is missing, ask the user to configure it.\n- Never request the key value in chat.\n- When Hermes shows `not enabled`, run `hermes plugins enable hermes-tweet`.\n- Project-local plugins require `HERMES_ENABLE_PROJECT_PLUGINS=true` in trusted\n  repositories.\n- For unattended work, prefer `tweet_read` and keep actions disabled.\n- Remote Desktop profiles run tools on the remote Hermes host.\n- Keep dashboard-managed secrets in the runtime environment.\n\n## Safety\n\n- Never ask for or reveal API keys, signing keys, passwords, cookies, or TOTP secrets.\n- Never pass credentials in tool arguments.\n- Use only catalog-listed `\u002Fapi\u002Fv1\u002F...` endpoints.\n- Copied endpoint URLs are accepted only when they resolve to catalog-listed paths.\n- Do not use account connection, re-authentication, API key, billing, credit top-up, or support-ticket endpoints.\n- For posting, deleting, following, DMs, profile changes, monitors, webhooks, extraction jobs, and draws, summarize the action before calling `tweet_action`.\n\n## Known risks and mitigations\n\n- **Broad requests.** Start with `tweet_explore` and prefer `tweet_read`.\n  Require an approved endpoint and payload before `tweet_action`.\n- **Exposed secrets.** Ask only whether environment configuration exists.\n  Never request key values or pass credentials as tool arguments.\n- **Guessed endpoints.** Accept only catalog-listed `\u002Fapi\u002Fv1\u002F...` paths.\n  Never create a direct HTTP fallback.\n- **Account changes.** Keep `HERMES_TWEET_ENABLE_ACTIONS=false` by default.\n  Summarize each account-changing call before approval.\n\n## Output\n\n- Return endpoint choices, result summaries, action previews, and fixes.\n- Use concise Markdown and JSON-like Hermes Tweet payloads.\n- `tweet_explore` does not call the API.\n- `tweet_read` performs authenticated reads.\n- `tweet_action` can change state only after explicit approval.\n\n## Error handling\n\nUse the narrowest recovery step that preserves the read-first and action-gated\ncontract.\n\n- **Missing tool.** Confirm the plugin is enabled. Run `hermes tools list`.\n- **Missing API key.** Configure `XQUIK_API_KEY` on the runtime host without pasting\n  its value into chat, then run `\u002Freload` in an active CLI session or run\n  `hermes gateway restart` and start a new gateway session.\n- **Unknown endpoint.** Call `tweet_explore` again. Never guess paths or create a\n  direct HTTP fallback.\n- **Disabled action.** Keep it blocked unless the user requested it and\n  `HERMES_TWEET_ENABLE_ACTIONS=true` is intentionally configured.\n- **Request failure.** Return the sanitized error and corrective step.\n  Do not retry through another route.\n- **Missing slash command.** Verify registration in an active Hermes session.\n  Prompt text does not prove registration.\n- **Secret in input.** Stop and ask the user to rotate it.\n\n## Examples\n\n**Search tweets.**\n\n```json\n{\"query\":\"tweet search\",\"method\":\"GET\"}\n```\n\nThen call `tweet_read` with this payload.\n\n```json\n{\"path\":\"\u002Fapi\u002Fv1\u002Fx\u002Ftweets\u002Fsearch\",\"query\":{\"q\":\"AI agents\",\"limit\":25}}\n```\n\n**Inspect trends.**\n\nRun `\u002Fxtrends` in an active Hermes session. Use `tweet_explore` when the task\nneeds a catalog endpoint or structured response instead of the slash command.\n\n**Post a tweet.**\n\n```json\n{\"query\":\"post tweet\",\"include_actions\":true}\n```\n\nThen call `tweet_action` with this payload.\n\n```json\n{\"path\":\"\u002Fapi\u002Fv1\u002Fx\u002Ftweets\",\"method\":\"POST\",\"body\":{\"account\":\"@example\",\"text\":\"Hello from Hermes Tweet\"},\"reason\":\"Post the user-approved tweet.\"}\n```\n\n## Testing\n\nRun these checks after you install or upgrade the plugin in Hermes Agent.\n\n1. Run `hermes plugins enable hermes-tweet` unless the install used `--enable`.\n2. Run `hermes plugins list` and confirm the plugin is `enabled`.\n3. Run `hermes tools list` and confirm the `hermes-tweet` toolset is enabled.\n4. Confirm `tweet_explore` is available without `XQUIK_API_KEY`.\n5. Confirm `tweet_read` appears only when `XQUIK_API_KEY` is configured.\n6. Confirm `tweet_action` stays hidden or disabled unless `HERMES_TWEET_ENABLE_ACTIONS=true`.\n\nUse these CLI checks.\n\n```bash\nhermes plugins enable hermes-tweet\nhermes tools list\n```\n\n## Release trust gate\n\nComplete these steps before you present this skill as NVIDIA-verified. Do the\nsame before you call it ready for broad enterprise deployment.\n\n1. Run SkillSpector against the complete skill directory and resolve critical or\n   high findings.\n2. Complete `skill-card.md` with owner, license, use case, deployment\n   geography, risks, references, output shape, and release version.\n3. Include Tier-3 eval data and `BENCHMARK.md` for the reviewed release.\n4. Sign the exact reviewed skill directory and publish `skill.oms.sig`.\n5. Verify the published directory with the expected certificate chain.\n\nDo not claim NVIDIA verification when those release artifacts are absent.\n\n## Resources\n\n- [Endpoint and approval contract](references\u002Fendpoint-contract.md)\n- [Skill card](skill-card.md)\n- [Hermes Tweet repository](https:\u002F\u002Fgithub.com\u002FXquik-dev\u002Fhermes-tweet)\n- [Hermes Agent plugin guide](https:\u002F\u002Fgithub.com\u002FNousResearch\u002Fhermes-agent\u002Fblob\u002Fmain\u002Fwebsite\u002Fdocs\u002Fuser-guide\u002Ffeatures\u002Fplugins.md)\n- [Xquik Hermes Tweet guide](https:\u002F\u002Fdocs.xquik.com\u002Fguides\u002Fhermes-tweet)\n",{"name":5,"repo":49,"tags":50,"author":57,"commit":58,"license":15,"version":59,"homepage":60,"metadata":61,"languages":64,"description":7,"capabilities":66,"allowed-tools":86,"argument-hint":87,"compatibility":88,"required_environment_variables":89},"https:\u002F\u002Fgithub.com\u002FXquik-dev\u002Fhermes-tweet",[51,52,53,54,55,56],"hermes-agent","xquik","twitter","x","social-media","automation","Burak Bayır (@burak-bayir), Xquik","c6ebdd7060965dd16a89e8cc12675ff834b5cc94","0.1.16","https:\u002F\u002Fgithub.com\u002FXquik-dev\u002Fhermes-tweet#readme",{"tags":62,"author":63,"version":59},[51,52,53,54,55,56],"Xquik",[65],"en",{"mcp":67,"files":69,"shell":71,"tools":73,"network":77,"environment":80},{"required":45,"justification":68},"No MCP server access is required.",{"required":45,"justification":70},"Normal use does not require local file reads or writes.",{"required":45,"justification":72},"Optional Hermes CLI checks are used only for installation and registry diagnostics.",[74,75,76],"tweet_explore","tweet_read","tweet_action",{"required":78,"justification":79},true,"Hermes Tweet tools call Xquik API routes for X\u002FTwitter reads and approved actions.",{"required":78,"variables":81,"justification":85},[82,83,84],"XQUIK_API_KEY","HERMES_TWEET_ENABLE_ACTIONS","HERMES_ENABLE_PROJECT_PLUGINS","Runtime configuration controls authenticated reads, gated actions, and trusted project-local plugin loading.",[74,75,76],"[X task, endpoint, or approved action]","Requires Hermes Agent plugin support and Xquik API access.",[90],{"help":91,"name":82,"prompt":92,"required_for":93},"Create an API key at https:\u002F\u002Fdashboard.xquik.com","Xquik API key","tweet_read, \u002Fxstatus, \u002Fxtrends, and authenticated Xquik API calls","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FXquik-dev\u002Fhermes-tweet\u002Fskills\u002Fhermes-tweet",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":105,"prompt":115,"zipAvailable":78},[106,109,112],{"tool":107,"command":108},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill hermes-tweet",{"tool":110,"command":111},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill hermes-tweet",{"tool":113,"command":114},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill hermes-tweet","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FXquik-dev\u002Fhermes-tweet\u002Fskills\u002Fhermes-tweet\u002FSKILL.md",[117,123],{"path":118,"resourceType":119,"resourceTypeDesc":120,"sizeBytes":121,"sourceHtmlUrl":122},"references\u002Fendpoint-contract.md","REFERENCE","参考文档",2655,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FXquik-dev\u002Fhermes-tweet\u002Fskills\u002Fhermes-tweet\u002Freferences\u002Fendpoint-contract.md",{"path":124,"resourceType":119,"resourceTypeDesc":120,"sizeBytes":125,"sourceHtmlUrl":126},"skill-card.md",3737,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FXquik-dev\u002Fhermes-tweet\u002Fskills\u002Fhermes-tweet\u002Fskill-card.md",[128,137,145,153,161,169],{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":132,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":136},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":141,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":136},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":149,"sourceHtmlUrl":150,"categories":151,"keywords":152,"publishedAt":136},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":157,"sourceHtmlUrl":158,"categories":159,"keywords":160,"publishedAt":136},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":165,"sourceHtmlUrl":166,"categories":167,"keywords":168,"publishedAt":136},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":173,"sourceHtmlUrl":174,"categories":175,"keywords":176,"publishedAt":136},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]