[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74FC3G04WE5R620CECEBDWN":3,"skill-same:01M74FC3G04WE5R620CECEBDWN":55},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":13,"repositoryHtmlUrl":38,"repositoryHomepageUrl":6,"ownerHtmlUrl":39,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":40,"install":41,"resources":54},"01M74FC3G04WE5R620CECEBDWN","plan",null,"Plan mode: write markdown plan to .hermes\u002Fplans\u002F, no exec.","LyrikNilpferd71\u002FHermes-Backup","LyrikNilpferd71","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F187173780?v=4","01M727S8GPB77P0S9ECRRMZT58","01M727S8HF63B0MD53F496MK1V",0,"MIT","https:\u002F\u002Fgithub.com\u002FLyrikNilpferd71\u002FHermes-Backup\u002Fblob\u002Fmain\u002Fsnapshots\u002F2026-05-17T14-00-48+0200\u002Fskills\u002Fsoftware-development\u002Fplan\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: plan\ndescription: \"Plan mode: write markdown plan to .hermes\u002Fplans\u002F, no exec.\"\nversion: 1.0.0\nauthor: Hermes Agent\nlicense: MIT\nmetadata:\n  hermes:\n    tags: [planning, plan-mode, implementation, workflow]\n    related_skills: [writing-plans, subagent-driven-development]\n---\n\n# Plan Mode\n\nUse this skill when the user wants a plan instead of execution.\n\n## Core behavior\n\nFor this turn, you are planning only.\n\n- Do not implement code.\n- Do not edit project files except the plan markdown file.\n- Do not run mutating terminal commands, commit, push, or perform external actions.\n- You may inspect the repo or other context with read-only commands\u002Ftools when needed.\n- Your deliverable is a markdown plan saved inside the active workspace under `.hermes\u002Fplans\u002F`.\n\n## Output requirements\n\nWrite a markdown plan that is concrete and actionable.\n\nInclude, when relevant:\n- Goal\n- Current context \u002F assumptions\n- Proposed approach\n- Step-by-step plan\n- Files likely to change\n- Tests \u002F validation\n- Risks, tradeoffs, and open questions\n\nIf the task is code-related, include exact file paths, likely test targets, and verification steps.\n\n## Save location\n\nSave the plan with `write_file` under:\n- `.hermes\u002Fplans\u002FYYYY-MM-DD_HHMMSS-\u003Cslug>.md`\n\nTreat that as relative to the active working directory \u002F backend workspace. Hermes file tools are backend-aware, so using this relative path keeps the plan with the workspace on local, docker, ssh, modal, and daytona backends.\n\nIf the runtime provides a specific target path, use that exact path.\nIf not, create a sensible timestamped filename yourself under `.hermes\u002Fplans\u002F`.\n\n## Interaction style\n\n- If the request is clear enough, write the plan directly.\n- If no explicit instruction accompanies `\u002Fplan`, infer the task from the current conversation context.\n- If it is genuinely underspecified, ask a brief clarifying question instead of guessing.\n- After saving the plan, reply briefly with what you planned and the saved path.\n","# Plan Mode\n\nUse this skill when the user wants a plan instead of execution.\n\n## Core behavior\n\nFor this turn, you are planning only.\n\n- Do not implement code.\n- Do not edit project files except the plan markdown file.\n- Do not run mutating terminal commands, commit, push, or perform external actions.\n- You may inspect the repo or other context with read-only commands\u002Ftools when needed.\n- Your deliverable is a markdown plan saved inside the active workspace under `.hermes\u002Fplans\u002F`.\n\n## Output requirements\n\nWrite a markdown plan that is concrete and actionable.\n\nInclude, when relevant:\n- Goal\n- Current context \u002F assumptions\n- Proposed approach\n- Step-by-step plan\n- Files likely to change\n- Tests \u002F validation\n- Risks, tradeoffs, and open questions\n\nIf the task is code-related, include exact file paths, likely test targets, and verification steps.\n\n## Save location\n\nSave the plan with `write_file` under:\n- `.hermes\u002Fplans\u002FYYYY-MM-DD_HHMMSS-\u003Cslug>.md`\n\nTreat that as relative to the active working directory \u002F backend workspace. Hermes file tools are backend-aware, so using this relative path keeps the plan with the workspace on local, docker, ssh, modal, and daytona backends.\n\nIf the runtime provides a specific target path, use that exact path.\nIf not, create a sensible timestamped filename yourself under `.hermes\u002Fplans\u002F`.\n\n## Interaction style\n\n- If the request is clear enough, write the plan directly.\n- If no explicit instruction accompanies `\u002Fplan`, infer the task from the current conversation context.\n- If it is genuinely underspecified, ask a brief clarifying question instead of guessing.\n- After saving the plan, reply briefly with what you planned and the saved path.\n",{"name":5,"author":23,"license":14,"version":24,"metadata":25,"description":7},"Hermes Agent","1.0.0",{"hermes":26},{"tags":27,"related_skills":32},[28,29,30,31],"planning","plan-mode","implementation","workflow",[33,34],"writing-plans","subagent-driven-development","main","404fd33aabef3b6bc1cc913117ba2160ade62625","snapshots\u002F2026-05-17T14-00-48+0200\u002Fskills\u002Fsoftware-development\u002Fplan","https:\u002F\u002Fgithub.com\u002FLyrikNilpferd71\u002FHermes-Backup","https:\u002F\u002Fgithub.com\u002FLyrikNilpferd71","2026-11-08 20:00:57",{"source":8,"skillName":5,"commands":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add LyrikNilpferd71\u002FHermes-Backup --skill plan",{"tool":47,"command":48},"bunx","bunx skills add LyrikNilpferd71\u002FHermes-Backup --skill plan",{"tool":50,"command":51},"pnpm","pnpm dlx skills add LyrikNilpferd71\u002FHermes-Backup --skill plan","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLyrikNilpferd71\u002FHermes-Backup\u002Fblob\u002Fmain\u002Fsnapshots\u002F2026-05-17T14-00-48+0200\u002Fskills\u002Fsoftware-development\u002Fplan\u002FSKILL.md",true,[],[56,63,70,76,82,89],{"skillNo":57,"name":33,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":62},"01M76BBCCNA7WQ82Q8QNZH8PBK","Write implementation plans: bite-sized tasks, paths, code.","https:\u002F\u002Fgithub.com\u002FLyrikNilpferd71\u002FHermes-Backup\u002Fblob\u002Fmain\u002Fsnapshots\u002F2026-11-08T13-00-51+0100\u002Fskills\u002Fsoftware-development\u002Fwriting-plans\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":62},"01M76BB8YS41CA3NKW0YMSSB88","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002FLyrikNilpferd71\u002FHermes-Backup\u002Fblob\u002Fmain\u002Fsnapshots\u002F2026-11-08T13-00-51+0100\u002Fskills\u002Fsoftware-development\u002Fsystematic-debugging\u002FSKILL.md",[],[],{"skillNo":71,"name":34,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":62},"01M76BB680FPNT998E1GM2QW10","Execute plans via delegate_task subagents (2-stage review).","https:\u002F\u002Fgithub.com\u002FLyrikNilpferd71\u002FHermes-Backup\u002Fblob\u002Fmain\u002Fsnapshots\u002F2026-11-08T13-00-51+0100\u002Fskills\u002Fsoftware-development\u002Fsubagent-driven-development\u002FSKILL.md",[],[],{"skillNo":77,"name":5,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":62},"01M76BB3C4ZB9S4RWPMM8MX0YB","Write a markdown plan to .hermes\u002Fplans\u002F; no execution.","https:\u002F\u002Fgithub.com\u002FLyrikNilpferd71\u002FHermes-Backup\u002Fblob\u002Fmain\u002Fsnapshots\u002F2026-11-08T13-00-51+0100\u002Fskills\u002Fsoftware-development\u002Fplan\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":62},"01M76BB0NK28KMP51YDB5R3EXA","hermes-agent-skill-authoring","Author in-repo SKILL.md files: frontmatter and structure.","https:\u002F\u002Fgithub.com\u002FLyrikNilpferd71\u002FHermes-Backup\u002Fblob\u002Fmain\u002Fsnapshots\u002F2026-11-08T13-00-51+0100\u002Fskills\u002Fsoftware-development\u002Fhermes-agent-skill-authoring\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":62},"01M76BAYV58H0CKNSTZE3ZH4NY","debugging-hermes-tui-commands","Debug Hermes TUI slash commands: Python, gateway, Ink UI.","https:\u002F\u002Fgithub.com\u002FLyrikNilpferd71\u002FHermes-Backup\u002Fblob\u002Fmain\u002Fsnapshots\u002F2026-11-08T13-00-51+0100\u002Fskills\u002Fsoftware-development\u002Fdebugging-hermes-tui-commands\u002FSKILL.md",[],[]]