[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M737XZQXP414HJSZ17DT4WW5":3,"skill-same:01M737XZQXP414HJSZ17DT4WW5":58},{"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":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":43,"install":44,"resources":57},"01M737XZQXP414HJSZ17DT4WW5","obsidian",null,"Read, search, create, and edit notes in the Obsidian vault.","ashneil12\u002Fvanilla-hermes-agent-canary","ashneil12","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F49880658?v=4","01M7378BQ9W161EPENEWBYAQNN","01M7378BRDJG8SFS93FG4V6BWY",1,"MIT","https:\u002F\u002Fgithub.com\u002Fashneil12\u002Fvanilla-hermes-agent-canary\u002Fblob\u002Fmain\u002Fskills\u002Fnote-taking\u002Fobsidian\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: obsidian\ndescription: Read, search, create, and edit notes in the Obsidian vault.\nversion: 1.0.0\nauthor: Teknium (teknium1), Hermes Agent\nlicense: MIT\nplatforms: [linux, macos, windows]\nmetadata:\n  hermes:\n    tags: [Obsidian, Notes, Markdown, Vault]\n    related_skills: []\n---\n\n# Obsidian Vault\n\nUse this skill for filesystem-first Obsidian vault work: reading notes, listing notes, searching note files, creating notes, appending content, and adding wikilinks.\n\n## Vault path\n\nUse a known or resolved vault path before calling file tools.\n\nThe documented vault-path convention is the `OBSIDIAN_VAULT_PATH` environment variable, for example from `${HERMES_HOME:-~\u002F.hermes}\u002F.env`. If it is unset, use `~\u002FDocuments\u002FObsidian Vault`.\n\nFile tools do not expand shell variables. Do not pass paths containing `$OBSIDIAN_VAULT_PATH` to `read_file`, `write_file`, `patch`, or `search_files`; resolve the vault path first and pass a concrete absolute path. Vault paths may contain spaces, which is another reason to prefer file tools over shell commands.\n\nIf the vault path is unknown, `terminal` is acceptable for resolving `OBSIDIAN_VAULT_PATH` or checking whether the fallback path exists. Once the path is known, switch back to file tools.\n\n## Read a note\n\nUse `read_file` with the resolved absolute path to the note. Prefer this over `cat` because it provides line numbers and pagination.\n\n## List notes\n\nUse `search_files` with `target: \"files\"` and the resolved vault path. Prefer this over `find` or `ls`.\n\n- To list all markdown notes, use `pattern: \"*.md\"` under the vault path.\n- To list a subfolder, search under that subfolder's absolute path.\n\n## Search\n\nUse `search_files` for both filename and content searches. Prefer this over `grep`, `find`, or `ls`.\n\n- For filenames, use `search_files` with `target: \"files\"` and a filename `pattern`.\n- For note contents, use `search_files` with `target: \"content\"`, the content regex as `pattern`, and `file_glob: \"*.md\"` when you want to restrict matches to markdown notes.\n\n## Create a note\n\nUse `write_file` with the resolved absolute path and the full markdown content. Prefer this over shell heredocs or `echo` because it avoids shell quoting issues and returns structured results.\n\n## Append to a note\n\nPrefer a native file-tool workflow when it is not awkward:\n\n- Read the target note with `read_file`.\n- Use `patch` for an anchored append when there is stable context, such as adding a section after an existing heading or appending before a known trailing block.\n- Use `write_file` when rewriting the whole note is clearer than constructing a fragile patch.\n\nFor an anchored append with `patch`, replace the anchor with the anchor plus the new content.\n\nFor a simple append with no stable context, `terminal` is acceptable if it is the clearest safe option.\n\n## Targeted edits\n\nUse `patch` for focused note changes when the current content gives you stable context. Prefer this over shell text rewriting.\n\n## Wikilinks\n\nObsidian links notes with `[[Note Name]]` syntax. When creating notes, use these to link related content.\n","# Obsidian Vault\n\nUse this skill for filesystem-first Obsidian vault work: reading notes, listing notes, searching note files, creating notes, appending content, and adding wikilinks.\n\n## Vault path\n\nUse a known or resolved vault path before calling file tools.\n\nThe documented vault-path convention is the `OBSIDIAN_VAULT_PATH` environment variable, for example from `${HERMES_HOME:-~\u002F.hermes}\u002F.env`. If it is unset, use `~\u002FDocuments\u002FObsidian Vault`.\n\nFile tools do not expand shell variables. Do not pass paths containing `$OBSIDIAN_VAULT_PATH` to `read_file`, `write_file`, `patch`, or `search_files`; resolve the vault path first and pass a concrete absolute path. Vault paths may contain spaces, which is another reason to prefer file tools over shell commands.\n\nIf the vault path is unknown, `terminal` is acceptable for resolving `OBSIDIAN_VAULT_PATH` or checking whether the fallback path exists. Once the path is known, switch back to file tools.\n\n## Read a note\n\nUse `read_file` with the resolved absolute path to the note. Prefer this over `cat` because it provides line numbers and pagination.\n\n## List notes\n\nUse `search_files` with `target: \"files\"` and the resolved vault path. Prefer this over `find` or `ls`.\n\n- To list all markdown notes, use `pattern: \"*.md\"` under the vault path.\n- To list a subfolder, search under that subfolder's absolute path.\n\n## Search\n\nUse `search_files` for both filename and content searches. Prefer this over `grep`, `find`, or `ls`.\n\n- For filenames, use `search_files` with `target: \"files\"` and a filename `pattern`.\n- For note contents, use `search_files` with `target: \"content\"`, the content regex as `pattern`, and `file_glob: \"*.md\"` when you want to restrict matches to markdown notes.\n\n## Create a note\n\nUse `write_file` with the resolved absolute path and the full markdown content. Prefer this over shell heredocs or `echo` because it avoids shell quoting issues and returns structured results.\n\n## Append to a note\n\nPrefer a native file-tool workflow when it is not awkward:\n\n- Read the target note with `read_file`.\n- Use `patch` for an anchored append when there is stable context, such as adding a section after an existing heading or appending before a known trailing block.\n- Use `write_file` when rewriting the whole note is clearer than constructing a fragile patch.\n\nFor an anchored append with `patch`, replace the anchor with the anchor plus the new content.\n\nFor a simple append with no stable context, `terminal` is acceptable if it is the clearest safe option.\n\n## Targeted edits\n\nUse `patch` for focused note changes when the current content gives you stable context. Prefer this over shell text rewriting.\n\n## Wikilinks\n\nObsidian links notes with `[[Note Name]]` syntax. When creating notes, use these to link related content.\n",{"name":5,"author":23,"license":14,"version":24,"metadata":25,"platforms":33,"description":7},"Teknium (teknium1), Hermes Agent","1.0.0",{"hermes":26},{"tags":27,"related_skills":32},[28,29,30,31],"Obsidian","Notes","Markdown","Vault",[],[34,35,36],"linux","macos","windows","main","0905b0264ce5a54908bedc9637e50251543db132","skills\u002Fnote-taking\u002Fobsidian",0,"https:\u002F\u002Fgithub.com\u002Fashneil12\u002Fvanilla-hermes-agent-canary","https:\u002F\u002Fgithub.com\u002Fashneil12","2026-11-04 08:25:00",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add ashneil12\u002Fvanilla-hermes-agent-canary --skill obsidian",{"tool":50,"command":51},"bunx","bunx skills add ashneil12\u002Fvanilla-hermes-agent-canary --skill obsidian",{"tool":53,"command":54},"pnpm","pnpm dlx skills add ashneil12\u002Fvanilla-hermes-agent-canary --skill obsidian","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fashneil12\u002Fvanilla-hermes-agent-canary\u002Fblob\u002Fmain\u002Fskills\u002Fnote-taking\u002Fobsidian\u002FSKILL.md",true,[],[59,66,73,80,87,94],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M7380YR13A23353XT9NS6EGR","blocked-page-recovery","Use when a fetch fails: 403\u002F429, paywall, WAF, bot wall.","https:\u002F\u002Fgithub.com\u002Fashneil12\u002Fvanilla-hermes-agent-canary\u002Fblob\u002Fmain\u002Fskills\u002Fweb\u002Fblocked-page-recovery\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M7380VZ8P60Q64J3F92D4AMY","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002Fashneil12\u002Fvanilla-hermes-agent-canary\u002Fblob\u002Fmain\u002Fskills\u002Fsoftware-development\u002Ftest-driven-development\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M7380QXN6F90R0MH1M3FHRKX","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002Fashneil12\u002Fvanilla-hermes-agent-canary\u002Fblob\u002Fmain\u002Fskills\u002Fsoftware-development\u002Fsystematic-debugging\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M7380N4BZYT2WRRZN1N9DZ65","spike","Throwaway experiments to validate an idea before build.","https:\u002F\u002Fgithub.com\u002Fashneil12\u002Fvanilla-hermes-agent-canary\u002Fblob\u002Fmain\u002Fskills\u002Fsoftware-development\u002Fspike\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":18},"01M7380JAEC9ZH5DVPHHK56P97","simplify-code","Parallel 4-agent cleanup of recent code changes.","https:\u002F\u002Fgithub.com\u002Fashneil12\u002Fvanilla-hermes-agent-canary\u002Fblob\u002Fmain\u002Fskills\u002Fsoftware-development\u002Fsimplify-code\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":18},"01M7380F5MBB7FKWWV3G3TZ193","requesting-code-review","Pre-commit review: security scan, quality gates, auto-fix.","https:\u002F\u002Fgithub.com\u002Fashneil12\u002Fvanilla-hermes-agent-canary\u002Fblob\u002Fmain\u002Fskills\u002Fsoftware-development\u002Frequesting-code-review\u002FSKILL.md",[],[]]