[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D7NGVBS0SDVSHWMK03M0NN":3,"skill-same:01M7D7NGVBS0SDVSHWMK03M0NN":81},{"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":54,"ownerDescription":55,"updatedAt":56,"install":57,"resources":70},"01M7D7NGVBS0SDVSHWMK03M0NN","here.now",null,"Publish static sites to {slug}.here.now and store private files in cloud Drives for agent-to-agent handoff.","GrupoANDevelopment-m\u002Falberto-ai","GrupoANDevelopment-m","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F257455179?v=4","01M7D69X2N2KEVN0SJF6WGM6SH","Antônio  Ndombe","01M7D69X3P5JTT8H8S904N3888",0,"MIT","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fskills\u002Foptional\u002Fproductivity\u002Fhere-now\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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","eac438ea9216a7cb8a570cab803eb01eeafc6793","skills\u002Foptional\u002Fproductivity\u002Fhere-now","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m","https:\u002F\u002Fid-preview--d5bef06d-6c9e-4563-a3d4-a855b9d61610.lovable.app\u002F","Eu sou Antonio B. B. Ndombe \r\nEu sou um Pesquisador e desenvolvedor de sistema autonomia cognitivos, fundador de sistemas ODCs ( organismos digital conscientes)","2026-11-04 06:53:39",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add GrupoANDevelopment-m\u002Falberto-ai --skill here.now",{"tool":63,"command":64},"bunx","bunx skills add GrupoANDevelopment-m\u002Falberto-ai --skill here.now",{"tool":66,"command":67},"pnpm","pnpm dlx skills add GrupoANDevelopment-m\u002Falberto-ai --skill here.now","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fskills\u002Foptional\u002Fproductivity\u002Fhere-now\u002FSKILL.md",true,[71,77],{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"scripts\u002Fdrive.sh","SCRIPT","脚本",13830,"https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fskills\u002Foptional\u002Fproductivity\u002Fhere-now\u002Fscripts\u002Fdrive.sh",{"path":78,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":79,"sourceHtmlUrl":80},"scripts\u002Fpublish.sh",15546,"https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fskills\u002Foptional\u002Fproductivity\u002Fhere-now\u002Fscripts\u002Fpublish.sh",[82,90,97,104,111,118],{"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":86,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7DASC6FSCJP49JZBSK0NY1Z","nemoclaw-user-reference","Describes the NemoClaw integration layer and blueprint architecture and how they orchestrate compatible agent sandboxes. Use when looking up architecture, agent integration, plugin structure, or blueprint design. Trigger keywords - nemoclaw architecture, nemoclaw agent architecture, nemoclaw plugin blueprint structure, nemoclaw vs openshell, which cli, nemoclaw cli, openshell cli, sandbox commands, nemoclaw cli commands, nemoclaw command reference, nemoclaw network policy, sandbox egress control operator approval, nemoclaw troubleshooting, nemoclaw debug sandbox issues.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fupstream\u002Fnemoclaw\u002Fskills\u002Fnemoclaw-user-reference\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":86,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M7DAS5S79VK33XFGVAM2TFWF","nemoclaw-user-overview","Explains how OpenClaw, OpenShell, and NemoClaw form the ecosystem, NemoClaw's position in the stack, what NemoClaw adds beyond the community sandbox, and when to prefer NemoClaw versus integrating OpenShell and OpenClaw directly. Use when users ask about the relationship between OpenClaw, OpenShell, and NemoClaw, or when to use NemoClaw versus OpenShell. Trigger keywords - nemoclaw ecosystem, openclaw openshell, nemoclaw vs openshell, sandboxed openclaw, how nemoclaw works, nemoclaw sandbox lifecycle blueprint, nemoclaw overview, openclaw always-on assistants, nvidia openshell, nvidia nemotron, nemoclaw release notes, nemoclaw changelog.","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fupstream\u002Fnemoclaw\u002Fskills\u002Fnemoclaw-user-overview\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":86,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M7DAS0PQEMET5MNGZ1ABSZVS","nemoclaw-user-monitor-sandbox","Inspects sandbox health, traces agent behavior, and diagnoses problems. Use when monitoring a running sandbox, debugging agent issues, or checking sandbox logs. Trigger keywords - monitor nemoclaw sandbox, debug nemoclaw agent issues.","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fupstream\u002Fnemoclaw\u002Fskills\u002Fnemoclaw-user-monitor-sandbox\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":19},"01M7DARQYGF7E9A69VH6S3CGN9","nemoclaw-user-manage-sandboxes","Explains operational tasks after the quickstart: listing sandboxes, status and health checks, logs, diagnostics, port forwards, multiple sandboxes, credential reset, rebuilds, network presets, upgrades, and uninstall. Trigger keywords - manage nemoclaw sandboxes, nemoclaw status, nemoclaw list, nemoclaw dashboard port, nemoclaw rebuild, nemoclaw upgrade sandboxes, nemoclaw uninstall, sandbox mutability, sandbox runtime configuration, sandbox rebuild, nemoclaw backup, nemoclaw restore, workspace backup, openshell sandbox download upload, nemoclaw messaging channels, nemoclaw telegram, nemoclaw discord, nemoclaw slack, nemoclaw wechat, nemoclaw whatsapp, openshell channel messaging, nemoclaw workspace files, soul.md, user.md, identity.md, agents.md, sandbox persistence.","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fupstream\u002Fnemoclaw\u002Fskills\u002Fnemoclaw-user-manage-sandboxes\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":19},"01M7DARH8BRTG51TRCAB7YWDJ4","nemoclaw-user-manage-policy","Adds, removes, or modifies allowed endpoints in the sandbox policy. Use when customizing network policy, changing egress rules, or configuring sandbox endpoint access. Trigger keywords - customize nemoclaw network policy, sandbox egress policy configuration, nemoclaw integration policy examples, post-install policy setup, openshell approval workflow, policy preset, nemoclaw approve network requests, sandbox egress approval tui.","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fupstream\u002Fnemoclaw\u002Fskills\u002Fnemoclaw-user-manage-policy\u002FSKILL.md",[],[],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":19},"01M7DARAT62M2VR37590VCZ5NS","nemoclaw-user-get-started","Installs NemoClaw, launches a sandbox, and runs the first agent prompt. Use when onboarding, installing, or launching a NemoClaw sandbox for the first time. Trigger keywords - nemoclaw quickstart, install nemoclaw openclaw sandbox, nemohermes quickstart, hermes agent nemoclaw, run hermes openshell sandbox, nemoclaw prerequisites, nemoclaw supported platforms, nemoclaw hardware software, nemoclaw windows wsl2 setup, nemoclaw install windows docker desktop.","https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fupstream\u002Fnemoclaw\u002Fskills\u002Fnemoclaw-user-get-started\u002FSKILL.md",[],[]]