[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78E3MH4CSWSXGY413TV5A83":3,"skill-same:01M78E3MH4CSWSXGY413TV5A83":69},{"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":37,"commitSha":38,"skillDirectory":39,"forksCount":14,"repositoryHtmlUrl":40,"repositoryHomepageUrl":6,"ownerHtmlUrl":41,"ownerBlogUrl":42,"ownerDescription":43,"updatedAt":44,"install":45,"resources":58},"01M78E3MH4CSWSXGY413TV5A83","himalaya",null,"Himalaya CLI: IMAP\u002FSMTP email from terminal.","pvbang\u002Fnexus","pvbang","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F89725712?v=4","01M78B6R1DXZZBTN9G0XXBBE0A","Phan Văn Bằng","01M78B6R2T4DYQ9ZY4GJR0Q3V4",0,"MIT","https:\u002F\u002Fgithub.com\u002Fpvbang\u002Fnexus\u002Fblob\u002Fmain\u002Fsrc\u002Fopen-source\u002Fhermes-agent\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\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\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:\n\n```bash\nhimalaya message move 42 \"Archive\"\n```\n\nCopy to folder:\n\n```bash\nhimalaya message copy 42 \"Important\"\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 --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\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:\n\n```bash\nhimalaya message move 42 \"Archive\"\n```\n\nCopy to folder:\n\n```bash\nhimalaya message copy 42 \"Important\"\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 --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,"description":7,"prerequisites":35},"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",{"commands":36},[5],"main","a0559bb2eb5ae47d603efe32afe4589f77bf4ded","src\u002Fopen-source\u002Fhermes-agent\u002Fskills\u002Femail\u002Fhimalaya","https:\u002F\u002Fgithub.com\u002Fpvbang\u002Fnexus","https:\u002F\u002Fgithub.com\u002Fpvbang","pvbang.github.io\u002Fcv","\u003C\u002F> It's a pleasure to meet you","2026-11-13 16:52:49",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add pvbang\u002Fnexus --skill himalaya",{"tool":51,"command":52},"bunx","bunx skills add pvbang\u002Fnexus --skill himalaya",{"tool":54,"command":55},"pnpm","pnpm dlx skills add pvbang\u002Fnexus --skill himalaya","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpvbang\u002Fnexus\u002Fblob\u002Fmain\u002Fsrc\u002Fopen-source\u002Fhermes-agent\u002Fskills\u002Femail\u002Fhimalaya\u002FSKILL.md",true,[59,65],{"path":60,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fconfiguration.md","REFERENCE","参考文档",5906,"https:\u002F\u002Fgithub.com\u002Fpvbang\u002Fnexus\u002Fblob\u002Fmain\u002Fsrc\u002Fopen-source\u002Fhermes-agent\u002Fskills\u002Femail\u002Fhimalaya\u002Freferences\u002Fconfiguration.md",{"path":66,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fmessage-composition.md",3799,"https:\u002F\u002Fgithub.com\u002Fpvbang\u002Fnexus\u002Fblob\u002Fmain\u002Fsrc\u002Fopen-source\u002Fhermes-agent\u002Fskills\u002Femail\u002Fhimalaya\u002Freferences\u002Fmessage-composition.md",[70,79,87,94,101,108],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":75,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M78EFV6FYHV11YKAKYXPND85","skill-creator","Create, edit, improve, or audit AgentSkills. Use when creating a new skill from scratch or when asked to improve, review, audit, tidy up, or clean up an existing skill or SKILL.md file. Also use when editing or restructuring a skill directory (moving files to references\u002F or scripts\u002F, removing stale content, validating against the AgentSkills spec). Triggers on phrases like \"create a skill\", \"author a skill\", \"tidy up a skill\", \"improve this skill\", \"review the skill\", \"clean up the skill\", \"audit the skill\".","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fpvbang\u002Fnexus\u002Fblob\u002Fmain\u002Fsrc\u002Fopen-source\u002Fopenclaw\u002Fskills\u002Fskill-creator\u002Flicense.txt","https:\u002F\u002Fgithub.com\u002Fpvbang\u002Fnexus\u002Fblob\u002Fmain\u002Fsrc\u002Fopen-source\u002Fopenclaw\u002Fskills\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":83,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M78EC37DFKY5X6RFQ6XPE9EY","prose","OpenProse VM skill pack. Activate on any `prose` command, .prose files, or OpenProse mentions; orchestrates multi-agent workflows.","https:\u002F\u002Fgithub.com\u002Fpvbang\u002Fnexus\u002Fblob\u002Fmain\u002Fsrc\u002Fopen-source\u002Fopenclaw\u002Fextensions\u002Fopen-prose\u002Fskills\u002Fprose\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fpvbang\u002Fnexus\u002Fblob\u002Fmain\u002Fsrc\u002Fopen-source\u002Fopenclaw\u002Fextensions\u002Fopen-prose\u002Fskills\u002Fprose\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},"01M78E9C2RKT5BJ8ZR9KZTNS2A","writing-plans","Write implementation plans: bite-sized tasks, paths, code.","https:\u002F\u002Fgithub.com\u002Fpvbang\u002Fnexus\u002Fblob\u002Fmain\u002Fsrc\u002Fopen-source\u002Fhermes-agent\u002Fskills\u002Fsoftware-development\u002Fwriting-plans\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},"01M78E98QY8PH80R7QN1P8NMTH","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002Fpvbang\u002Fnexus\u002Fblob\u002Fmain\u002Fsrc\u002Fopen-source\u002Fhermes-agent\u002Fskills\u002Fsoftware-development\u002Ftest-driven-development\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},"01M78E93DGFNKP1WZ9WJ9S9N7H","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002Fpvbang\u002Fnexus\u002Fblob\u002Fmain\u002Fsrc\u002Fopen-source\u002Fhermes-agent\u002Fskills\u002Fsoftware-development\u002Fsystematic-debugging\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},"01M78E8ZM4CER22PJT0WJ1RWMJ","subagent-driven-development","Execute plans via delegate_task subagents (2-stage review).","https:\u002F\u002Fgithub.com\u002Fpvbang\u002Fnexus\u002Fblob\u002Fmain\u002Fsrc\u002Fopen-source\u002Fhermes-agent\u002Fskills\u002Fsoftware-development\u002Fsubagent-driven-development\u002FSKILL.md",[],[]]