[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7317G3HEMXD6DBZ1SAXAAJM":3,"skill-same:01M7317G3HEMXD6DBZ1SAXAAJM":50},{"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":28,"commitSha":29,"skillDirectory":30,"forksCount":31,"repositoryHtmlUrl":32,"repositoryHomepageUrl":33,"ownerHtmlUrl":34,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":35,"install":36,"resources":49},"01M7317G3HEMXD6DBZ1SAXAAJM","obsidian",null,"Read, search, create, and edit notes in the Obsidian vault.","StarryCod\u002Fcogitum","StarryCod","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F200964623?v=4","01M7311AM3RY259SYKGHWBEDN0","OpenReason","01M7311AMRC1PBSTYZWSD1AQFJ",12,"MIT","https:\u002F\u002Fgithub.com\u002FStarryCod\u002Fcogitum\u002Fblob\u002Fmaster\u002Fcogitum\u002Fdata\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.\nplatforms: [linux, macos, windows]\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 `~\u002F.config\u002Fcogitum\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 `~\u002F.config\u002Fcogitum\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,"platforms":24,"description":7},[25,26,27],"linux","macos","windows","master","a99de210a5d82a24b7aa5020afa1f904f595d14c","cogitum\u002Fdata\u002Fskills\u002Fnote-taking\u002Fobsidian",0,"https:\u002F\u002Fgithub.com\u002FStarryCod\u002Fcogitum","https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fcogitum","https:\u002F\u002Fgithub.com\u002FStarryCod","2026-05-25 23:49:07",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add StarryCod\u002Fcogitum --skill obsidian",{"tool":42,"command":43},"bunx","bunx skills add StarryCod\u002Fcogitum --skill obsidian",{"tool":45,"command":46},"pnpm","pnpm dlx skills add StarryCod\u002Fcogitum --skill obsidian","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FStarryCod\u002Fcogitum\u002Fblob\u002Fmaster\u002Fcogitum\u002Fdata\u002Fskills\u002Fnote-taking\u002Fobsidian\u002FSKILL.md",true,[],[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M731AYJQFFAGEQ8T8NMPKM72","yuanbao","Yuanbao (元宝) groups: @mention users, query info\u002Fmembers.","https:\u002F\u002Fgithub.com\u002FStarryCod\u002Fcogitum\u002Fblob\u002Fmaster\u002Fcogitum\u002Fdata\u002Fskills\u002Fyuanbao\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M731AWAHBZQ4JG5HBRXSTEWP","tg-moderator","Telegram chat moderator\u002Fcompanion mode. No tools, conversational only.","https:\u002F\u002Fgithub.com\u002FStarryCod\u002Fcogitum\u002Fblob\u002Fmaster\u002Fcogitum\u002Fdata\u002Fskills\u002Ftg-moderator\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M731AS9N89S2E50MSW2Y9QYY","writing-plans","Write implementation plans: bite-sized tasks, paths, code.","https:\u002F\u002Fgithub.com\u002FStarryCod\u002Fcogitum\u002Fblob\u002Fmaster\u002Fcogitum\u002Fdata\u002Fskills\u002Fsoftware-development\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M731ANESTYGBFV3XSAT0AS8Q","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002FStarryCod\u002Fcogitum\u002Fblob\u002Fmaster\u002Fcogitum\u002Fdata\u002Fskills\u002Fsoftware-development\u002Ftest-driven-development\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":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M731AG1KE7ZHM0P1R890ZVB0","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002FStarryCod\u002Fcogitum\u002Fblob\u002Fmaster\u002Fcogitum\u002Fdata\u002Fskills\u002Fsoftware-development\u002Fsystematic-debugging\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M731ABWQ3DTCBY8E6WTYSBTT","subagent-driven-development","Execute plans via delegate_task subagents (2-stage review).","https:\u002F\u002Fgithub.com\u002FStarryCod\u002Fcogitum\u002Fblob\u002Fmaster\u002Fcogitum\u002Fdata\u002Fskills\u002Fsoftware-development\u002Fsubagent-driven-development\u002FSKILL.md",[],[]]