[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D6X82BFCTYB9ZR6YGDVNCE":3,"skill-same:01M7D6X82BFCTYB9ZR6YGDVNCE":73},{"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":41,"commitSha":42,"skillDirectory":43,"forksCount":14,"repositoryHtmlUrl":44,"repositoryHomepageUrl":6,"ownerHtmlUrl":45,"ownerBlogUrl":46,"ownerDescription":47,"updatedAt":48,"install":49,"resources":62},"01M7D6X82BFCTYB9ZR6YGDVNCE","himalaya",null,"Himalaya CLI: IMAP\u002FSMTP email from terminal.","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\u002Femail\u002Fhimalaya\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: himalaya\ndescription: \"Himalaya CLI: IMAP\u002FSMTP email from terminal.\"\nversion: 1.1.0\nauthor: community\nlicense: MIT\nplatforms: [linux, macos, windows]\nmetadata:\n  hermes:\n    tags: [Email, IMAP, SMTP, CLI, Communication]\n    homepage: https:\u002F\u002Fgithub.com\u002Fpimalaya\u002Fhimalaya\nprerequisites:\n  commands: [himalaya]\n---\n\n# Himalaya Email CLI\n\nHimalaya is a CLI email client that lets you manage emails from the terminal using IMAP, SMTP, Notmuch, or Sendmail backends.\n\nThis skill is separate from the Hermes Email gateway adapter. The gateway\nadapter lets people email the agent and uses Hermes' built-in IMAP\u002FSMTP\nadapter; this skill lets the agent operate a mailbox from terminal tools and\nrequires the external `himalaya` CLI.\n\n## References\n\n- `references\u002Fconfiguration.md` (config file setup + IMAP\u002FSMTP authentication)\n- `references\u002Fmessage-composition.md` (MML syntax for composing emails)\n\n## Prerequisites\n\n1. Himalaya CLI installed (`himalaya --version` to verify)\n2. A configuration file at `~\u002F.config\u002Fhimalaya\u002Fconfig.toml`\n3. IMAP\u002FSMTP credentials configured (password stored securely)\n\n### Installation\n\n```bash\n# Pre-built binary (Linux\u002FmacOS — recommended)\ncurl -sSL https:\u002F\u002Fraw.githubusercontent.com\u002Fpimalaya\u002Fhimalaya\u002Fmaster\u002Finstall.sh | PREFIX=~\u002F.local sh\n\n# macOS via Homebrew\nbrew install himalaya\n\n# Or via cargo (any platform with Rust)\ncargo install himalaya --locked\n```\n\n## Configuration Setup\n\nRun the interactive wizard to set up an account:\n\n```bash\nhimalaya account configure\n```\n\nOr create `~\u002F.config\u002Fhimalaya\u002Fconfig.toml` manually:\n\n```toml\n[accounts.personal]\nemail = \"you@example.com\"\ndisplay-name = \"Your Name\"\ndefault = true\n\nbackend.type = \"imap\"\nbackend.host = \"imap.example.com\"\nbackend.port = 993\nbackend.encryption.type = \"tls\"\nbackend.login = \"you@example.com\"\nbackend.auth.type = \"password\"\nbackend.auth.cmd = \"pass show email\u002Fimap\"  # or use keyring\n\nmessage.send.backend.type = \"smtp\"\nmessage.send.backend.host = \"smtp.example.com\"\nmessage.send.backend.port = 587\nmessage.send.backend.encryption.type = \"start-tls\"\nmessage.send.backend.login = \"you@example.com\"\nmessage.send.backend.auth.type = \"password\"\nmessage.send.backend.auth.cmd = \"pass show email\u002Fsmtp\"\n\n# Folder aliases (himalaya v1.2.0+ syntax). Required whenever the\n# server's folder names don't match himalaya's canonical names\n# (inbox\u002Fsent\u002Fdrafts\u002Ftrash). Gmail is the common case — see\n# `references\u002Fconfiguration.md` for the `[Gmail]\u002FSent Mail` mapping.\nfolder.aliases.inbox = \"INBOX\"\nfolder.aliases.sent = \"Sent\"\nfolder.aliases.drafts = \"Drafts\"\nfolder.aliases.trash = \"Trash\"\n```\n\n> **Heads up on the alias syntax.** Pre-v1.2.0 docs used a\n> `[accounts.NAME.folder.alias]` sub-section (singular `alias`).\n> v1.2.0 silently ignores that form — TOML parses fine, but the\n> alias resolver never reads it, so every lookup falls through to\n> the canonical name. On Gmail this means save-to-Sent fails *after*\n> SMTP delivery succeeds, and `himalaya message send` exits non-zero.\n> Any caller (agent, script, user) that retries on that exit code\n> will re-run the entire send — including SMTP — producing duplicate\n> emails to recipients. Always use `folder.aliases.X` (plural, dotted\n> keys, directly under `[accounts.NAME]`).\n\n## Hermes Integration Notes\n\n- **Reading, listing, searching, moving, deleting** all work directly through the terminal tool\n- **Composing\u002Freplying\u002Fforwarding** — piped input (`cat \u003C\u003C EOF | himalaya template send`) is recommended for reliability. Interactive `$EDITOR` mode works with `pty=true` + background + process tool, but requires knowing the editor and its commands\n- Use `--output json` for structured output that's easier to parse programmatically\n- The `himalaya account configure` wizard requires interactive input — use PTY mode: `terminal(command=\"himalaya account configure\", pty=true)`\n\n## Common Operations\n\n### List Folders\n\n```bash\nhimalaya folder list\n```\n\n### List Emails\n\nList emails in INBOX (default):\n\n```bash\nhimalaya envelope list\n```\n\nList emails in a specific folder:\n\n```bash\nhimalaya envelope list --folder \"Sent\"\n```\n\nList with pagination:\n\n```bash\nhimalaya envelope list --page 1 --page-size 20\n```\n\n### Search Emails\n\n```bash\nhimalaya envelope list from john@example.com subject meeting\n```\n\n### Read an Email\n\nRead email by ID (shows plain text):\n\n```bash\nhimalaya message read 42\n```\n\nExport raw MIME:\n\n```bash\nhimalaya message export 42 --full\n```\n\n### Reply to an Email\n\nTo reply non-interactively from Hermes, read the original message, compose a reply, and pipe it:\n\n```bash\n# Get the reply template, edit it, and send\nhimalaya template reply 42 | sed 's\u002F^$\u002F\\nYour reply text here\\n\u002F' | himalaya template send\n```\n\nOr build the reply manually:\n\n```bash\ncat \u003C\u003C 'EOF' | himalaya template send\nFrom: you@example.com\nTo: sender@example.com\nSubject: Re: Original Subject\nIn-Reply-To: \u003Coriginal-message-id>\n\nYour reply here.\nEOF\n```\n\nReply-all (interactive — needs $EDITOR, use template approach above instead):\n\n```bash\nhimalaya message reply 42 --all\n```\n\n### Forward an Email\n\n```bash\n# Get forward template and pipe with modifications\nhimalaya template forward 42 | sed 's\u002F^To:.*\u002FTo: newrecipient@example.com\u002F' | himalaya template send\n```\n\n### Write a New Email\n\n**Non-interactive (use this from Hermes)** — pipe the message via stdin:\n\n```bash\ncat \u003C\u003C 'EOF' | himalaya template send\nFrom: you@example.com\nTo: recipient@example.com\nSubject: Test Message\n\nHello from Himalaya!\nEOF\n```\n\nOr with headers flag:\n\n```bash\nhimalaya message write -H \"To:recipient@example.com\" -H \"Subject:Test\" \"Message body here\"\n```\n\nNote: `himalaya message write` without piped input opens `$EDITOR`. This works with `pty=true` + background mode, but piping is simpler and more reliable.\n\n### Move\u002FCopy Emails\n\nMove to folder (target folder comes first, then the message ID):\n\n```bash\nhimalaya message move \"Archive\" 42\n```\n\nCopy to folder (target folder comes first, then the message ID):\n\n```bash\nhimalaya message copy \"Important\" 42\n```\n\n### Delete an Email\n\n```bash\nhimalaya message delete 42\n```\n\n### Manage Flags\n\nAdd flag:\n\n```bash\nhimalaya flag add 42 --flag seen\n```\n\nRemove flag:\n\n```bash\nhimalaya flag remove 42 --flag seen\n```\n\n## Multiple Accounts\n\nList accounts:\n\n```bash\nhimalaya account list\n```\n\nUse a specific account:\n\n```bash\nhimalaya --account work envelope list\n```\n\n## Attachments\n\nSave attachments from a message:\n\n```bash\nhimalaya attachment download 42\n```\n\nSave to specific directory:\n\n```bash\nhimalaya attachment download 42 --downloads-dir ~\u002FDownloads\n```\n\n## Output Formats\n\nMost commands support `--output` for structured output:\n\n```bash\nhimalaya envelope list --output json\nhimalaya envelope list --output plain\n```\n\n## Debugging\n\nEnable debug logging:\n\n```bash\nRUST_LOG=debug himalaya envelope list\n```\n\nFull trace with backtrace:\n\n```bash\nRUST_LOG=trace RUST_BACKTRACE=1 himalaya envelope list\n```\n\n## Tips\n\n- Use `himalaya --help` or `himalaya \u003Ccommand> --help` for detailed usage.\n- Message IDs are relative to the current folder; re-list after folder changes.\n- For composing rich emails with attachments, use MML syntax (see `references\u002Fmessage-composition.md`).\n- Store passwords securely using `pass`, system keyring, or a command that outputs the password.\n","# Himalaya Email CLI\n\nHimalaya is a CLI email client that lets you manage emails from the terminal using IMAP, SMTP, Notmuch, or Sendmail backends.\n\nThis skill is separate from the Hermes Email gateway adapter. The gateway\nadapter lets people email the agent and uses Hermes' built-in IMAP\u002FSMTP\nadapter; this skill lets the agent operate a mailbox from terminal tools and\nrequires the external `himalaya` CLI.\n\n## References\n\n- `references\u002Fconfiguration.md` (config file setup + IMAP\u002FSMTP authentication)\n- `references\u002Fmessage-composition.md` (MML syntax for composing emails)\n\n## Prerequisites\n\n1. Himalaya CLI installed (`himalaya --version` to verify)\n2. A configuration file at `~\u002F.config\u002Fhimalaya\u002Fconfig.toml`\n3. IMAP\u002FSMTP credentials configured (password stored securely)\n\n### Installation\n\n```bash\n# Pre-built binary (Linux\u002FmacOS — recommended)\ncurl -sSL https:\u002F\u002Fraw.githubusercontent.com\u002Fpimalaya\u002Fhimalaya\u002Fmaster\u002Finstall.sh | PREFIX=~\u002F.local sh\n\n# macOS via Homebrew\nbrew install himalaya\n\n# Or via cargo (any platform with Rust)\ncargo install himalaya --locked\n```\n\n## Configuration Setup\n\nRun the interactive wizard to set up an account:\n\n```bash\nhimalaya account configure\n```\n\nOr create `~\u002F.config\u002Fhimalaya\u002Fconfig.toml` manually:\n\n```toml\n[accounts.personal]\nemail = \"you@example.com\"\ndisplay-name = \"Your Name\"\ndefault = true\n\nbackend.type = \"imap\"\nbackend.host = \"imap.example.com\"\nbackend.port = 993\nbackend.encryption.type = \"tls\"\nbackend.login = \"you@example.com\"\nbackend.auth.type = \"password\"\nbackend.auth.cmd = \"pass show email\u002Fimap\"  # or use keyring\n\nmessage.send.backend.type = \"smtp\"\nmessage.send.backend.host = \"smtp.example.com\"\nmessage.send.backend.port = 587\nmessage.send.backend.encryption.type = \"start-tls\"\nmessage.send.backend.login = \"you@example.com\"\nmessage.send.backend.auth.type = \"password\"\nmessage.send.backend.auth.cmd = \"pass show email\u002Fsmtp\"\n\n# Folder aliases (himalaya v1.2.0+ syntax). Required whenever the\n# server's folder names don't match himalaya's canonical names\n# (inbox\u002Fsent\u002Fdrafts\u002Ftrash). Gmail is the common case — see\n# `references\u002Fconfiguration.md` for the `[Gmail]\u002FSent Mail` mapping.\nfolder.aliases.inbox = \"INBOX\"\nfolder.aliases.sent = \"Sent\"\nfolder.aliases.drafts = \"Drafts\"\nfolder.aliases.trash = \"Trash\"\n```\n\n> **Heads up on the alias syntax.** Pre-v1.2.0 docs used a\n> `[accounts.NAME.folder.alias]` sub-section (singular `alias`).\n> v1.2.0 silently ignores that form — TOML parses fine, but the\n> alias resolver never reads it, so every lookup falls through to\n> the canonical name. On Gmail this means save-to-Sent fails *after*\n> SMTP delivery succeeds, and `himalaya message send` exits non-zero.\n> Any caller (agent, script, user) that retries on that exit code\n> will re-run the entire send — including SMTP — producing duplicate\n> emails to recipients. Always use `folder.aliases.X` (plural, dotted\n> keys, directly under `[accounts.NAME]`).\n\n## Hermes Integration Notes\n\n- **Reading, listing, searching, moving, deleting** all work directly through the terminal tool\n- **Composing\u002Freplying\u002Fforwarding** — piped input (`cat \u003C\u003C EOF | himalaya template send`) is recommended for reliability. Interactive `$EDITOR` mode works with `pty=true` + background + process tool, but requires knowing the editor and its commands\n- Use `--output json` for structured output that's easier to parse programmatically\n- The `himalaya account configure` wizard requires interactive input — use PTY mode: `terminal(command=\"himalaya account configure\", pty=true)`\n\n## Common Operations\n\n### List Folders\n\n```bash\nhimalaya folder list\n```\n\n### List Emails\n\nList emails in INBOX (default):\n\n```bash\nhimalaya envelope list\n```\n\nList emails in a specific folder:\n\n```bash\nhimalaya envelope list --folder \"Sent\"\n```\n\nList with pagination:\n\n```bash\nhimalaya envelope list --page 1 --page-size 20\n```\n\n### Search Emails\n\n```bash\nhimalaya envelope list from john@example.com subject meeting\n```\n\n### Read an Email\n\nRead email by ID (shows plain text):\n\n```bash\nhimalaya message read 42\n```\n\nExport raw MIME:\n\n```bash\nhimalaya message export 42 --full\n```\n\n### Reply to an Email\n\nTo reply non-interactively from Hermes, read the original message, compose a reply, and pipe it:\n\n```bash\n# Get the reply template, edit it, and send\nhimalaya template reply 42 | sed 's\u002F^$\u002F\\nYour reply text here\\n\u002F' | himalaya template send\n```\n\nOr build the reply manually:\n\n```bash\ncat \u003C\u003C 'EOF' | himalaya template send\nFrom: you@example.com\nTo: sender@example.com\nSubject: Re: Original Subject\nIn-Reply-To: \u003Coriginal-message-id>\n\nYour reply here.\nEOF\n```\n\nReply-all (interactive — needs $EDITOR, use template approach above instead):\n\n```bash\nhimalaya message reply 42 --all\n```\n\n### Forward an Email\n\n```bash\n# Get forward template and pipe with modifications\nhimalaya template forward 42 | sed 's\u002F^To:.*\u002FTo: newrecipient@example.com\u002F' | himalaya template send\n```\n\n### Write a New Email\n\n**Non-interactive (use this from Hermes)** — pipe the message via stdin:\n\n```bash\ncat \u003C\u003C 'EOF' | himalaya template send\nFrom: you@example.com\nTo: recipient@example.com\nSubject: Test Message\n\nHello from Himalaya!\nEOF\n```\n\nOr with headers flag:\n\n```bash\nhimalaya message write -H \"To:recipient@example.com\" -H \"Subject:Test\" \"Message body here\"\n```\n\nNote: `himalaya message write` without piped input opens `$EDITOR`. This works with `pty=true` + background mode, but piping is simpler and more reliable.\n\n### Move\u002FCopy Emails\n\nMove to folder (target folder comes first, then the message ID):\n\n```bash\nhimalaya message move \"Archive\" 42\n```\n\nCopy to folder (target folder comes first, then the message ID):\n\n```bash\nhimalaya message copy \"Important\" 42\n```\n\n### Delete an Email\n\n```bash\nhimalaya message delete 42\n```\n\n### Manage Flags\n\nAdd flag:\n\n```bash\nhimalaya flag add 42 --flag seen\n```\n\nRemove flag:\n\n```bash\nhimalaya flag remove 42 --flag seen\n```\n\n## Multiple Accounts\n\nList accounts:\n\n```bash\nhimalaya account list\n```\n\nUse a specific account:\n\n```bash\nhimalaya --account work envelope list\n```\n\n## Attachments\n\nSave attachments from a message:\n\n```bash\nhimalaya attachment download 42\n```\n\nSave to specific directory:\n\n```bash\nhimalaya attachment download 42 --downloads-dir ~\u002FDownloads\n```\n\n## Output Formats\n\nMost commands support `--output` for structured output:\n\n```bash\nhimalaya envelope list --output json\nhimalaya envelope list --output plain\n```\n\n## Debugging\n\nEnable debug logging:\n\n```bash\nRUST_LOG=debug himalaya envelope list\n```\n\nFull trace with backtrace:\n\n```bash\nRUST_LOG=trace RUST_BACKTRACE=1 himalaya envelope list\n```\n\n## Tips\n\n- Use `himalaya --help` or `himalaya \u003Ccommand> --help` for detailed usage.\n- Message IDs are relative to the current folder; re-list after folder changes.\n- For composing rich emails with attachments, use MML syntax (see `references\u002Fmessage-composition.md`).\n- Store passwords securely using `pass`, system keyring, or a command that outputs the password.\n",{"name":5,"author":24,"license":15,"version":25,"metadata":26,"platforms":35,"description":7,"prerequisites":39},"community","1.1.0",{"hermes":27},{"tags":28,"homepage":34},[29,30,31,32,33],"Email","IMAP","SMTP","CLI","Communication","https:\u002F\u002Fgithub.com\u002Fpimalaya\u002Fhimalaya",[36,37,38],"linux","macos","windows",{"commands":40},[5],"main","eac438ea9216a7cb8a570cab803eb01eeafc6793","skills\u002Femail\u002Fhimalaya","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":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add GrupoANDevelopment-m\u002Falberto-ai --skill himalaya",{"tool":55,"command":56},"bunx","bunx skills add GrupoANDevelopment-m\u002Falberto-ai --skill himalaya",{"tool":58,"command":59},"pnpm","pnpm dlx skills add GrupoANDevelopment-m\u002Falberto-ai --skill himalaya","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fskills\u002Femail\u002Fhimalaya\u002FSKILL.md",true,[63,69],{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fconfiguration.md","REFERENCE","参考文档",5906,"https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fskills\u002Femail\u002Fhimalaya\u002Freferences\u002Fconfiguration.md",{"path":70,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fmessage-composition.md",3799,"https:\u002F\u002Fgithub.com\u002FGrupoANDevelopment-m\u002Falberto-ai\u002Fblob\u002Fmain\u002Fskills\u002Femail\u002Fhimalaya\u002Freferences\u002Fmessage-composition.md",[74,82,89,96,103,110],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"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":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"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":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"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":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"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":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"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":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"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",[],[]]