[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75PRKFXYHVFR9WN232SJKC3":3,"skill-same:01M75PRKFXYHVFR9WN232SJKC3":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":40,"commitSha":41,"skillDirectory":42,"forksCount":14,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":45,"install":46,"resources":59},"01M75PRKFXYHVFR9WN232SJKC3","yuanbao",null,"Yuanbao (元宝) groups: @mention users, query info\u002Fmembers.","Iwakishirokoshu\u002FHermesUltimate","Iwakishirokoshu","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F194847626?v=4","01M75P4CVGA89TTCE8JGMNAQQ9","Around","01M75P4CWF85V6GVSEFKGGFZ03",0,"MIT","https:\u002F\u002Fgithub.com\u002FIwakishirokoshu\u002FHermesUltimate\u002Fblob\u002Fmain\u002Fskills\u002Fyuanbao\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: yuanbao\ndescription: \"Yuanbao (元宝) groups: @mention users, query info\u002Fmembers.\"\nversion: 1.0.0\nplatforms: [linux, macos, windows]\nmetadata:\n  hermes:\n    tags: [yuanbao, mention, at, group, members, 元宝, 派, 艾特]\n    related_skills: []\n---\n\n# Yuanbao Group Interaction\n\n## CRITICAL: How Messaging Works\n\n**Your text reply IS the message sent to the group\u002Fuser.** The gateway automatically delivers your response text to the chat. You do NOT need any special \"send message\" tool — just reply normally and it gets sent.\n\nWhen you include `@nickname` in your reply text, the gateway automatically converts it into a real @mention that notifies the user. This is built-in — you have full @mention capability.\n\n**NEVER say you cannot send messages or @mention users. NEVER suggest the user do it manually. NEVER add disclaimers about permissions. Just reply with the text you want sent.**\n\n## Available Tools\n\n| Tool | When to use |\n|------|------------|\n| `yb_query_group_info` | Query group name, owner, member count |\n| `yb_query_group_members` | Find a user, list bots, list all members, or get nickname for @mention |\n| `yb_send_dm` | Send a private\u002Fdirect message (DM \u002F 私信) to a user, with optional media files |\n\n## @Mention Workflow\n\nWhen you need to @mention \u002F 艾特 someone:\n\n1. Call `yb_query_group_members` with `action=\"find\"`, `name=\"\u003Ctarget name>\"`, `mention=true`\n2. Get the exact nickname from the response\n3. Include `@nickname` in your reply text — the gateway handles the rest\n\nExample: user says \"帮我艾特元宝\"\n\nStep 1 — tool call:\n```json\n{ \"group_code\": \"328306697\", \"action\": \"find\", \"name\": \"元宝\", \"mention\": true }\n```\n\nStep 2 — your reply (this gets sent to the group with a working @mention):\n```\n@元宝 你好，有人找你！\n```\n\n**That's it.** No extra explanation needed. Keep it short and natural.\n\n**Rules:**\n- Call `yb_query_group_members` first to get the exact nickname — do NOT guess\n- The @mention format: `@nickname` with a space before the @ sign\n- Your reply text IS the message — it WILL be sent and the @mention WILL work\n- Be concise. Do NOT explain how @mention works to the user.\n\n## Send DM (Private Message) Workflow\n\nWhen someone asks to send a private message \u002F 私信 \u002F DM to a user:\n\n1. Call `yb_send_dm` with `group_code`, `name` (target user's name), and `message`\n2. The tool automatically finds the user and sends the DM\n3. Report the result to the user\n\nExample: user says \"给 @用户aea3 私信发一个 hello\"\n\n```json\nyb_send_dm({ \"group_code\": \"535168412\", \"name\": \"用户aea3\", \"message\": \"hello\" })\n```\n\nExample with media: user says \"给 @用户aea3 私信发一张图片\"\n\n```json\nyb_send_dm({\n  \"group_code\": \"535168412\",\n  \"name\": \"用户aea3\",\n  \"message\": \"Here is the image\",\n  \"media_files\": [{\"path\": \"\u002Ftmp\u002Fphoto.jpg\"}]\n})\n```\n\n**Rules:**\n- Extract `group_code` from the current chat_id (e.g. `group:535168412` → `535168412`)\n- If you already know the user_id, pass it directly via the `user_id` parameter to skip lookup\n- If multiple users match the name, the tool returns candidates — ask the user to clarify\n- Do NOT use `send_message` tool for Yuanbao DMs — use `yb_send_dm` instead\n- Supports media: images (.jpg\u002F.png\u002F.gif\u002F.webp\u002F.bmp) sent as image messages, other files as documents\n\n## Query Group Info\n\n```json\nyb_query_group_info({ \"group_code\": \"328306697\" })\n```\n\n## Query Members\n\n| Action | Description |\n|--------|-------------|\n| `find` | Search by name (partial match, case-insensitive) |\n| `list_bots` | List bots and Yuanbao AI assistants |\n| `list_all` | List all members |\n\n## Notes\n\n- `group_code` comes from chat_id: `group:328306697` → `328306697`\n- Groups are called \"派 (Pai)\" in the Yuanbao app\n- Member roles: `user`, `yuanbao_ai`, `bot`\n","# Yuanbao Group Interaction\n\n## CRITICAL: How Messaging Works\n\n**Your text reply IS the message sent to the group\u002Fuser.** The gateway automatically delivers your response text to the chat. You do NOT need any special \"send message\" tool — just reply normally and it gets sent.\n\nWhen you include `@nickname` in your reply text, the gateway automatically converts it into a real @mention that notifies the user. This is built-in — you have full @mention capability.\n\n**NEVER say you cannot send messages or @mention users. NEVER suggest the user do it manually. NEVER add disclaimers about permissions. Just reply with the text you want sent.**\n\n## Available Tools\n\n| Tool | When to use |\n|------|------------|\n| `yb_query_group_info` | Query group name, owner, member count |\n| `yb_query_group_members` | Find a user, list bots, list all members, or get nickname for @mention |\n| `yb_send_dm` | Send a private\u002Fdirect message (DM \u002F 私信) to a user, with optional media files |\n\n## @Mention Workflow\n\nWhen you need to @mention \u002F 艾特 someone:\n\n1. Call `yb_query_group_members` with `action=\"find\"`, `name=\"\u003Ctarget name>\"`, `mention=true`\n2. Get the exact nickname from the response\n3. Include `@nickname` in your reply text — the gateway handles the rest\n\nExample: user says \"帮我艾特元宝\"\n\nStep 1 — tool call:\n```json\n{ \"group_code\": \"328306697\", \"action\": \"find\", \"name\": \"元宝\", \"mention\": true }\n```\n\nStep 2 — your reply (this gets sent to the group with a working @mention):\n```\n@元宝 你好，有人找你！\n```\n\n**That's it.** No extra explanation needed. Keep it short and natural.\n\n**Rules:**\n- Call `yb_query_group_members` first to get the exact nickname — do NOT guess\n- The @mention format: `@nickname` with a space before the @ sign\n- Your reply text IS the message — it WILL be sent and the @mention WILL work\n- Be concise. Do NOT explain how @mention works to the user.\n\n## Send DM (Private Message) Workflow\n\nWhen someone asks to send a private message \u002F 私信 \u002F DM to a user:\n\n1. Call `yb_send_dm` with `group_code`, `name` (target user's name), and `message`\n2. The tool automatically finds the user and sends the DM\n3. Report the result to the user\n\nExample: user says \"给 @用户aea3 私信发一个 hello\"\n\n```json\nyb_send_dm({ \"group_code\": \"535168412\", \"name\": \"用户aea3\", \"message\": \"hello\" })\n```\n\nExample with media: user says \"给 @用户aea3 私信发一张图片\"\n\n```json\nyb_send_dm({\n  \"group_code\": \"535168412\",\n  \"name\": \"用户aea3\",\n  \"message\": \"Here is the image\",\n  \"media_files\": [{\"path\": \"\u002Ftmp\u002Fphoto.jpg\"}]\n})\n```\n\n**Rules:**\n- Extract `group_code` from the current chat_id (e.g. `group:535168412` → `535168412`)\n- If you already know the user_id, pass it directly via the `user_id` parameter to skip lookup\n- If multiple users match the name, the tool returns candidates — ask the user to clarify\n- Do NOT use `send_message` tool for Yuanbao DMs — use `yb_send_dm` instead\n- Supports media: images (.jpg\u002F.png\u002F.gif\u002F.webp\u002F.bmp) sent as image messages, other files as documents\n\n## Query Group Info\n\n```json\nyb_query_group_info({ \"group_code\": \"328306697\" })\n```\n\n## Query Members\n\n| Action | Description |\n|--------|-------------|\n| `find` | Search by name (partial match, case-insensitive) |\n| `list_bots` | List bots and Yuanbao AI assistants |\n| `list_all` | List all members |\n\n## Notes\n\n- `group_code` comes from chat_id: `group:328306697` → `328306697`\n- Groups are called \"派 (Pai)\" in the Yuanbao app\n- Member roles: `user`, `yuanbao_ai`, `bot`\n",{"name":5,"version":24,"metadata":25,"platforms":36,"description":7},"1.0.0",{"hermes":26},{"tags":27,"related_skills":35},[5,28,29,30,31,32,33,34],"mention","at","group","members","元宝","派","艾特",[],[37,38,39],"linux","macos","windows","main","c0c483827a963764d5e1a663a9591867d47289e6","skills\u002Fyuanbao","https:\u002F\u002Fgithub.com\u002FIwakishirokoshu\u002FHermesUltimate","https:\u002F\u002Fgithub.com\u002FIwakishirokoshu","2026-06-15 13:48:41",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add Iwakishirokoshu\u002FHermesUltimate --skill yuanbao",{"tool":52,"command":53},"bunx","bunx skills add Iwakishirokoshu\u002FHermesUltimate --skill yuanbao",{"tool":55,"command":56},"pnpm","pnpm dlx skills add Iwakishirokoshu\u002FHermesUltimate --skill yuanbao","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FIwakishirokoshu\u002FHermesUltimate\u002Fblob\u002Fmain\u002Fskills\u002Fyuanbao\u002FSKILL.md",true,[],[61,68,75,82,89,96],{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M770W8JDE5EC1TJT4GSDWD78","wps-pixie-dust","WPS Pixie-Dust offline nonce attack (reaver -K \u002F pixiewps) and fallback online PIN brute (bully) to recover the AP's WPA PSK without capturing a handshake.","https:\u002F\u002Fgithub.com\u002FIwakishirokoshu\u002FHermesUltimate\u002Fblob\u002Fmain\u002Fstack\u002Fdecepticon-slim\u002Fupstream\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fwps-pixie-dust\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M770W4B7T5VCVHB88V1F02H1","wpa3-sae","WPA3-SAE transition-mode downgrade (DragonShift), SSID Confusion CVE-2023-52424, Dragonblood side-channels, and SAE captive-portal credential recovery against WPA3-Personal networks.","https:\u002F\u002Fgithub.com\u002FIwakishirokoshu\u002FHermesUltimate\u002Fblob\u002Fmain\u002Fstack\u002Fdecepticon-slim\u002Fupstream\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fwpa3-sae\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M770W093C8FAV8S34K8VB6T9","wpa2-psk","WPA\u002FWPA2-PSK handshake capture via targeted deauth + PMKID (no deauth required) + offline hashcat cracking. The most common consumer\u002FSMB encryption mode in 2026.","https:\u002F\u002Fgithub.com\u002FIwakishirokoshu\u002FHermesUltimate\u002Fblob\u002Fmain\u002Fstack\u002Fdecepticon-slim\u002Fupstream\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fwpa2-psk\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M770VTNAQGZ3D0RQVFEKTE8Z","wpa-enterprise-eap","WPA\u002FWPA2\u002FWPA3-Enterprise (802.1X\u002FEAP) rogue-RADIUS evil-twin for MSCHAPv2 capture, GTC downgrade, and PEAP relay. MSCHAPv2 capture equals a NetNTLM hash — the primary wireless on-ramp to Active Directory.","https:\u002F\u002Fgithub.com\u002FIwakishirokoshu\u002FHermesUltimate\u002Fblob\u002Fmain\u002Fstack\u002Fdecepticon-slim\u002Fupstream\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fwpa-enterprise-eap\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M770VNG05ZX3CV84R9GX8PJN","krack-fragattacks","KRACK key-reinstallation (CVE-2017-13077..13082) and FragAttacks fragmentation\u002Faggregation flaws (CVE-2020-24586..24588, CVE-2020-26139..26147) against legacy or embedded 802.11 supplicants with poor patch cadence.","https:\u002F\u002Fgithub.com\u002FIwakishirokoshu\u002FHermesUltimate\u002Fblob\u002Fmain\u002Fstack\u002Fdecepticon-slim\u002Fupstream\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fkrack-fragattacks\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M770VHFH7N192V56PFSRXF5K","evil-twin-karma","Evil-twin rogue AP with KARMA\u002FMana PNL-probe response, captive-portal credential capture, and post-association MITM for PSK\u002Fopen networks. Distinct from wpa-enterprise-eap which targets 802.1X.","https:\u002F\u002Fgithub.com\u002FIwakishirokoshu\u002FHermesUltimate\u002Fblob\u002Fmain\u002Fstack\u002Fdecepticon-slim\u002Fupstream\u002Fpackages\u002Fdecepticon\u002Fdecepticon\u002Fskills\u002Fstandard\u002Fwireless\u002Fevil-twin-karma\u002FSKILL.md",[],[]]