[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70FWHK80WMW5C9Y12KEZ8RG":3,"skill-same:01M70FWHK80WMW5C9Y12KEZ8RG":56},{"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":30,"linkOnly":31,"markdownContent":32,"markdownBody":33,"frontMatter":34,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":41,"install":42,"resources":55},"01M70FWHK80WMW5C9Y12KEZ8RG","vault-conventions",null,"Use when creating or modifying notes in a Knowlery-structured vault. Enforces frontmatter requirements, wikilinks, and naming conventions.","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\u002Fvault-conventions\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29],"vault","vault conventions","conventions","notes","naming","use","naming conventions","when","frontmatter","requirements","structured","2026-11-10 10:12:30",false,"---\nname: vault-conventions\ndescription: Use when creating or modifying notes in a Knowlery-structured vault. Enforces frontmatter requirements, wikilinks, and naming conventions.\n---\n\n# Vault Document Conventions\n\nYou MUST follow these conventions when creating or modifying any note in this vault.\n\n## Pre-Flight Checklist\n\nBefore creating any note:\n\n1. Read `KNOWLEDGE.md` — check the knowledge base structure (user notes vs agent-maintained pages)\n2. Decide where the note belongs: **user notes** stay in their existing areas (e.g. `Projects\u002F`, `Daily\u002F`); **agent knowledge pages** live only under `entities\u002F`, `concepts\u002F`, `comparisons\u002F`, or `queries\u002F`\n3. Pick the writing tool by the operation (see Creating Notes below), following every convention in this skill\n\n## Creating Notes\n\nChoose the writing tool **by the operation, not by whether Obsidian is running**:\n\n| Operation | Preferred tool | Why |\n|-----------|----------------|-----|\n| New page with long or complex content (frontmatter + body, code blocks, quotes) | Write the `.md` file directly at the exact path | Obsidian indexes new files automatically; no shell escaping can corrupt content |\n| Short new note, or appending a line or two | `obsidian create path=\"dir\u002Fnote.md\" content=\"...\"` \u002F `obsidian append` | Cheap when the content is small; `\\n` escapes newlines |\n| Rename \u002F move an existing note | `obsidian rename` (Obsidian running) | The CLI rewrites wikilinks across the vault — the real graph-consistency win |\n\n`obsidian create` passes content as **one shell-quoted argument**. Inside a\nbash double-quoted string, backticks run as command substitution, `$` expands,\nand nested quotes end the argument — so a page containing a code fence or\nquoted prose will usually break the command or corrupt the content. **If\n`create` fails once on content escaping, do not fight the shell: write the\nfile directly** with identical frontmatter and naming conventions, then verify\nwith `obsidian read` (or `knowlery health` after bulk changes).\n\nWhen you do use `obsidian create`, pass `path=\"dir\u002Fnote.md\"` — `name=`\nresolves like a wikilink and lands in the default new-note location, not\nnecessarily the directory the page belongs in.\n\nTreat any page containing frontmatter plus body, Mermaid or other charts, code\nfences, tables, or quoted prose as a full page and write the `.md` file\ndirectly.\n\nIn headless environments (Obsidian closed, CLI-initialized workspaces), write\n`.md` files directly, and run `knowlery health` after bulk changes.\n\n## Hidden Config Paths\n\nDot-directories (`.claude\u002F`, `.knowlery\u002F`, `.agents\u002F`) are outside\nObsidian's vault index. Obsidian CLI commands that depend on the vault index —\nincluding `read` and `create` — cannot reach them even with `path=`; use\nyour file tools directly.\n\nEvery platform starts from the same sources: the user's `KNOWLEDGE.md` and\nthe rules in `.agents\u002Frules\u002F`, plus Knowlery's operating rules. Codex and\nOpenCode read the vault-root `AGENTS.md`, where those sources are copied in;\nClaude Code reads `.claude\u002FCLAUDE.md`, which `@`-imports the same files. Both\nentry files are regenerated on sync: change `KNOWLEDGE.md` or a rule file,\nnever the managed block itself.\n\n## Required Frontmatter\n\nEvery note MUST have these fields:\n\n| Field | Values |\n|-------|--------|\n| `title` | Descriptive title |\n| `type` | `meeting`, `idea`, `reference`, `daily`, `project`, `person`, `entity`, `concept`, `comparison`, `query`, etc. |\n| `date` | YYYY-MM-DD — today's date or extracted from content |\n| `tags` | Array of relevant tags |\n\nAdditional fields (optional):\n\n| Field | Purpose |\n|-------|---------|\n| `domain` | Knowledge area (e.g. ai-agents, product-strategy) |\n| `references` | Related notes as wikilinks: `[[Note Name]]` |\n| `status` | `draft`, `active`, `completed`, `archived` |\n| `updated` | YYYY-MM-DD — last substantive edit (common on agent pages) |\n| `contradictions` | Cross-links when conflicting claims need review (agent pages) |\n\n## Wikilink Rules\n\nALWAYS use wikilinks for:\n\n- People → `[[Person Name]]`\n- Projects → `[[Project Name]]`\n- Domain concepts → `[[Concept Name]]`\n- Related notes → `[[Note Name]]`\n\nRules:\n- Use `[[wikilinks]]` for internal vault connections\n- Use `[text](url)` for external URLs only\n- Use `[[Note Name#Heading]]` for specific section links\n- Use `[[Note Name|Display Text]]` for custom display text\n\n## File Naming\n\n- **Agent knowledge pages** (per `SCHEMA.md`): lowercase with hyphens, no spaces\n  (`response-time-metrics.md`); one topic per file under `entities\u002F`, `concepts\u002F`,\n  `comparisons\u002F`, or `queries\u002F`\n- **User notes** keep the user's own naming — never rename them to match agent conventions\n- No special characters, no leading\u002Ftrailing spaces\n- Daily notes: `YYYY-MM-DD` format where applicable\n\n## Post-Creation Verification\n\nAfter creating or modifying a note, verify:\n\n1. All required frontmatter fields are present and correct\n2. People and project mentions use `[[wikilinks]]`\n3. Domain concepts are linked consistently\n","# Vault Document Conventions\n\nYou MUST follow these conventions when creating or modifying any note in this vault.\n\n## Pre-Flight Checklist\n\nBefore creating any note:\n\n1. Read `KNOWLEDGE.md` — check the knowledge base structure (user notes vs agent-maintained pages)\n2. Decide where the note belongs: **user notes** stay in their existing areas (e.g. `Projects\u002F`, `Daily\u002F`); **agent knowledge pages** live only under `entities\u002F`, `concepts\u002F`, `comparisons\u002F`, or `queries\u002F`\n3. Pick the writing tool by the operation (see Creating Notes below), following every convention in this skill\n\n## Creating Notes\n\nChoose the writing tool **by the operation, not by whether Obsidian is running**:\n\n| Operation | Preferred tool | Why |\n|-----------|----------------|-----|\n| New page with long or complex content (frontmatter + body, code blocks, quotes) | Write the `.md` file directly at the exact path | Obsidian indexes new files automatically; no shell escaping can corrupt content |\n| Short new note, or appending a line or two | `obsidian create path=\"dir\u002Fnote.md\" content=\"...\"` \u002F `obsidian append` | Cheap when the content is small; `\\n` escapes newlines |\n| Rename \u002F move an existing note | `obsidian rename` (Obsidian running) | The CLI rewrites wikilinks across the vault — the real graph-consistency win |\n\n`obsidian create` passes content as **one shell-quoted argument**. Inside a\nbash double-quoted string, backticks run as command substitution, `$` expands,\nand nested quotes end the argument — so a page containing a code fence or\nquoted prose will usually break the command or corrupt the content. **If\n`create` fails once on content escaping, do not fight the shell: write the\nfile directly** with identical frontmatter and naming conventions, then verify\nwith `obsidian read` (or `knowlery health` after bulk changes).\n\nWhen you do use `obsidian create`, pass `path=\"dir\u002Fnote.md\"` — `name=`\nresolves like a wikilink and lands in the default new-note location, not\nnecessarily the directory the page belongs in.\n\nTreat any page containing frontmatter plus body, Mermaid or other charts, code\nfences, tables, or quoted prose as a full page and write the `.md` file\ndirectly.\n\nIn headless environments (Obsidian closed, CLI-initialized workspaces), write\n`.md` files directly, and run `knowlery health` after bulk changes.\n\n## Hidden Config Paths\n\nDot-directories (`.claude\u002F`, `.knowlery\u002F`, `.agents\u002F`) are outside\nObsidian's vault index. Obsidian CLI commands that depend on the vault index —\nincluding `read` and `create` — cannot reach them even with `path=`; use\nyour file tools directly.\n\nEvery platform starts from the same sources: the user's `KNOWLEDGE.md` and\nthe rules in `.agents\u002Frules\u002F`, plus Knowlery's operating rules. Codex and\nOpenCode read the vault-root `AGENTS.md`, where those sources are copied in;\nClaude Code reads `.claude\u002FCLAUDE.md`, which `@`-imports the same files. Both\nentry files are regenerated on sync: change `KNOWLEDGE.md` or a rule file,\nnever the managed block itself.\n\n## Required Frontmatter\n\nEvery note MUST have these fields:\n\n| Field | Values |\n|-------|--------|\n| `title` | Descriptive title |\n| `type` | `meeting`, `idea`, `reference`, `daily`, `project`, `person`, `entity`, `concept`, `comparison`, `query`, etc. |\n| `date` | YYYY-MM-DD — today's date or extracted from content |\n| `tags` | Array of relevant tags |\n\nAdditional fields (optional):\n\n| Field | Purpose |\n|-------|---------|\n| `domain` | Knowledge area (e.g. ai-agents, product-strategy) |\n| `references` | Related notes as wikilinks: `[[Note Name]]` |\n| `status` | `draft`, `active`, `completed`, `archived` |\n| `updated` | YYYY-MM-DD — last substantive edit (common on agent pages) |\n| `contradictions` | Cross-links when conflicting claims need review (agent pages) |\n\n## Wikilink Rules\n\nALWAYS use wikilinks for:\n\n- People → `[[Person Name]]`\n- Projects → `[[Project Name]]`\n- Domain concepts → `[[Concept Name]]`\n- Related notes → `[[Note Name]]`\n\nRules:\n- Use `[[wikilinks]]` for internal vault connections\n- Use `[text](url)` for external URLs only\n- Use `[[Note Name#Heading]]` for specific section links\n- Use `[[Note Name|Display Text]]` for custom display text\n\n## File Naming\n\n- **Agent knowledge pages** (per `SCHEMA.md`): lowercase with hyphens, no spaces\n  (`response-time-metrics.md`); one topic per file under `entities\u002F`, `concepts\u002F`,\n  `comparisons\u002F`, or `queries\u002F`\n- **User notes** keep the user's own naming — never rename them to match agent conventions\n- No special characters, no leading\u002Ftrailing spaces\n- Daily notes: `YYYY-MM-DD` format where applicable\n\n## Post-Creation Verification\n\nAfter creating or modifying a note, verify:\n\n1. All required frontmatter fields are present and correct\n2. People and project mentions use `[[wikilinks]]`\n3. Domain concepts are linked consistently\n",{"name":5,"description":7},"main","0e53802c0c332ab23445b83651f15999e1ac89b8","plugin\u002Fskills\u002Fvault-conventions",1,"https:\u002F\u002Fgithub.com\u002FJayJiangCT\u002Fknowlery","https:\u002F\u002Fgithub.com\u002FJayJiangCT","2026-11-09 16:04:29",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add JayJiangCT\u002Fknowlery --skill vault-conventions",{"tool":48,"command":49},"bunx","bunx skills add JayJiangCT\u002Fknowlery --skill vault-conventions",{"tool":51,"command":52},"pnpm","pnpm dlx skills add JayJiangCT\u002Fknowlery --skill vault-conventions","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJayJiangCT\u002Fknowlery\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fvault-conventions\u002FSKILL.md",true,[],[57,78,99,130,146,173],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":30},"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",[],[59,64,65,66,67,68,69,24,26,70,71,22,72,19,73,74,75,27,76,77],"move","up","fix","clean","tidy","files","keep","file","structure","organization","directory","my","user","metadata",{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":89,"publishedAt":30},"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",[84],{"categoryNo":85,"categoryName":86,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",[90,91,92,69,24,26,93,94,95,22,96,97,98,27,76],"obsidian","obsidian markdown","markdown","tags","with","create","properties","edit","syntax",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":113,"publishedAt":30},"01M70FW95K6BD12KQERZS0FWHW","obsidian-cli","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.","https:\u002F\u002Fgithub.com\u002FJayJiangCT\u002Fknowlery\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fobsidian-cli\u002FSKILL.md",[105,110],{"categoryNo":106,"categoryName":107,"taxonomyType":108,"taxonomyTypeDesc":109},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":111,"categoryName":112,"taxonomyType":108,"taxonomyTypeDesc":109},"01JBSEEDCAT000000000000036","内容创作者",[90,114,115,116,117,118,119,26,120,95,22,121,122,123,124,125,126,127,128,129],"cli","obsidian cli","inspect","search","errors","themes","tasks","command","run","line","read","commands","take","vaults","screenshots","theme",{"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":30},"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",[],[90,137,138,139,140,69,141,24,142,26,94,95,22,143,97,144,76,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":30},"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":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000023","Skill与智能体开发",[156,157,158,159,160,161,162,163,164,165,166,24,167,26,168,169,170,171,122,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":30},"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,114,181,182,183,184,185,186,187,188,90,189,166,24,26,168,190,191,169,94],"knowlery cli","shared","bulk","as","operate","initialize","standalone","manage","workspaces","pages","review","share"]