[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70FWF616X3Z6BPPW6A96VHT":3,"skill-same:01M70FWF616X3Z6BPPW6A96VHT":64},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":49,"install":50,"resources":63},"01M70FWF616X3Z6BPPW6A96VHT","organize",null,"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\".","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\u002Forganize\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"file","metadata","user","frontmatter","my","directory","organization","vault","structure","notes","keep","when","use","files","tidy","clean","fix","up","move","2026-11-10 10:12:30",false,"---\nname: organize\ndescription: >\n  Directory organization based on frontmatter metadata. Suggests and applies file moves\n  to keep the vault structured. Use when the user wants to reorganize notes, fix directory\n  placement, clean up the vault structure, or says anything like \"organize my notes\",\n  \"clean up the vault\", \"move files to the right folders\", \"tidy up\", or \"restructure\n  my notes\".\n---\n\n# \u002Forganize — Directory Organization\n\nYou are a librarian. Your job is to ensure every note lives in the right place based on its frontmatter metadata, type, and domain — and to suggest improvements to the overall vault structure.\n\n## Parameters\n\n- **scope** (optional): `all` (full vault), `agents` (agent pages only), `sources` (user notes), or a specific directory. Default: `all`.\n- **dry_run** (optional): `true` to only suggest, `false` to apply changes. Default: `true`.\n\n## Process\n\n### Step 1: Scan Current Structure\n\nStart from the orientation map — the compiled layer, bundles, and\nstale\u002Funcooked counts, precomputed:\n\n```bash\nknowlery index    # or read the MCP knowlery:\u002F\u002F\u003Ckb>\u002Findex resource\nobsidian list\n```\n\nBuild a picture of:\n- Current directory structure\n- Notes in each directory\n- Notes that seem misplaced based on their frontmatter\n\n### Step 2: Check Agent Pages\n\nAgent pages should live in their designated directories:\n\n| `type` frontmatter | Expected directory |\n|-------------------|-------------------|\n| `entity` | `entities\u002F` |\n| `concept` | `concepts\u002F` |\n| `comparison` | `comparisons\u002F` |\n| `query` | `queries\u002F` |\n\nFor each agent page, check:\n- Does its current directory match its `type`?\n- If not, suggest a move\n\n### Step 3: Check User Notes\n\nUser notes should **remain** in their existing directories (`Projects\u002F`, `Daily\u002F`, personal folders, etc.). Do not suggest moving them into agent directories. Suggest organization only if:\n\n- A user note has been placed in an agent directory (`entities\u002F`, `concepts\u002F`, `comparisons\u002F`, `queries\u002F`) — this is likely a mistake; propose moving it back to an appropriate user area\n- Multiple user notes about the same topic are scattered across **user** directories when they could be grouped there (never into agent dirs unless they are true agent pages with correct `type` frontmatter)\n\n### Step 4: Check Naming Conventions\n\nPer SCHEMA.md conventions — these apply to **agent pages** (user notes keep the\nuser's own naming):\n- File names should be lowercase with hyphens, no spaces\n- Names should match the page title (abbreviated, hyphenated)\n- No duplicate names with different suffixes (e.g., `feature-a.md` and `feature-a-1.md`)\n\nFlag naming violations on agent pages only.\n\n### Step 5: Suggest Moves\n\nFor each misplaced file:\n\n```\nMove: entities\u002Fwrong-place.md → concepts\u002Fwrong-place.md\n  Reason: type=concept but currently in entities\u002F\n\nMove: Projects\u002Frandom-notes.md → Projects\u002Ffeature-a\u002F\n  Reason: Content is about Feature A, should be grouped with other Feature A notes\n```\n\n### Step 6: Apply Moves (If Confirmed)\n\nPrefer Obsidian CLI to rename\u002Fmove files (it updates wikilinks automatically):\n\n```bash\nobsidian rename file=\"old-path.md\" new_name=\"new-path.md\"\n```\n\nIn headless environments, move the files directly, then check for broken wikilinks\nyourself (moved-page names grepped across the vault) and run `knowlery health` after\nbulk changes.\n\nAlways show the full plan before applying. Never move files silently.\n\n### Step 7: Update Wikilinks\n\nAfter moving files, check that all wikilinks to the moved files are still valid:\n\n```bash\nobsidian backlinks \"moved-file\"\n```\n\nObsidian typically handles wikilink updates on rename automatically, but verify for safety.\n\n## Key Principles\n\n- **Suggest first, act second.** Default to dry_run mode. Show the full plan before making any changes.\n- **Agent directories are sacred.** Only agent pages should live in `entities\u002F`, `concepts\u002F`, `comparisons\u002F`, `queries\u002F`.\n- **User notes are user territory.** Suggest organizational improvements but never move user notes without explicit confirmation.\n- **Obsidian first, headless second.** Prefer Obsidian CLI for note operations; in headless environments work with files directly under the same conventions.\n","# \u002Forganize — Directory Organization\n\nYou are a librarian. Your job is to ensure every note lives in the right place based on its frontmatter metadata, type, and domain — and to suggest improvements to the overall vault structure.\n\n## Parameters\n\n- **scope** (optional): `all` (full vault), `agents` (agent pages only), `sources` (user notes), or a specific directory. Default: `all`.\n- **dry_run** (optional): `true` to only suggest, `false` to apply changes. Default: `true`.\n\n## Process\n\n### Step 1: Scan Current Structure\n\nStart from the orientation map — the compiled layer, bundles, and\nstale\u002Funcooked counts, precomputed:\n\n```bash\nknowlery index    # or read the MCP knowlery:\u002F\u002F\u003Ckb>\u002Findex resource\nobsidian list\n```\n\nBuild a picture of:\n- Current directory structure\n- Notes in each directory\n- Notes that seem misplaced based on their frontmatter\n\n### Step 2: Check Agent Pages\n\nAgent pages should live in their designated directories:\n\n| `type` frontmatter | Expected directory |\n|-------------------|-------------------|\n| `entity` | `entities\u002F` |\n| `concept` | `concepts\u002F` |\n| `comparison` | `comparisons\u002F` |\n| `query` | `queries\u002F` |\n\nFor each agent page, check:\n- Does its current directory match its `type`?\n- If not, suggest a move\n\n### Step 3: Check User Notes\n\nUser notes should **remain** in their existing directories (`Projects\u002F`, `Daily\u002F`, personal folders, etc.). Do not suggest moving them into agent directories. Suggest organization only if:\n\n- A user note has been placed in an agent directory (`entities\u002F`, `concepts\u002F`, `comparisons\u002F`, `queries\u002F`) — this is likely a mistake; propose moving it back to an appropriate user area\n- Multiple user notes about the same topic are scattered across **user** directories when they could be grouped there (never into agent dirs unless they are true agent pages with correct `type` frontmatter)\n\n### Step 4: Check Naming Conventions\n\nPer SCHEMA.md conventions — these apply to **agent pages** (user notes keep the\nuser's own naming):\n- File names should be lowercase with hyphens, no spaces\n- Names should match the page title (abbreviated, hyphenated)\n- No duplicate names with different suffixes (e.g., `feature-a.md` and `feature-a-1.md`)\n\nFlag naming violations on agent pages only.\n\n### Step 5: Suggest Moves\n\nFor each misplaced file:\n\n```\nMove: entities\u002Fwrong-place.md → concepts\u002Fwrong-place.md\n  Reason: type=concept but currently in entities\u002F\n\nMove: Projects\u002Frandom-notes.md → Projects\u002Ffeature-a\u002F\n  Reason: Content is about Feature A, should be grouped with other Feature A notes\n```\n\n### Step 6: Apply Moves (If Confirmed)\n\nPrefer Obsidian CLI to rename\u002Fmove files (it updates wikilinks automatically):\n\n```bash\nobsidian rename file=\"old-path.md\" new_name=\"new-path.md\"\n```\n\nIn headless environments, move the files directly, then check for broken wikilinks\nyourself (moved-page names grepped across the vault) and run `knowlery health` after\nbulk changes.\n\nAlways show the full plan before applying. Never move files silently.\n\n### Step 7: Update Wikilinks\n\nAfter moving files, check that all wikilinks to the moved files are still valid:\n\n```bash\nobsidian backlinks \"moved-file\"\n```\n\nObsidian typically handles wikilink updates on rename automatically, but verify for safety.\n\n## Key Principles\n\n- **Suggest first, act second.** Default to dry_run mode. Show the full plan before making any changes.\n- **Agent directories are sacred.** Only agent pages should live in `entities\u002F`, `concepts\u002F`, `comparisons\u002F`, `queries\u002F`.\n- **User notes are user territory.** Suggest organizational improvements but never move user notes without explicit confirmation.\n- **Obsidian first, headless second.** Prefer Obsidian CLI for note operations; in headless environments work with files directly under the same conventions.\n",{"name":5,"description":7},"main","0e53802c0c332ab23445b83651f15999e1ac89b8","plugin\u002Fskills\u002Forganize",1,"https:\u002F\u002Fgithub.com\u002FJayJiangCT\u002Fknowlery","https:\u002F\u002Fgithub.com\u002FJayJiangCT","2026-11-09 16:04:29",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add JayJiangCT\u002Fknowlery --skill organize",{"tool":56,"command":57},"bunx","bunx skills add JayJiangCT\u002Fknowlery --skill organize",{"tool":59,"command":60},"pnpm","pnpm dlx skills add JayJiangCT\u002Fknowlery --skill organize","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJayJiangCT\u002Fknowlery\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Forganize\u002FSKILL.md",true,[],[65,78,99,130,146,173],{"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":38},"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",[],[26,72,73,28,74,31,75,30,22,76,77],"vault conventions","conventions","naming","naming conventions","requirements","structured",{"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":38},"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,32,31,30,93,94,95,28,96,97,98,22,21],"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":38},"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,30,120,95,28,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":38},"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,32,141,31,142,30,94,95,28,143,97,144,21,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":38},"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,31,167,30,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":38},"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,31,30,168,190,191,169,94],"knowlery cli","shared","bulk","as","operate","initialize","standalone","manage","workspaces","pages","review","share"]