[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70FW95K6BD12KQERZS0FWHW":3,"skill-same:01M70FW95K6BD12KQERZS0FWHW":73},{"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":26,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":58,"install":59,"resources":72},"01M70FW95K6BD12KQERZS0FWHW","obsidian-cli",null,"Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more. Also supports plugin and theme development with commands to reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM. Use when the user asks to interact with their Obsidian vault, manage notes, search vault content, perform vault operations from the command line, or develop and debug Obsidian plugins and themes.","JayJiangCT\u002Fknowlery","JayJiangCT","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F59813406?v=4","01M70FV52GQJT4F12FBSYG48R2","Jay Jiang","01M70FV536R3NCMG5ZB0TMEWNP",15,"MIT","https:\u002F\u002Fgithub.com\u002FJayJiangCT\u002Fknowlery\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fobsidian-cli\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000036","内容创作者",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"cli","obsidian cli","obsidian","theme","screenshots","vaults","take","commands","read","line","run","command","notes","create","tasks","when","themes","errors","search","inspect","2026-11-10 10:12:30",false,"---\nname: obsidian-cli\ndescription: Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more. Also supports plugin and theme development with commands to reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM. Use when the user asks to interact with their Obsidian vault, manage notes, search vault content, perform vault operations from the command line, or develop and debug Obsidian plugins and themes.\n---\n\n# Obsidian CLI\n\nUse the `obsidian` CLI to interact with a running Obsidian instance. Requires Obsidian to be open.\n\n## Command reference\n\nRun `obsidian help` to see all available commands. This is always up to date. Full docs: https:\u002F\u002Fhelp.obsidian.md\u002Fcli\n\nNever run `obsidian` with no command — a bare call opens an interactive TUI\nmeant for humans, and is field-observed to leave a blank `Untitled.md` in\nthe vault.\n\nA blank note is provably tool debris only when your own bare call just\ncreated it: you ran the call this session, the file did not exist before it\n(check creation time), and it is empty. Only then run\n`obsidian delete path=\"Untitled.md\"` (trashes by default), and verify with\n`obsidian read path=\"Untitled.md\"` that the output reports not found — bare\n`obsidian read` reads the active file, and the CLI can print an error while\nexiting 0, so trust the not-found output or a filesystem existence check,\nnever the exit code. If any condition is unproven — the note predates your\ncall or has content — leave it and ask the user. Never leave CLI side\neffects in the vault, and never guess a user's note into the trash either.\n\n## Syntax\n\n**Parameters** take a value with `=`. Quote values with spaces:\n\n```bash\nobsidian create name=\"My Note\" content=\"Hello world\"\n```\n\n**Flags** are boolean switches with no value:\n\n```bash\nobsidian create name=\"My Note\" silent overwrite\n```\n\nFor multiline content use `\\n` for newline and `\\t` for tab.\n\n## Writing long or complex content\n\n`content=` is a **single shell-quoted argument**, and three bash hazards apply\ninside it: backticks run as command substitution, `$` expands variables, and\nnested double quotes end the argument. Any page carrying a code fence, LaTeX,\nor quoted prose will usually break the command or corrupt the written content —\non top of the `\\n` escaping that multiline content already needs.\n\n- **Short content** (a heading, a line or two): `obsidian create` \u002F `obsidian append` are fine.\n- **Full pages** (frontmatter + body, Mermaid or other charts, code fences,\n  tables): write the `.md` file directly with your file tools — Obsidian\n  indexes new files automatically — then verify with `obsidian read path=\"...\"`.\n- Always pass `path=\"dir\u002Fnote.md\"` when the note must land in a specific folder;\n  `name=` resolves like a wikilink and uses the default new-note location.\n- If `create` fails once on escaping, switch to a direct file write; do not retry\n  with more escaping.\n\n## File targeting\n\nMany commands accept `file` or `path` to target a file. Without either, the active file is used.\n\n- `file=\u003Cname>` — resolves like a wikilink (name only, no path or extension needed)\n- `path=\u003Cpath>` — exact path from vault root, e.g. `folder\u002Fnote.md`\n\nDot-directories (`.claude\u002F`, `.knowlery\u002F`, `.agents\u002F`, `.obsidian\u002F`) are\noutside Obsidian's vault index. File-targeting commands that depend on that\nindex — including `read` and `create`, even with `path=` — cannot reach\nthem. Read or write those paths directly with your file tools. This is an\nexpected boundary; do not retry the Obsidian CLI. The CLI may print an\n`Error:` while still exiting with status 0, so require a `Created: \u003Cpath>`\nresult and verify important writes.\n\n## Vault targeting\n\nCommands target the most recently focused vault by default. Use `vault=\u003Cname>` as the first parameter to target a specific vault:\n\n```bash\nobsidian vault=\"My Vault\" search query=\"test\"\n```\n\n## Common patterns\n\n```bash\nobsidian read file=\"My Note\"\nobsidian create name=\"New Note\" content=\"# Hello\" template=\"Template\" silent\nobsidian append file=\"My Note\" content=\"New line\"\nobsidian rename file=\"old-path.md\" new_name=\"new-path.md\"\nobsidian search query=\"search term\" limit=10\nobsidian search:context query=\"search term\"\nobsidian daily:read\nobsidian daily:append content=\"- [ ] New task\"\nobsidian property:set name=\"status\" value=\"done\" file=\"My Note\"\nobsidian tasks daily todo\nobsidian tags sort=count counts\nobsidian backlinks file=\"My Note\"\n```\n\nUse `--copy` on any command to copy output to clipboard. Use `silent` to prevent files from opening. Use `total` on list commands to get a count.\n\n## Plugin development\n\n### Develop\u002Ftest cycle\n\nAfter making code changes to a plugin or theme, follow this workflow:\n\n1. **Reload** the plugin to pick up changes:\n   ```bash\n   obsidian plugin:reload id=my-plugin\n   ```\n2. **Check for errors** — if errors appear, fix and repeat from step 1:\n   ```bash\n   obsidian dev:errors\n   ```\n3. **Verify visually** with a screenshot or DOM inspection:\n   ```bash\n   obsidian dev:screenshot path=screenshot.png\n   obsidian dev:dom selector=\".workspace-leaf\" text\n   ```\n4. **Check console output** for warnings or unexpected logs:\n   ```bash\n   obsidian dev:console level=error\n   ```\n\n### Additional developer commands\n\nRun JavaScript in the app context:\n\n```bash\nobsidian eval code=\"app.vault.getFiles().length\"\n```\n\nInspect CSS values:\n\n```bash\nobsidian dev:css selector=\".workspace-leaf\" prop=background-color\n```\n\nToggle mobile emulation:\n\n```bash\nobsidian dev:mobile on\n```\n\nRun `obsidian help` to see additional developer commands including CDP and debugger controls.\n","# Obsidian CLI\n\nUse the `obsidian` CLI to interact with a running Obsidian instance. Requires Obsidian to be open.\n\n## Command reference\n\nRun `obsidian help` to see all available commands. This is always up to date. Full docs: https:\u002F\u002Fhelp.obsidian.md\u002Fcli\n\nNever run `obsidian` with no command — a bare call opens an interactive TUI\nmeant for humans, and is field-observed to leave a blank `Untitled.md` in\nthe vault.\n\nA blank note is provably tool debris only when your own bare call just\ncreated it: you ran the call this session, the file did not exist before it\n(check creation time), and it is empty. Only then run\n`obsidian delete path=\"Untitled.md\"` (trashes by default), and verify with\n`obsidian read path=\"Untitled.md\"` that the output reports not found — bare\n`obsidian read` reads the active file, and the CLI can print an error while\nexiting 0, so trust the not-found output or a filesystem existence check,\nnever the exit code. If any condition is unproven — the note predates your\ncall or has content — leave it and ask the user. Never leave CLI side\neffects in the vault, and never guess a user's note into the trash either.\n\n## Syntax\n\n**Parameters** take a value with `=`. Quote values with spaces:\n\n```bash\nobsidian create name=\"My Note\" content=\"Hello world\"\n```\n\n**Flags** are boolean switches with no value:\n\n```bash\nobsidian create name=\"My Note\" silent overwrite\n```\n\nFor multiline content use `\\n` for newline and `\\t` for tab.\n\n## Writing long or complex content\n\n`content=` is a **single shell-quoted argument**, and three bash hazards apply\ninside it: backticks run as command substitution, `$` expands variables, and\nnested double quotes end the argument. Any page carrying a code fence, LaTeX,\nor quoted prose will usually break the command or corrupt the written content —\non top of the `\\n` escaping that multiline content already needs.\n\n- **Short content** (a heading, a line or two): `obsidian create` \u002F `obsidian append` are fine.\n- **Full pages** (frontmatter + body, Mermaid or other charts, code fences,\n  tables): write the `.md` file directly with your file tools — Obsidian\n  indexes new files automatically — then verify with `obsidian read path=\"...\"`.\n- Always pass `path=\"dir\u002Fnote.md\"` when the note must land in a specific folder;\n  `name=` resolves like a wikilink and uses the default new-note location.\n- If `create` fails once on escaping, switch to a direct file write; do not retry\n  with more escaping.\n\n## File targeting\n\nMany commands accept `file` or `path` to target a file. Without either, the active file is used.\n\n- `file=\u003Cname>` — resolves like a wikilink (name only, no path or extension needed)\n- `path=\u003Cpath>` — exact path from vault root, e.g. `folder\u002Fnote.md`\n\nDot-directories (`.claude\u002F`, `.knowlery\u002F`, `.agents\u002F`, `.obsidian\u002F`) are\noutside Obsidian's vault index. File-targeting commands that depend on that\nindex — including `read` and `create`, even with `path=` — cannot reach\nthem. Read or write those paths directly with your file tools. This is an\nexpected boundary; do not retry the Obsidian CLI. The CLI may print an\n`Error:` while still exiting with status 0, so require a `Created: \u003Cpath>`\nresult and verify important writes.\n\n## Vault targeting\n\nCommands target the most recently focused vault by default. Use `vault=\u003Cname>` as the first parameter to target a specific vault:\n\n```bash\nobsidian vault=\"My Vault\" search query=\"test\"\n```\n\n## Common patterns\n\n```bash\nobsidian read file=\"My Note\"\nobsidian create name=\"New Note\" content=\"# Hello\" template=\"Template\" silent\nobsidian append file=\"My Note\" content=\"New line\"\nobsidian rename file=\"old-path.md\" new_name=\"new-path.md\"\nobsidian search query=\"search term\" limit=10\nobsidian search:context query=\"search term\"\nobsidian daily:read\nobsidian daily:append content=\"- [ ] New task\"\nobsidian property:set name=\"status\" value=\"done\" file=\"My Note\"\nobsidian tasks daily todo\nobsidian tags sort=count counts\nobsidian backlinks file=\"My Note\"\n```\n\nUse `--copy` on any command to copy output to clipboard. Use `silent` to prevent files from opening. Use `total` on list commands to get a count.\n\n## Plugin development\n\n### Develop\u002Ftest cycle\n\nAfter making code changes to a plugin or theme, follow this workflow:\n\n1. **Reload** the plugin to pick up changes:\n   ```bash\n   obsidian plugin:reload id=my-plugin\n   ```\n2. **Check for errors** — if errors appear, fix and repeat from step 1:\n   ```bash\n   obsidian dev:errors\n   ```\n3. **Verify visually** with a screenshot or DOM inspection:\n   ```bash\n   obsidian dev:screenshot path=screenshot.png\n   obsidian dev:dom selector=\".workspace-leaf\" text\n   ```\n4. **Check console output** for warnings or unexpected logs:\n   ```bash\n   obsidian dev:console level=error\n   ```\n\n### Additional developer commands\n\nRun JavaScript in the app context:\n\n```bash\nobsidian eval code=\"app.vault.getFiles().length\"\n```\n\nInspect CSS values:\n\n```bash\nobsidian dev:css selector=\".workspace-leaf\" prop=background-color\n```\n\nToggle mobile emulation:\n\n```bash\nobsidian dev:mobile on\n```\n\nRun `obsidian help` to see additional developer commands including CDP and debugger controls.\n",{"name":5,"description":7},"main","0e53802c0c332ab23445b83651f15999e1ac89b8","plugin\u002Fskills\u002Fobsidian-cli",1,"https:\u002F\u002Fgithub.com\u002FJayJiangCT\u002Fknowlery","https:\u002F\u002Fgithub.com\u002FJayJiangCT","2026-11-09 16:04:29",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add JayJiangCT\u002Fknowlery --skill obsidian-cli",{"tool":65,"command":66},"bunx","bunx skills add JayJiangCT\u002Fknowlery --skill obsidian-cli",{"tool":68,"command":69},"pnpm","pnpm dlx skills add JayJiangCT\u002Fknowlery --skill obsidian-cli","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJayJiangCT\u002Fknowlery\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fobsidian-cli\u002FSKILL.md",true,[],[74,90,111,130,146,173],{"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":47},"01M70FWHK80WMW5C9Y12KEZ8RG","vault-conventions","Use when creating or modifying notes in a Knowlery-structured vault. Enforces frontmatter requirements, wikilinks, and naming conventions.","https:\u002F\u002Fgithub.com\u002FJayJiangCT\u002Fknowlery\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fvault-conventions\u002FSKILL.md",[],[81,82,83,39,84,85,86,42,87,88,89],"vault","vault conventions","conventions","naming","use","naming conventions","frontmatter","requirements","structured",{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":47},"01M70FWF616X3Z6BPPW6A96VHT","organize","Directory organization based on frontmatter metadata. Suggests and applies file moves to keep the vault structured. Use when the user wants to reorganize notes, fix directory placement, clean up the vault structure, or says anything like \"organize my notes\", \"clean up the vault\", \"move files to the right folders\", \"tidy up\", or \"restructure my notes\".","https:\u002F\u002Fgithub.com\u002FJayJiangCT\u002Fknowlery\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Forganize\u002FSKILL.md",[],[92,97,98,99,100,101,102,85,42,103,104,39,105,81,106,107,108,87,109,110],"move","up","fix","clean","tidy","files","keep","file","structure","organization","directory","my","user","metadata",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":122,"publishedAt":47},"01M70FWC3VG73VJD8C56SEPM3X","obsidian-markdown","Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax. Use when working with .md files in Obsidian, or when the user mentions wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes.","https:\u002F\u002Fgithub.com\u002FJayJiangCT\u002Fknowlery\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fobsidian-markdown\u002FSKILL.md",[117],{"categoryNo":118,"categoryName":119,"taxonomyType":120,"taxonomyTypeDesc":121},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",[29,123,124,102,85,42,125,126,40,39,127,128,129,87,109],"obsidian markdown","markdown","tags","with","properties","edit","syntax",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":47},"01M70FW75P9SEH28NWR115GZNN","obsidian-bases","Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.","https:\u002F\u002Fgithub.com\u002FJayJiangCT\u002Fknowlery\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fobsidian-bases\u002FSKILL.md",[],[29,137,138,139,140,102,141,85,142,42,126,40,39,143,128,144,109,145],"obsidian bases","bases","formulas","card","filters","database","summaries","base","table",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":155,"publishedAt":47},"01M70FW4ASRQ42NW1AC0AAWWAC","knowlery-mcp","Work a Knowlery knowledge base through its MCP tools — choose the right tool for the job, run the capture-to-cook loop, and behave well while doing it. Use when Knowlery MCP tools (query, capture, stale, health, init_kb, register_kb, sync, list_kbs, list_bundles) are available in the session, especially in clients without a shell.","https:\u002F\u002Fgithub.com\u002FJayJiangCT\u002Fknowlery\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fknowlery-mcp\u002FSKILL.md",[152],{"categoryNo":153,"categoryName":154,"taxonomyType":120,"taxonomyTypeDesc":121},"01JBSEEDCAT000000000000023","Skill与智能体开发",[156,157,158,159,160,161,162,163,164,165,166,85,167,42,168,169,170,171,37,172],"knowlery mcp","MCP","kb","register","for","choose","session","tool","behave","init","knowledge","loop","query","health","knowledge base","work","shell",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":179,"publishedAt":47},"01M70FW1DAYXG7MFZAA5NWYHT9","knowlery-cli","Manage a Knowlery knowledge base from the command line with the standalone knowlery CLI — initialize and sync workspaces, run health checks, query knowledge, detect stale pages, and install, export, and review knowledge bundles. Use when the user asks to operate their knowledge base headlessly (without Obsidian), share knowledge as a bundle, install a bundle someone shared, or verify the workspace after bulk changes.","https:\u002F\u002Fgithub.com\u002FJayJiangCT\u002Fknowlery\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fknowlery-cli\u002FSKILL.md",[],[180,27,181,182,183,184,185,186,187,188,29,189,166,85,42,168,190,191,169,126],"knowlery cli","shared","bulk","as","operate","initialize","standalone","manage","workspaces","pages","review","share"]