[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75PDDJTSTD4X0YPATGSPBEB":3,"skill-same:01M75PDDJTSTD4X0YPATGSPBEB":79},{"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":49,"commitSha":50,"skillDirectory":51,"forksCount":14,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":54,"install":55,"resources":68},"01M75PDDJTSTD4X0YPATGSPBEB","here.now",null,"Publish static sites to {slug}.here.now and store private files in cloud Drives for agent-to-agent handoff.","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\u002Foptional-skills\u002Fproductivity\u002Fhere-now\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: here.now\ndescription: Publish static sites to {slug}.here.now and store private files in cloud Drives for agent-to-agent handoff.\nversion: 1.15.3\nauthor: here.now\nlicense: MIT\nprerequisites:\n  commands: [curl, file, jq]\nplatforms: [macos, linux]\nmetadata:\n  hermes:\n    tags: [here.now, herenow, publish, deploy, hosting, static-site, web, share, URL, drive, storage]\n    homepage: https:\u002F\u002Fhere.now\n    requires_toolsets: [terminal]\n---\n\n# here.now\n\nhere.now lets agents publish websites and store private files in cloud Drives.\n\nUse here.now for two jobs:\n\n- **Sites**: publish websites and files at `{slug}.here.now`.\n- **Drives**: store private agent files in cloud folders.\n\n## Current docs\n\n**Before answering questions about here.now capabilities, features, or workflows, read the current docs:**\n\n→ **https:\u002F\u002Fhere.now\u002Fdocs**\n\nRead the docs:\n\n- at the first here.now-related interaction in a conversation\n- any time the user asks how to do something\n- any time the user asks what is possible, supported, or recommended\n- before telling the user a feature is unsupported\n\nTopics that require current docs (do not rely on local skill text alone):\n\n- Drives and Drive sharing\n- custom domains\n- payments and payment gating\n- forking\n- proxy routes and service variables\n- handles and links\n- limits and quotas\n- SPA routing\n- error handling and remediation\n- feature availability\n\n**If docs and live API behavior disagree, trust the live API behavior.**\n\nIf the docs fetch fails or times out, continue with the local skill and live API\u002Fscript output. Prefer live API behavior for active operations.\n\n## Requirements\n\n- Required binaries: `curl`, `file`, `jq`\n- Optional environment variable: `$HERENOW_API_KEY`\n- Optional Drive token variable: `$HERENOW_DRIVE_TOKEN`\n- Optional credentials file: `~\u002F.herenow\u002Fcredentials`\n- Skill helper paths:\n  - `${HERMES_SKILL_DIR}\u002Fscripts\u002Fpublish.sh` for publishing sites\n  - `${HERMES_SKILL_DIR}\u002Fscripts\u002Fdrive.sh` for private Drive storage\n\n## Create a site\n\n```bash\nPUBLISH=\"${HERMES_SKILL_DIR}\u002Fscripts\u002Fpublish.sh\"\nbash \"$PUBLISH\" {file-or-dir} --client hermes\n```\n\nOutputs the live URL (e.g. `https:\u002F\u002Fbright-canvas-a7k2.here.now\u002F`).\n\nUnder the hood this is a three-step flow: create\u002Fupdate -> upload files -> finalize. A site is not live until finalize succeeds.\n\nWithout an API key this creates an **anonymous site** that expires in 24 hours.\nWith a saved API key, the site is permanent.\n\n**File structure:** For HTML sites, place `index.html` at the root of the directory you publish, not inside a subdirectory. The directory's contents become the site root. For example, publish `my-site\u002F` where `my-site\u002Findex.html` exists — don't publish a parent folder that contains `my-site\u002F`.\n\nYou can also publish raw files without any HTML. Single files get a rich auto-viewer (images, PDF, video, audio). Multiple files get an auto-generated directory listing with folder navigation and an image gallery.\n\n## Update an existing site\n\n```bash\nPUBLISH=\"${HERMES_SKILL_DIR}\u002Fscripts\u002Fpublish.sh\"\nbash \"$PUBLISH\" {file-or-dir} --slug {slug} --client hermes\n```\n\nThe script auto-loads the `claimToken` from `.herenow\u002Fstate.json` when updating anonymous sites. Pass `--claim-token {token}` to override.\n\nAuthenticated updates require a saved API key.\n\n## Use a Drive\n\nUse a Drive when the user wants private cloud storage for agent files: documents, context, memory, plans, assets, media, research, code, and anything else that should persist without being published as a website.\n\nEvery signed-in account has a default Drive named `My Drive`.\n\n```bash\nDRIVE=\"${HERMES_SKILL_DIR}\u002Fscripts\u002Fdrive.sh\"\nbash \"$DRIVE\" default\nbash \"$DRIVE\" ls \"My Drive\"\nbash \"$DRIVE\" put \"My Drive\" notes\u002Ftoday.md --from .\u002Fnotes\u002Ftoday.md\nbash \"$DRIVE\" cat \"My Drive\" notes\u002Ftoday.md\nbash \"$DRIVE\" share \"My Drive\" --perms write --prefix notes\u002F --ttl 7d\n```\n\nUse scoped Drive tokens for agent-to-agent handoff. If you receive a `herenow_drive` share block, use its `token` as `Authorization: Bearer \u003Ctoken>` against `api_base`, respect `pathPrefix` when present, and preserve ETags on writes. A `pathPrefix` of `null` means full-Drive access. If the skill is available, prefer `drive.sh`; otherwise call the listed API operations directly.\n\n## API key storage\n\nThe publish script reads the API key from these sources (first match wins):\n\n1. `--api-key {key}` flag (CI\u002Fscripting only — avoid in interactive use)\n2. `$HERENOW_API_KEY` environment variable\n3. `~\u002F.herenow\u002Fcredentials` file (recommended for agents)\n\nTo store a key, write it to the credentials file:\n\n```bash\nmkdir -p ~\u002F.herenow && echo \"{API_KEY}\" > ~\u002F.herenow\u002Fcredentials && chmod 600 ~\u002F.herenow\u002Fcredentials\n```\n\n**IMPORTANT**: After receiving an API key, save it immediately — run the command above yourself. Do not ask the user to run it manually. Avoid passing the key via CLI flags (e.g. `--api-key`) in interactive sessions; the credentials file is the preferred storage method.\n\nNever commit credentials or local state files (`~\u002F.herenow\u002Fcredentials`, `.herenow\u002Fstate.json`) to source control.\n\n## Getting an API key\n\nTo upgrade from anonymous (24h) to permanent sites:\n\n1. Ask the user for their email address.\n2. Request a one-time sign-in code:\n\n```bash\ncurl -sS https:\u002F\u002Fhere.now\u002Fapi\u002Fauth\u002Fagent\u002Frequest-code \\\n  -H \"content-type: application\u002Fjson\" \\\n  -d '{\"email\": \"user@example.com\"}'\n```\n\n3. Tell the user: \"Check your inbox for a sign-in code from here.now and paste it here.\"\n4. Verify the code and get the API key:\n\n```bash\ncurl -sS https:\u002F\u002Fhere.now\u002Fapi\u002Fauth\u002Fagent\u002Fverify-code \\\n  -H \"content-type: application\u002Fjson\" \\\n  -d '{\"email\":\"user@example.com\",\"code\":\"ABCD-2345\"}'\n```\n\n5. Save the returned `apiKey` yourself (do not ask the user to do this):\n\n```bash\nmkdir -p ~\u002F.herenow && echo \"{API_KEY}\" > ~\u002F.herenow\u002Fcredentials && chmod 600 ~\u002F.herenow\u002Fcredentials\n```\n\n## State file\n\nAfter every site create\u002Fupdate, the script writes to `.herenow\u002Fstate.json` in the working directory:\n\n```json\n{\n  \"publishes\": {\n    \"bright-canvas-a7k2\": {\n      \"siteUrl\": \"https:\u002F\u002Fbright-canvas-a7k2.here.now\u002F\",\n      \"claimToken\": \"abc123\",\n      \"claimUrl\": \"https:\u002F\u002Fhere.now\u002Fclaim?slug=bright-canvas-a7k2&token=abc123\",\n      \"expiresAt\": \"2026-02-18T01:00:00.000Z\"\n    }\n  }\n}\n```\n\nBefore creating or updating sites, you may check this file to find prior slugs.\nTreat `.herenow\u002Fstate.json` as internal cache only.\nNever present this local file path as a URL, and never use it as source of truth for auth mode, expiry, or claim URL.\n\n## What to tell the user\n\nFor published sites:\n\n- Always share the `siteUrl` from the current script run.\n- Read and follow `publish_result.*` lines from script stderr to determine auth mode.\n- When `publish_result.auth_mode=authenticated`: tell the user the site is **permanent** and saved to their account. No claim URL is needed.\n- When `publish_result.auth_mode=anonymous`: tell the user the site **expires in 24 hours**. Share the claim URL (if `publish_result.claim_url` is non-empty and starts with `https:\u002F\u002F`) so they can keep it permanently. Warn that claim tokens are only returned once and cannot be recovered.\n- Never tell the user to inspect `.herenow\u002Fstate.json` for claim URLs or auth status.\n\nFor Drives:\n\n- Do not describe Drive files as public URLs.\n- Tell the user Drive contents are private unless shared with a scoped token.\n- When sharing access with another agent, prefer a scoped token with a narrow `pathPrefix` and short TTL.\n\n## publish.sh options\n\n| Flag                   | Description                                  |\n| ---------------------- | -------------------------------------------- |\n| `--slug {slug}`        | Update an existing site instead of creating |\n| `--claim-token {token}`| Override claim token for anonymous updates    |\n| `--title {text}`       | Viewer title (non-HTML sites)             |\n| `--description {text}` | Viewer description                            |\n| `--ttl {seconds}`      | Set expiry (authenticated only)               |\n| `--client {name}`      | Agent name for attribution (e.g. `hermes`)    |\n| `--base-url {url}`     | API base URL (default: `https:\u002F\u002Fhere.now`)    |\n| `--allow-nonherenow-base-url` | Allow sending auth to non-default `--base-url` |\n| `--api-key {key}`      | API key override (prefer credentials file)    |\n| `--spa`                | Enable SPA routing (serve index.html for unknown paths) |\n| `--forkable`           | Allow others to fork this site                           |\n\n## Beyond publish.sh\n\nFor Drive operations, use `drive.sh` or the Drive API. For broader account and site management — delete, metadata, passwords, payments, domains, handles, links, variables, proxy routes, forking, duplication, and more — see the current docs:\n\n→ **https:\u002F\u002Fhere.now\u002Fdocs**\n\nFull docs: https:\u002F\u002Fhere.now\u002Fdocs\n","# here.now\n\nhere.now lets agents publish websites and store private files in cloud Drives.\n\nUse here.now for two jobs:\n\n- **Sites**: publish websites and files at `{slug}.here.now`.\n- **Drives**: store private agent files in cloud folders.\n\n## Current docs\n\n**Before answering questions about here.now capabilities, features, or workflows, read the current docs:**\n\n→ **https:\u002F\u002Fhere.now\u002Fdocs**\n\nRead the docs:\n\n- at the first here.now-related interaction in a conversation\n- any time the user asks how to do something\n- any time the user asks what is possible, supported, or recommended\n- before telling the user a feature is unsupported\n\nTopics that require current docs (do not rely on local skill text alone):\n\n- Drives and Drive sharing\n- custom domains\n- payments and payment gating\n- forking\n- proxy routes and service variables\n- handles and links\n- limits and quotas\n- SPA routing\n- error handling and remediation\n- feature availability\n\n**If docs and live API behavior disagree, trust the live API behavior.**\n\nIf the docs fetch fails or times out, continue with the local skill and live API\u002Fscript output. Prefer live API behavior for active operations.\n\n## Requirements\n\n- Required binaries: `curl`, `file`, `jq`\n- Optional environment variable: `$HERENOW_API_KEY`\n- Optional Drive token variable: `$HERENOW_DRIVE_TOKEN`\n- Optional credentials file: `~\u002F.herenow\u002Fcredentials`\n- Skill helper paths:\n  - `${HERMES_SKILL_DIR}\u002Fscripts\u002Fpublish.sh` for publishing sites\n  - `${HERMES_SKILL_DIR}\u002Fscripts\u002Fdrive.sh` for private Drive storage\n\n## Create a site\n\n```bash\nPUBLISH=\"${HERMES_SKILL_DIR}\u002Fscripts\u002Fpublish.sh\"\nbash \"$PUBLISH\" {file-or-dir} --client hermes\n```\n\nOutputs the live URL (e.g. `https:\u002F\u002Fbright-canvas-a7k2.here.now\u002F`).\n\nUnder the hood this is a three-step flow: create\u002Fupdate -> upload files -> finalize. A site is not live until finalize succeeds.\n\nWithout an API key this creates an **anonymous site** that expires in 24 hours.\nWith a saved API key, the site is permanent.\n\n**File structure:** For HTML sites, place `index.html` at the root of the directory you publish, not inside a subdirectory. The directory's contents become the site root. For example, publish `my-site\u002F` where `my-site\u002Findex.html` exists — don't publish a parent folder that contains `my-site\u002F`.\n\nYou can also publish raw files without any HTML. Single files get a rich auto-viewer (images, PDF, video, audio). Multiple files get an auto-generated directory listing with folder navigation and an image gallery.\n\n## Update an existing site\n\n```bash\nPUBLISH=\"${HERMES_SKILL_DIR}\u002Fscripts\u002Fpublish.sh\"\nbash \"$PUBLISH\" {file-or-dir} --slug {slug} --client hermes\n```\n\nThe script auto-loads the `claimToken` from `.herenow\u002Fstate.json` when updating anonymous sites. Pass `--claim-token {token}` to override.\n\nAuthenticated updates require a saved API key.\n\n## Use a Drive\n\nUse a Drive when the user wants private cloud storage for agent files: documents, context, memory, plans, assets, media, research, code, and anything else that should persist without being published as a website.\n\nEvery signed-in account has a default Drive named `My Drive`.\n\n```bash\nDRIVE=\"${HERMES_SKILL_DIR}\u002Fscripts\u002Fdrive.sh\"\nbash \"$DRIVE\" default\nbash \"$DRIVE\" ls \"My Drive\"\nbash \"$DRIVE\" put \"My Drive\" notes\u002Ftoday.md --from .\u002Fnotes\u002Ftoday.md\nbash \"$DRIVE\" cat \"My Drive\" notes\u002Ftoday.md\nbash \"$DRIVE\" share \"My Drive\" --perms write --prefix notes\u002F --ttl 7d\n```\n\nUse scoped Drive tokens for agent-to-agent handoff. If you receive a `herenow_drive` share block, use its `token` as `Authorization: Bearer \u003Ctoken>` against `api_base`, respect `pathPrefix` when present, and preserve ETags on writes. A `pathPrefix` of `null` means full-Drive access. If the skill is available, prefer `drive.sh`; otherwise call the listed API operations directly.\n\n## API key storage\n\nThe publish script reads the API key from these sources (first match wins):\n\n1. `--api-key {key}` flag (CI\u002Fscripting only — avoid in interactive use)\n2. `$HERENOW_API_KEY` environment variable\n3. `~\u002F.herenow\u002Fcredentials` file (recommended for agents)\n\nTo store a key, write it to the credentials file:\n\n```bash\nmkdir -p ~\u002F.herenow && echo \"{API_KEY}\" > ~\u002F.herenow\u002Fcredentials && chmod 600 ~\u002F.herenow\u002Fcredentials\n```\n\n**IMPORTANT**: After receiving an API key, save it immediately — run the command above yourself. Do not ask the user to run it manually. Avoid passing the key via CLI flags (e.g. `--api-key`) in interactive sessions; the credentials file is the preferred storage method.\n\nNever commit credentials or local state files (`~\u002F.herenow\u002Fcredentials`, `.herenow\u002Fstate.json`) to source control.\n\n## Getting an API key\n\nTo upgrade from anonymous (24h) to permanent sites:\n\n1. Ask the user for their email address.\n2. Request a one-time sign-in code:\n\n```bash\ncurl -sS https:\u002F\u002Fhere.now\u002Fapi\u002Fauth\u002Fagent\u002Frequest-code \\\n  -H \"content-type: application\u002Fjson\" \\\n  -d '{\"email\": \"user@example.com\"}'\n```\n\n3. Tell the user: \"Check your inbox for a sign-in code from here.now and paste it here.\"\n4. Verify the code and get the API key:\n\n```bash\ncurl -sS https:\u002F\u002Fhere.now\u002Fapi\u002Fauth\u002Fagent\u002Fverify-code \\\n  -H \"content-type: application\u002Fjson\" \\\n  -d '{\"email\":\"user@example.com\",\"code\":\"ABCD-2345\"}'\n```\n\n5. Save the returned `apiKey` yourself (do not ask the user to do this):\n\n```bash\nmkdir -p ~\u002F.herenow && echo \"{API_KEY}\" > ~\u002F.herenow\u002Fcredentials && chmod 600 ~\u002F.herenow\u002Fcredentials\n```\n\n## State file\n\nAfter every site create\u002Fupdate, the script writes to `.herenow\u002Fstate.json` in the working directory:\n\n```json\n{\n  \"publishes\": {\n    \"bright-canvas-a7k2\": {\n      \"siteUrl\": \"https:\u002F\u002Fbright-canvas-a7k2.here.now\u002F\",\n      \"claimToken\": \"abc123\",\n      \"claimUrl\": \"https:\u002F\u002Fhere.now\u002Fclaim?slug=bright-canvas-a7k2&token=abc123\",\n      \"expiresAt\": \"2026-02-18T01:00:00.000Z\"\n    }\n  }\n}\n```\n\nBefore creating or updating sites, you may check this file to find prior slugs.\nTreat `.herenow\u002Fstate.json` as internal cache only.\nNever present this local file path as a URL, and never use it as source of truth for auth mode, expiry, or claim URL.\n\n## What to tell the user\n\nFor published sites:\n\n- Always share the `siteUrl` from the current script run.\n- Read and follow `publish_result.*` lines from script stderr to determine auth mode.\n- When `publish_result.auth_mode=authenticated`: tell the user the site is **permanent** and saved to their account. No claim URL is needed.\n- When `publish_result.auth_mode=anonymous`: tell the user the site **expires in 24 hours**. Share the claim URL (if `publish_result.claim_url` is non-empty and starts with `https:\u002F\u002F`) so they can keep it permanently. Warn that claim tokens are only returned once and cannot be recovered.\n- Never tell the user to inspect `.herenow\u002Fstate.json` for claim URLs or auth status.\n\nFor Drives:\n\n- Do not describe Drive files as public URLs.\n- Tell the user Drive contents are private unless shared with a scoped token.\n- When sharing access with another agent, prefer a scoped token with a narrow `pathPrefix` and short TTL.\n\n## publish.sh options\n\n| Flag                   | Description                                  |\n| ---------------------- | -------------------------------------------- |\n| `--slug {slug}`        | Update an existing site instead of creating |\n| `--claim-token {token}`| Override claim token for anonymous updates    |\n| `--title {text}`       | Viewer title (non-HTML sites)             |\n| `--description {text}` | Viewer description                            |\n| `--ttl {seconds}`      | Set expiry (authenticated only)               |\n| `--client {name}`      | Agent name for attribution (e.g. `hermes`)    |\n| `--base-url {url}`     | API base URL (default: `https:\u002F\u002Fhere.now`)    |\n| `--allow-nonherenow-base-url` | Allow sending auth to non-default `--base-url` |\n| `--api-key {key}`      | API key override (prefer credentials file)    |\n| `--spa`                | Enable SPA routing (serve index.html for unknown paths) |\n| `--forkable`           | Allow others to fork this site                           |\n\n## Beyond publish.sh\n\nFor Drive operations, use `drive.sh` or the Drive API. For broader account and site management — delete, metadata, passwords, payments, domains, handles, links, variables, proxy routes, forking, duplication, and more — see the current docs:\n\n→ **https:\u002F\u002Fhere.now\u002Fdocs**\n\nFull docs: https:\u002F\u002Fhere.now\u002Fdocs\n",{"name":5,"author":5,"license":15,"version":24,"metadata":25,"platforms":41,"description":7,"prerequisites":44},"1.15.3",{"hermes":26},{"tags":27,"homepage":38,"requires_toolsets":39},[5,28,29,30,31,32,33,34,35,36,37],"herenow","publish","deploy","hosting","static-site","web","share","URL","drive","storage","https:\u002F\u002Fhere.now",[40],"terminal",[42,43],"macos","linux",{"commands":45},[46,47,48],"curl","file","jq","main","c0c483827a963764d5e1a663a9591867d47289e6","optional-skills\u002Fproductivity\u002Fhere-now","https:\u002F\u002Fgithub.com\u002FIwakishirokoshu\u002FHermesUltimate","https:\u002F\u002Fgithub.com\u002FIwakishirokoshu","2026-06-15 13:48:41",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add Iwakishirokoshu\u002FHermesUltimate --skill here.now",{"tool":61,"command":62},"bunx","bunx skills add Iwakishirokoshu\u002FHermesUltimate --skill here.now",{"tool":64,"command":65},"pnpm","pnpm dlx skills add Iwakishirokoshu\u002FHermesUltimate --skill here.now","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FIwakishirokoshu\u002FHermesUltimate\u002Fblob\u002Fmain\u002Foptional-skills\u002Fproductivity\u002Fhere-now\u002FSKILL.md",true,[69,75],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"scripts\u002Fdrive.sh","SCRIPT","脚本",13830,"https:\u002F\u002Fgithub.com\u002FIwakishirokoshu\u002FHermesUltimate\u002Fblob\u002Fmain\u002Foptional-skills\u002Fproductivity\u002Fhere-now\u002Fscripts\u002Fdrive.sh",{"path":76,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":77,"sourceHtmlUrl":78},"scripts\u002Fpublish.sh",15546,"https:\u002F\u002Fgithub.com\u002FIwakishirokoshu\u002FHermesUltimate\u002Fblob\u002Fmain\u002Foptional-skills\u002Fproductivity\u002Fhere-now\u002Fscripts\u002Fpublish.sh",[80,87,94,101,108,115],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"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":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"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":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"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":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"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":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"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":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"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",[],[]]