[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CP1MT0R9XYF8GC7WRWRCX5":3,"skill-same:01M7CP1MT0R9XYF8GC7WRWRCX5":66},{"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":38,"commitSha":39,"skillDirectory":40,"forksCount":41,"repositoryHtmlUrl":42,"repositoryHomepageUrl":6,"ownerHtmlUrl":43,"ownerBlogUrl":6,"ownerDescription":44,"updatedAt":45,"install":46,"resources":59},"01M7CP1MT0R9XYF8GC7WRWRCX5","installing-external-skills",null,"Use when installing external skills into Hermes. Organize.","iwindd\u002Fugh-cloud","iwindd","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F134185860?v=4","01M7CNSVBBZRNZPXFMTMCKMG0M","Achirawit Kaewkhong","01M7CNSVCBZK36SE7MBEE0Q3V0",1,"MIT","https:\u002F\u002Fgithub.com\u002Fiwindd\u002Fugh-cloud\u002Fblob\u002Fmain\u002Fagents\u002Flyla\u002Fskills\u002Fsoftware-development\u002Finstalling-external-skills\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\r\nname: installing-external-skills\r\ndescription: \"Use when installing external skills into Hermes. Organize.\"\r\nversion: 1.0.0\r\nauthor: Hermes Agent\r\nlicense: MIT\r\nplatforms: [windows, macos, linux]\r\nmetadata:\r\n  hermes:\r\n    tags: [hermes, skills, installation, profiles, organization]\r\n---\r\n\r\n# Installing External Skills into Hermes\r\n\r\nInstall external skill collections into the active Hermes profile, preserve their support files, organize them by task class, and verify that Hermes can load them.\r\n\r\n## Procedure\r\n\r\n1. Identify the active profile before writing anything. Resolve `$HERMES_HOME`; never assume `~\u002F.hermes` when a profile is active. Treat `$HERMES_HOME\u002Fskills\u002F` as the target library.\r\n\r\n2. Read the publisher's installation instructions and identify the canonical source repository. Prefer the repository named by the publisher over a copied web page or a third-party mirror. Record the source commit after fetching it.\r\n\r\n3. Discover the collection before installing it. Use the publisher's installer with its listing mode, or inspect the repository's `skills\u002F` tree. Count the discovered `SKILL.md` files and note the source category of every skill.\r\n\r\n4. Try the supported installer only when its destination is compatible with Hermes. For the Skills CLI, the canonical package form is `npx skills@latest add \u003Cowner>\u002F\u003Crepo>`. Use `--all` only when the user wants the complete collection, and use `--copy` when editable, self-contained files are preferred over links.\r\n\r\n5. If the installer reports that global installation is unsupported or places files outside the active Hermes profile, fetch the canonical repository and copy each skill directory into `$HERMES_HOME\u002Fskills\u002F\u003CHermes category>\u002F\u003Cskill-name>\u002F`. Preserve `SKILL.md`, `references\u002F`, `templates\u002F`, `scripts\u002F`, and other support files; do not flatten a skill into one file.\r\n\r\n6. Map source categories to Hermes categories by task class, not by publisher directory name. Put engineering workflows and code utilities under `software-development`; put general planning, writing, teaching, and handoff workflows under `productivity`. Consult `references\u002Fcategory-mapping.md` for the default mapping and adjust only when the skill's actual trigger warrants it.\r\n\r\n7. Before deleting unscoped or duplicate manifests, confirm the categorized copy exists and is complete. Remove only files created by the current installation; never delete bundled, hub-installed, pinned, externally owned, or user-owned skills. Leave unrelated directories untouched.\r\n\r\n8. Verify the result with `hermes skills list`. Confirm every intended skill is enabled, the count matches the discovered collection plus pre-existing local skills, and no duplicate name makes lookup ambiguous. Use `hermes doctor` only as a secondary profile\u002Fdirectory check; do not treat unrelated credential or package warnings as installation failures.\r\n\r\n9. Report the target profile path, source repository and commit, number installed, category placement, and any unresolved cleanup or installer limitation plainly. Do not claim success from a command exit code alone; base the report on the final Hermes listing.\r\n\r\n## Durable pitfalls\r\n\r\n- Use the active `$HERMES_HOME`, not the default profile path — Hermes profiles isolate their skills and a correct install in another profile is invisible here.\r\n- Preserve the whole skill directory — support files hold procedures and templates that `SKILL.md` references at runtime.\r\n- Organize by task class and keep one canonical copy — unscoped duplicates create ambiguous skill resolution and make future updates target the wrong file.\r\n- Treat installer summaries as provisional — an installer can clone a repository while failing to link or register files for a specific agent, so verify with Hermes itself.\r\n- Keep source provenance beside the installation notes or report — a commit identifies exactly which external instructions were imported when the upstream collection changes.\r\n\r\nA deeper source-to-Hermes category decision table is in `references\u002Fcategory-mapping.md`.\r\n","# Installing External Skills into Hermes\r\n\r\nInstall external skill collections into the active Hermes profile, preserve their support files, organize them by task class, and verify that Hermes can load them.\r\n\r\n## Procedure\r\n\r\n1. Identify the active profile before writing anything. Resolve `$HERMES_HOME`; never assume `~\u002F.hermes` when a profile is active. Treat `$HERMES_HOME\u002Fskills\u002F` as the target library.\r\n\r\n2. Read the publisher's installation instructions and identify the canonical source repository. Prefer the repository named by the publisher over a copied web page or a third-party mirror. Record the source commit after fetching it.\r\n\r\n3. Discover the collection before installing it. Use the publisher's installer with its listing mode, or inspect the repository's `skills\u002F` tree. Count the discovered `SKILL.md` files and note the source category of every skill.\r\n\r\n4. Try the supported installer only when its destination is compatible with Hermes. For the Skills CLI, the canonical package form is `npx skills@latest add \u003Cowner>\u002F\u003Crepo>`. Use `--all` only when the user wants the complete collection, and use `--copy` when editable, self-contained files are preferred over links.\r\n\r\n5. If the installer reports that global installation is unsupported or places files outside the active Hermes profile, fetch the canonical repository and copy each skill directory into `$HERMES_HOME\u002Fskills\u002F\u003CHermes category>\u002F\u003Cskill-name>\u002F`. Preserve `SKILL.md`, `references\u002F`, `templates\u002F`, `scripts\u002F`, and other support files; do not flatten a skill into one file.\r\n\r\n6. Map source categories to Hermes categories by task class, not by publisher directory name. Put engineering workflows and code utilities under `software-development`; put general planning, writing, teaching, and handoff workflows under `productivity`. Consult `references\u002Fcategory-mapping.md` for the default mapping and adjust only when the skill's actual trigger warrants it.\r\n\r\n7. Before deleting unscoped or duplicate manifests, confirm the categorized copy exists and is complete. Remove only files created by the current installation; never delete bundled, hub-installed, pinned, externally owned, or user-owned skills. Leave unrelated directories untouched.\r\n\r\n8. Verify the result with `hermes skills list`. Confirm every intended skill is enabled, the count matches the discovered collection plus pre-existing local skills, and no duplicate name makes lookup ambiguous. Use `hermes doctor` only as a secondary profile\u002Fdirectory check; do not treat unrelated credential or package warnings as installation failures.\r\n\r\n9. Report the target profile path, source repository and commit, number installed, category placement, and any unresolved cleanup or installer limitation plainly. Do not claim success from a command exit code alone; base the report on the final Hermes listing.\r\n\r\n## Durable pitfalls\r\n\r\n- Use the active `$HERMES_HOME`, not the default profile path — Hermes profiles isolate their skills and a correct install in another profile is invisible here.\r\n- Preserve the whole skill directory — support files hold procedures and templates that `SKILL.md` references at runtime.\r\n- Organize by task class and keep one canonical copy — unscoped duplicates create ambiguous skill resolution and make future updates target the wrong file.\r\n- Treat installer summaries as provisional — an installer can clone a repository while failing to link or register files for a specific agent, so verify with Hermes itself.\r\n- Keep source provenance beside the installation notes or report — a commit identifies exactly which external instructions were imported when the upstream collection changes.\r\n\r\nA deeper source-to-Hermes category decision table is in `references\u002Fcategory-mapping.md`.\r\n",{"name":5,"author":24,"license":15,"version":25,"metadata":26,"platforms":34,"description":7},"Hermes Agent","1.0.0",{"hermes":27},{"tags":28},[29,30,31,32,33],"hermes","skills","installation","profiles","organization",[35,36,37],"windows","macos","linux","main","4d224ae3f890cda32343a34d262a5ddc406784f2","agents\u002Flyla\u002Fskills\u002Fsoftware-development\u002Finstalling-external-skills",0,"https:\u002F\u002Fgithub.com\u002Fiwindd\u002Fugh-cloud","https:\u002F\u002Fgithub.com\u002Fiwindd","Hi. Hi. Hi.","2026-09-13 07:57:16",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add iwindd\u002Fugh-cloud --skill installing-external-skills",{"tool":52,"command":53},"bunx","bunx skills add iwindd\u002Fugh-cloud --skill installing-external-skills",{"tool":55,"command":56},"pnpm","pnpm dlx skills add iwindd\u002Fugh-cloud --skill installing-external-skills","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fiwindd\u002Fugh-cloud\u002Fblob\u002Fmain\u002Fagents\u002Flyla\u002Fskills\u002Fsoftware-development\u002Finstalling-external-skills\u002FSKILL.md",true,[60],{"path":61,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fcategory-mapping.md","REFERENCE","参考文档",1465,"https:\u002F\u002Fgithub.com\u002Fiwindd\u002Fugh-cloud\u002Fblob\u002Fmain\u002Fagents\u002Flyla\u002Fskills\u002Fsoftware-development\u002Finstalling-external-skills\u002Freferences\u002Fcategory-mapping.md",[67,74,81,88,95,102],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7CP42B6WAVRJJ1N3HYEQ8YH","blocked-page-recovery","Use when a fetch fails: 403\u002F429, paywall, WAF, bot wall.","https:\u002F\u002Fgithub.com\u002Fiwindd\u002Fugh-cloud\u002Fblob\u002Fmain\u002Fagents\u002Flyla\u002Fskills\u002Fweb\u002Fblocked-page-recovery\u002FSKILL.md",[],[],{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7CP3F6PTEZTNHXGV876JA22","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002Fiwindd\u002Fugh-cloud\u002Fblob\u002Fmain\u002Fagents\u002Flyla\u002Fskills\u002Fsoftware-development\u002Ftest-driven-development\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7CP373VVYP86Y253EWHEGAX","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002Fiwindd\u002Fugh-cloud\u002Fblob\u002Fmain\u002Fagents\u002Flyla\u002Fskills\u002Fsoftware-development\u002Fsystematic-debugging\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7CP33QGVW5X4HQ640S16RDN","spike","Throwaway experiments to validate an idea before build.","https:\u002F\u002Fgithub.com\u002Fiwindd\u002Fugh-cloud\u002Fblob\u002Fmain\u002Fagents\u002Flyla\u002Fskills\u002Fsoftware-development\u002Fspike\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M7CP30ZYZTSETAR194G5YXV1","simplify-code","Parallel 4-agent cleanup of recent code changes.","https:\u002F\u002Fgithub.com\u002Fiwindd\u002Fugh-cloud\u002Fblob\u002Fmain\u002Fagents\u002Flyla\u002Fskills\u002Fsoftware-development\u002Fsimplify-code\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":19},"01M7CP2AQD1JCVGRB7NV0M1A8Y","requesting-code-review","Pre-commit review: security scan, quality gates, auto-fix.","https:\u002F\u002Fgithub.com\u002Fiwindd\u002Fugh-cloud\u002Fblob\u002Fmain\u002Fagents\u002Flyla\u002Fskills\u002Fsoftware-development\u002Frequesting-code-review\u002FSKILL.md",[],[]]