[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B2PJ80G8N8ZFKG59ES4NF2":3,"skill-same:01M7B2PJ80G8N8ZFKG59ES4NF2":45},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7B2PJ80G8N8ZFKG59ES4NF2","obsidian-markdown",null,"Explain, draft, or validate Obsidian Flavored Markdown syntax: properties, wikilinks, embeds, callouts, tags, comments, highlights, block references, math, and Mermaid. Use when the user explicitly requests Obsidian note formatting or syntax help, not for general Markdown or broad vault operations.","Perryong\u002Fknowledge-brain","Perryong","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F67753175?v=4","01M7B2P4V7VJ31NK9B6N15FV95","Perry Ong WQ","01M7B2P4VVN72C07228FVB427F",0,"MIT","https:\u002F\u002Fgithub.com\u002FPerryong\u002Fknowledge-brain\u002Fblob\u002Fmain\u002Fskills\u002Fobsidian-markdown\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: obsidian-markdown\ndescription: \"Explain, draft, or validate Obsidian Flavored Markdown syntax: properties, wikilinks, embeds, callouts, tags, comments, highlights, block references, math, and Mermaid. Use when the user explicitly requests Obsidian note formatting or syntax help, not for general Markdown or broad vault operations.\"\n---\n\n# Obsidian Flavored Markdown\n\nUse this as a compact fallback for Obsidian-specific syntax. Prefer a separately\ninstalled `kepano\u002Fobsidian-skills` `obsidian-markdown` skill when available,\nthen current [Obsidian Help](https:\u002F\u002Fhelp.obsidian.md\u002F), for detailed or\nversion-sensitive questions.\n\nResolve the installed product root from this skill's own location, not from the\nvault or current working directory:\n\n```bash\nPRODUCT_ROOT=\u002Fabsolute\u002Fpath\u002Fto\u002Finstalled\u002Fclaude-obsidian\nCORE=\"$PRODUCT_ROOT\u002Fscripts\u002Fclaude-obsidian.py\"\ntest -f \"$CORE\"\n```\n\nAnswer syntax questions read-only. If the user requests a vault edit, draft the\ncomplete note, read [operation-transactions.md](..\u002Fwiki\u002Freferences\u002Foperation-transactions.md),\nand build one `claude-obsidian.transaction.v1` bundle with\n`operation_type: markdown` and only `wiki\u002F` targets. Inspect it, then set\n`APPROVAL_SHA256` to the returned `approval_sha256` after review and apply it\nthrough the same vault-bound plan. A canonical page create or removal includes\nan active index or MOC update in that bundle; update the overview only when its\nstable high-level synthesis changed:\n\n```bash\npython3 \"$CORE\" transaction inspect \"$BUNDLE\" --vault \"$VAULT\"\npython3 \"$CORE\" transaction apply \"$BUNDLE\" --vault \"$VAULT\" \\\n  --approved-plan-sha256 \"$APPROVAL_SHA256\"\n```\n\nNever write a note directly.\n\n## Properties\n\nUse flat YAML properties and `YYYY-MM-DD` dates. Quote wikilinks inside YAML.\n\n```yaml\n---\ntype: concept\ntitle: \"Contextual Retrieval\"\ncreated: 2026-07-11\nupdated: 2026-07-11\nstatus: developing\ntags:\n  - retrieval\n  - ai\u002Fknowledge\naliases:\n  - Context-aware retrieval\nrelated:\n  - \"[[Retrieval]]\"\nsources:\n  - \"[[Anthropic Contextual Retrieval]]\"\n---\n```\n\nDo not nest objects in generated wiki properties. Use block lists rather than\ninline YAML arrays. Quote numeric-only tag values, for example `- \"2026\"`, so\nYAML parsers preserve them as tags instead of numbers. Keep unknown existing\nproperties unless the requested edit changes them.\n\n## Wikilinks and embeds\n\n```markdown\n[[Note Name]]\n[[Note Name|Display text]]\n[[Note Name#Heading]]\n[[Note Name#^block-id]]\n[[Folder\u002FNote Name]]\n\nThis paragraph is addressable. ^evidence-block\n\n![[Note Name#Summary]]\n![[diagram.png|480]]\n![[paper.pdf#page=3]]\n```\n\nMatch the target filename exactly. Use a vault-relative folder path when a\nbasename is ambiguous. Use standard Markdown links for external URLs; use\nwikilinks for this vault's notes.\n\n## Callouts\n\n```markdown\n> [!note]\n> Supporting context.\n\n> [!warning] Review required\n> This claim has contradictory evidence.\n\n> [!question]- Open question\n> What evidence would resolve this?\n```\n\n`-` starts collapsed and `+` starts expanded. Common built-in types include\n`note`, `abstract`, `info`, `todo`, `tip`, `success`, `question`, `warning`,\n`failure`, `danger`, `bug`, `example`, and `quote`. Preserve custom vault\ncallout types rather than rewriting them.\n\n## Other Obsidian syntax\n\n````markdown\n#inline-tag #nested\u002Ftag\n\n==Highlighted text==\n\nVisible text %%hidden comment%%\n\nInline math: $E = mc^2$\n\n$$\n\\int_0^1 x^2\\,dx = \\frac{1}{3}\n$$\n\n```mermaid\nflowchart LR\n  Source --> Claim\n```\n````\n\nStandard CommonMark\u002FGFM headings, lists, tasks, tables, code fences, and\nfootnotes remain valid. Avoid HTML when native Markdown is sufficient.\n\n## Validate a drafted note\n\n- Parse the YAML boundary and keep property types consistent.\n- Verify every internal target, heading, and block reference that can be\n  checked locally; never fabricate a target to make a link look complete.\n- Keep evidence wording distinct from inference and preserve source locators.\n- Ensure code fences and callout quoting are balanced.\n- Run deterministic wiki lint after a requested mutation and report remaining\n  findings without silently repairing them.\n\nFor source-cited pages, also follow\n[provenance.md](..\u002Fwiki\u002Freferences\u002Fprovenance.md). Report the transaction\noperation ID and exact changed paths after an applied edit.\n","# Obsidian Flavored Markdown\n\nUse this as a compact fallback for Obsidian-specific syntax. Prefer a separately\ninstalled `kepano\u002Fobsidian-skills` `obsidian-markdown` skill when available,\nthen current [Obsidian Help](https:\u002F\u002Fhelp.obsidian.md\u002F), for detailed or\nversion-sensitive questions.\n\nResolve the installed product root from this skill's own location, not from the\nvault or current working directory:\n\n```bash\nPRODUCT_ROOT=\u002Fabsolute\u002Fpath\u002Fto\u002Finstalled\u002Fclaude-obsidian\nCORE=\"$PRODUCT_ROOT\u002Fscripts\u002Fclaude-obsidian.py\"\ntest -f \"$CORE\"\n```\n\nAnswer syntax questions read-only. If the user requests a vault edit, draft the\ncomplete note, read [operation-transactions.md](..\u002Fwiki\u002Freferences\u002Foperation-transactions.md),\nand build one `claude-obsidian.transaction.v1` bundle with\n`operation_type: markdown` and only `wiki\u002F` targets. Inspect it, then set\n`APPROVAL_SHA256` to the returned `approval_sha256` after review and apply it\nthrough the same vault-bound plan. A canonical page create or removal includes\nan active index or MOC update in that bundle; update the overview only when its\nstable high-level synthesis changed:\n\n```bash\npython3 \"$CORE\" transaction inspect \"$BUNDLE\" --vault \"$VAULT\"\npython3 \"$CORE\" transaction apply \"$BUNDLE\" --vault \"$VAULT\" \\\n  --approved-plan-sha256 \"$APPROVAL_SHA256\"\n```\n\nNever write a note directly.\n\n## Properties\n\nUse flat YAML properties and `YYYY-MM-DD` dates. Quote wikilinks inside YAML.\n\n```yaml\n---\ntype: concept\ntitle: \"Contextual Retrieval\"\ncreated: 2026-07-11\nupdated: 2026-07-11\nstatus: developing\ntags:\n  - retrieval\n  - ai\u002Fknowledge\naliases:\n  - Context-aware retrieval\nrelated:\n  - \"[[Retrieval]]\"\nsources:\n  - \"[[Anthropic Contextual Retrieval]]\"\n---\n```\n\nDo not nest objects in generated wiki properties. Use block lists rather than\ninline YAML arrays. Quote numeric-only tag values, for example `- \"2026\"`, so\nYAML parsers preserve them as tags instead of numbers. Keep unknown existing\nproperties unless the requested edit changes them.\n\n## Wikilinks and embeds\n\n```markdown\n[[Note Name]]\n[[Note Name|Display text]]\n[[Note Name#Heading]]\n[[Note Name#^block-id]]\n[[Folder\u002FNote Name]]\n\nThis paragraph is addressable. ^evidence-block\n\n![[Note Name#Summary]]\n![[diagram.png|480]]\n![[paper.pdf#page=3]]\n```\n\nMatch the target filename exactly. Use a vault-relative folder path when a\nbasename is ambiguous. Use standard Markdown links for external URLs; use\nwikilinks for this vault's notes.\n\n## Callouts\n\n```markdown\n> [!note]\n> Supporting context.\n\n> [!warning] Review required\n> This claim has contradictory evidence.\n\n> [!question]- Open question\n> What evidence would resolve this?\n```\n\n`-` starts collapsed and `+` starts expanded. Common built-in types include\n`note`, `abstract`, `info`, `todo`, `tip`, `success`, `question`, `warning`,\n`failure`, `danger`, `bug`, `example`, and `quote`. Preserve custom vault\ncallout types rather than rewriting them.\n\n## Other Obsidian syntax\n\n````markdown\n#inline-tag #nested\u002Ftag\n\n==Highlighted text==\n\nVisible text %%hidden comment%%\n\nInline math: $E = mc^2$\n\n$$\n\\int_0^1 x^2\\,dx = \\frac{1}{3}\n$$\n\n```mermaid\nflowchart LR\n  Source --> Claim\n```\n````\n\nStandard CommonMark\u002FGFM headings, lists, tasks, tables, code fences, and\nfootnotes remain valid. Avoid HTML when native Markdown is sufficient.\n\n## Validate a drafted note\n\n- Parse the YAML boundary and keep property types consistent.\n- Verify every internal target, heading, and block reference that can be\n  checked locally; never fabricate a target to make a link look complete.\n- Keep evidence wording distinct from inference and preserve source locators.\n- Ensure code fences and callout quoting are balanced.\n- Run deterministic wiki lint after a requested mutation and report remaining\n  findings without silently repairing them.\n\nFor source-cited pages, also follow\n[provenance.md](..\u002Fwiki\u002Freferences\u002Fprovenance.md). Report the transaction\noperation ID and exact changed paths after an applied edit.\n",{"name":5,"description":7},"main","1b6b4755bf678871237e0047cbac7a467824d0d4","skills\u002Fobsidian-markdown",1,"https:\u002F\u002Fgithub.com\u002FPerryong\u002Fknowledge-brain","https:\u002F\u002Fgithub.com\u002FPerryong","2026-11-14 10:36:45",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add Perryong\u002Fknowledge-brain --skill obsidian-markdown",{"tool":37,"command":38},"bunx","bunx skills add Perryong\u002Fknowledge-brain --skill obsidian-markdown",{"tool":40,"command":41},"pnpm","pnpm dlx skills add Perryong\u002Fknowledge-brain --skill obsidian-markdown","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FPerryong\u002Fknowledge-brain\u002Fblob\u002Fmain\u002Fskills\u002Fobsidian-markdown\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7B2QSV52XZ3153FYF6X6ZBB","example","Hermetic contract-validation fixture.","https:\u002F\u002Fgithub.com\u002FPerryong\u002Fknowledge-brain\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fcontracts\u002Fvalid\u002Fskills\u002Fexample\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7B2QP3HQQT2QDHEDM4QT2PD","wiki","Initialize, adopt, and route work for a separate Obsidian knowledge vault through the portable claude-obsidian core. Use for vault setup, scaffolding, workspace selection, cross-project configuration, or choosing the correct wiki sub-skill. Triggers: \u002Fwiki, set up wiki, scaffold vault, create knowledge base, adopt this vault, Obsidian vault, second brain setup, persistent wiki.","https:\u002F\u002Fgithub.com\u002FPerryong\u002Fknowledge-brain\u002Fblob\u002Fmain\u002Fskills\u002Fwiki\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7B2QJSFR0ZCK5QB402AA5DQ","wiki-retrieve","Build and query a vault-local contextual BM25 retrieval index with optional multilingual Nomic cosine reranking; use for retrieve, hybrid retrieval, BM25, rerank, contextual retrieval, chunk search, vault search, semantic search, find relevant passages, or retrieval diagnostics. Derived caches stay under .vault-meta, remote egress requires explicit consent, and unavailable reranking falls back deterministically.","https:\u002F\u002Fgithub.com\u002FPerryong\u002Fknowledge-brain\u002Fblob\u002Fmain\u002Fskills\u002Fwiki-retrieve\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7B2QFQW4NSVSXWRR9WQ7NAH","wiki-query","Answer an explicitly vault-scoped question from an Obsidian wiki without changing it. Use when the user selects the vault as the evidence source: query the wiki, query quick, query deep, explain from the wiki, summarize the vault, find in wiki, search the wiki, or based on the wiki. Do not route ordinary general-knowledge questions here.","https:\u002F\u002Fgithub.com\u002FPerryong\u002Fknowledge-brain\u002Fblob\u002Fmain\u002Fskills\u002Fwiki-query\u002FSKILL.md",[],[],{"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":19},"01M7B2QCP36HBTQXF0XY15MX95","wiki-mode","Read or configure the vault filing methodology and suggest destinations for planned knowledge creation under Generic, LYT, PARA, or Zettelkasten. Use for wiki mode, methodology mode, what is my vault mode, set vault mode, switch to PARA, use LYT, Zettelkasten setup, change mode, configure mode, or methodology routing. This skill does not save content or migrate notes.","https:\u002F\u002Fgithub.com\u002FPerryong\u002Fknowledge-brain\u002Fblob\u002Fmain\u002Fskills\u002Fwiki-mode\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7B2Q9SMNY50QKDRD68QGSYQ","wiki-lint","Run a deterministic, read-only health check on an Obsidian wiki. Use for lint, vault health check, audit wiki health, find orphans, find dead links, frontmatter audit, provenance audit, or wiki audit. Reports graph, link, frontmatter, provenance-ledger, empty-section, and stale-index findings; it does not reason broadly or repair files.","https:\u002F\u002Fgithub.com\u002FPerryong\u002Fknowledge-brain\u002Fblob\u002Fmain\u002Fskills\u002Fwiki-lint\u002FSKILL.md",[],[]]