[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6NSWSZQ01KXVDH0W8B8XT3F":3,"skill-same:01M6NSWSZQ01KXVDH0W8B8XT3F":66},{"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":48,"ownerHtmlUrl":49,"ownerBlogUrl":48,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M6NSWSZQ01KXVDH0W8B8XT3F","think",null,"Apply the Fable-derived 10-stage OBSERVE, OBSERVE, LISTEN, THINK, CONNECT, CONNECT, FEEL, ACCEPT, CREATE, GROW loop to consequential or ambiguous reasoning and decisions. Use for think this through, deep think, architecture review, postmortem, tradeoff analysis, or challenges to assumptions. This is a reasoning review, not a deterministic vault health check or repair workflow.","AgriciDaniel\u002Fclaude-obsidian","AgriciDaniel","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F223140489?v=4","01M6NSV41N5002GVCNZH16EN21","Agrici Daniel","01M6NSV45ZB53JY0AVD3F7GPY0",16492,"MIT","https:\u002F\u002Fgithub.com\u002FAgriciDaniel\u002Fclaude-obsidian\u002Fblob\u002Fmain\u002Fskills\u002Fthink\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"decisions","for","grow","stage","deep","repair","deterministic","observe","use","review","postmortem","loop","analysis","create","connect","tradeoff analysis","architecture review","architecture","workflow","2026-11-10 10:12:30",false,"---\nname: think\ndescription: Apply the Fable-derived 10-stage OBSERVE, OBSERVE, LISTEN, THINK, CONNECT, CONNECT, FEEL, ACCEPT, CREATE, GROW loop to consequential or ambiguous reasoning and decisions. Use for think this through, deep think, architecture review, postmortem, tradeoff analysis, or challenges to assumptions. This is a reasoning review, not a deterministic vault health check or repair workflow.\n---\n\n# Think\n\nUse the ten stages as a loop of attention, not a ceremonial transcript. Scale\nthe depth to novelty, stakes, uncertainty, and irreversibility. Keep the final\nreasoning summary concise and evidence-bearing.\n\nThis skill is read-only. It may inspect available evidence, but it does not\nedit files, execute a vault mutation, commit Git, or publish anything. If the\nCREATE stage recommends a change, compose with the appropriate mutation skill\nafter the user authorizes that operation.\n\n## Establish an evidence frame\n\nBefore the loop, separate:\n\n- **Observed:** directly supported by an input, source, test, or measurement.\n- **Inferred:** a conclusion drawn from observations; state the bridge.\n- **Unknown:** missing evidence that could change the decision.\n- **Preference:** a user or designer choice, not a factual claim.\n\nAttach citations or concrete locators when sources exist. Never fabricate a\nquotation, locator, test result, consensus, or confidence level.\n\n## The ten stages\n\n### 1. OBSERVE: external\n\nRead the actual inputs, current state, constraints, failures, and prior work.\nDistinguish what was inspected in full from what was sampled or assumed.\n\n### 2. OBSERVE: internal\n\nName the biases most likely to distort this decision: anchoring, ownership,\nnovelty, familiarity, urgency, sunk cost, confirmation, or a desired verdict.\nRecalibrate confidence to the evidence available.\n\n### 3. LISTEN\n\nRecover the user's intent, success condition, constraints, and unstated stakes.\nAttend to error messages, dissent, edge cases, and affected voices. Ask only\nquestions whose answers could materially change the outcome.\n\n### 4. THINK\n\nReduce the problem to invariants, alternatives, tradeoffs, and failure modes.\nPrefer the smallest reversible test that could disprove the leading hypothesis.\nTreat failure behavior as part of the specification.\n\n### 5. CONNECT: lateral\n\nLook for the same structure in adjacent components or another domain. Use an\nanalogy only when its mapped similarities and limits are explicit.\n\n### 6. CONNECT: system\n\nTrace upstream inputs, downstream consumers, ownership, state boundaries,\ninterfaces, and recovery paths. Check whether a locally sound decision creates\nan integration failure elsewhere.\n\n### 7. FEEL\n\nConsider the user's cognitive load, emotional state, accessibility, trust, and\nerror-recovery experience. Treat intuition as a signal to investigate, never as\na substitute for evidence.\n\n### 8. ACCEPT\n\nState constraints, uncertainty, contradictory evidence, and unfavorable\nfindings plainly. Do not inflate a score, soften a material risk to please the\nuser, or mistake agreement for correctness. Present the strongest reasonable\ncounterargument to the preferred conclusion.\n\n### 9. CREATE\n\nProduce the smallest useful artifact: a recommendation, decision record,\nexperiment, draft, review, or handoff. Mark assumptions and unresolved risks.\nDo not mutate state under this skill.\n\n### 10. GROW\n\nDefine what feedback or measurement should update the decision, when to revisit\nit, and what lesson is reusable. Saving the lesson is a separate explicit\noperation composed with `save`.\n\n## Verification discipline\n\nBefore calling the work complete:\n\n1. Test the highest-risk claim or clearly state why it remains untested.\n2. Seek disconfirming evidence, not only supporting examples.\n3. Match verification effort to blast radius and reversibility.\n4. Report actual commands, sources, artifacts, or observations used.\n5. Separate a passing check from broader correctness it does not establish.\n6. Give confidence as a calibrated qualitative judgment with reasons, not as a\n   decorative percentage.\n\n## Output shape\n\nAdapt the headings to the task, but preserve these outcomes:\n\n```markdown\n## Decision\n\u003Crecommendation or artifact>\n\n## Evidence\n\u003Cobserved facts and important inferences>\n\n## Counterargument and risks\n\u003Cstrongest alternative, contradictions, unknowns>\n\n## Verification\n\u003Cchecks performed and checks still needed>\n\n## Growth loop\n\u003Cfeedback signal, revisit condition, reusable lesson>\n```\n\nFor a trivial, reversible lookup or typo, skip the formal loop. For a\nconsequential decision, loop back whenever a later stage exposes a missing\nobservation or misunderstood requirement.\n","# Think\n\nUse the ten stages as a loop of attention, not a ceremonial transcript. Scale\nthe depth to novelty, stakes, uncertainty, and irreversibility. Keep the final\nreasoning summary concise and evidence-bearing.\n\nThis skill is read-only. It may inspect available evidence, but it does not\nedit files, execute a vault mutation, commit Git, or publish anything. If the\nCREATE stage recommends a change, compose with the appropriate mutation skill\nafter the user authorizes that operation.\n\n## Establish an evidence frame\n\nBefore the loop, separate:\n\n- **Observed:** directly supported by an input, source, test, or measurement.\n- **Inferred:** a conclusion drawn from observations; state the bridge.\n- **Unknown:** missing evidence that could change the decision.\n- **Preference:** a user or designer choice, not a factual claim.\n\nAttach citations or concrete locators when sources exist. Never fabricate a\nquotation, locator, test result, consensus, or confidence level.\n\n## The ten stages\n\n### 1. OBSERVE: external\n\nRead the actual inputs, current state, constraints, failures, and prior work.\nDistinguish what was inspected in full from what was sampled or assumed.\n\n### 2. OBSERVE: internal\n\nName the biases most likely to distort this decision: anchoring, ownership,\nnovelty, familiarity, urgency, sunk cost, confirmation, or a desired verdict.\nRecalibrate confidence to the evidence available.\n\n### 3. LISTEN\n\nRecover the user's intent, success condition, constraints, and unstated stakes.\nAttend to error messages, dissent, edge cases, and affected voices. Ask only\nquestions whose answers could materially change the outcome.\n\n### 4. THINK\n\nReduce the problem to invariants, alternatives, tradeoffs, and failure modes.\nPrefer the smallest reversible test that could disprove the leading hypothesis.\nTreat failure behavior as part of the specification.\n\n### 5. CONNECT: lateral\n\nLook for the same structure in adjacent components or another domain. Use an\nanalogy only when its mapped similarities and limits are explicit.\n\n### 6. CONNECT: system\n\nTrace upstream inputs, downstream consumers, ownership, state boundaries,\ninterfaces, and recovery paths. Check whether a locally sound decision creates\nan integration failure elsewhere.\n\n### 7. FEEL\n\nConsider the user's cognitive load, emotional state, accessibility, trust, and\nerror-recovery experience. Treat intuition as a signal to investigate, never as\na substitute for evidence.\n\n### 8. ACCEPT\n\nState constraints, uncertainty, contradictory evidence, and unfavorable\nfindings plainly. Do not inflate a score, soften a material risk to please the\nuser, or mistake agreement for correctness. Present the strongest reasonable\ncounterargument to the preferred conclusion.\n\n### 9. CREATE\n\nProduce the smallest useful artifact: a recommendation, decision record,\nexperiment, draft, review, or handoff. Mark assumptions and unresolved risks.\nDo not mutate state under this skill.\n\n### 10. GROW\n\nDefine what feedback or measurement should update the decision, when to revisit\nit, and what lesson is reusable. Saving the lesson is a separate explicit\noperation composed with `save`.\n\n## Verification discipline\n\nBefore calling the work complete:\n\n1. Test the highest-risk claim or clearly state why it remains untested.\n2. Seek disconfirming evidence, not only supporting examples.\n3. Match verification effort to blast radius and reversibility.\n4. Report actual commands, sources, artifacts, or observations used.\n5. Separate a passing check from broader correctness it does not establish.\n6. Give confidence as a calibrated qualitative judgment with reasons, not as a\n   decorative percentage.\n\n## Output shape\n\nAdapt the headings to the task, but preserve these outcomes:\n\n```markdown\n## Decision\n\u003Crecommendation or artifact>\n\n## Evidence\n\u003Cobserved facts and important inferences>\n\n## Counterargument and risks\n\u003Cstrongest alternative, contradictions, unknowns>\n\n## Verification\n\u003Cchecks performed and checks still needed>\n\n## Growth loop\n\u003Cfeedback signal, revisit condition, reusable lesson>\n```\n\nFor a trivial, reversible lookup or typo, skip the formal loop. For a\nconsequential decision, loop back whenever a later stage exposes a missing\nobservation or misunderstood requirement.\n",{"name":5,"description":7},"main","2e545563172f97f02ecaaaab376ceea1246a0583","skills\u002Fthink",1619,"https:\u002F\u002Fgithub.com\u002FAgriciDaniel\u002Fclaude-obsidian","skool.com\u002Fai-marketing-hub-pro","https:\u002F\u002Fgithub.com\u002FAgriciDaniel","AI Marketing Systems Architect. Building open-source Claude & Codex skills for SEO, ads & content.","2026-10-26 06:24:31",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add AgriciDaniel\u002Fclaude-obsidian --skill think",{"tool":58,"command":59},"bunx","bunx skills add AgriciDaniel\u002Fclaude-obsidian --skill think",{"tool":61,"command":62},"pnpm","pnpm dlx skills add AgriciDaniel\u002Fclaude-obsidian --skill think","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAgriciDaniel\u002Fclaude-obsidian\u002Fblob\u002Fmain\u002Fskills\u002Fthink\u002FSKILL.md",true,[],[67,77,106,130,151,172],{"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":38},"01M6NT0DAAX3MYEFY0KAHHB8ZM","example","Hermetic contract-validation fixture.","https:\u002F\u002Fgithub.com\u002FAgriciDaniel\u002Fclaude-obsidian\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fcontracts\u002Fvalid\u002Fskills\u002Fexample\u002FSKILL.md",[],[69,74,75,76],"validation","fixture","contract",{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":88,"publishedAt":38},"01M6NSZXSXYVNAP466EJM5VYSW","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\u002FAgriciDaniel\u002Fclaude-obsidian\u002Fblob\u002Fmain\u002Fskills\u002Fwiki\u002FSKILL.md",[83],{"categoryNo":84,"categoryName":85,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[79,89,90,32,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,20],"obsidian","core","SET","obsidian vault","knowledge","correct","work","initialize","up","second brain","selection","route","scaffolding","knowledge base","project","brain","adopt",{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":38},"01M6NSZ8X3MMTK7SHXR75G6GEB","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\u002FAgriciDaniel\u002Fclaude-obsidian\u002Fblob\u002Fmain\u002Fskills\u002Fwiki-retrieve\u002FSKILL.md",[],[79,113,114,115,116,117,118,119,27,120,121,122,123,124,125,126,127,128,20,129],"wiki retrieve","semantic search","diagnostics","chunk","search","Meta","vault","multilingual","build","back","query","local","bm25","relevant","remote","with","hybrid",{"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":139,"publishedAt":38},"01M6NSYHAKKYH5XM3ABQRAJ8P9","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\u002FAgriciDaniel\u002Fclaude-obsidian\u002Fblob\u002Fmain\u002Fskills\u002Fwiki-query\u002FSKILL.md",[136],{"categoryNo":137,"categoryName":138,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000021","资料检索与研究",[140,79,123,89,117,119,93,141,142,27,143,144,145,100,23,146,147,148,149,150],"wiki query","explain","question","evidence","general","do","as","quick","answer","source","scoped",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":157,"publishedAt":38},"01M6NSYCX1THMPAAX3EWNQDKVE","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\u002FAgriciDaniel\u002Fclaude-obsidian\u002Fblob\u002Fmain\u002Fskills\u002Fwiki-mode\u002FSKILL.md",[],[79,158,159,160,161,162,91,119,163,93,164,165,166,27,167,168,169,170,171,20],"mode","wiki mode","change","notes","routing","save","migrate","configure","read","switch","creation","filing","zettelkasten","my",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":181,"publishedAt":38},"01M6NSY916ASYAVW53W6A78AWT","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\u002FAgriciDaniel\u002Fclaude-obsidian\u002Fblob\u002Fmain\u002Fskills\u002Fwiki-lint\u002FSKILL.md",[178],{"categoryNo":179,"categoryName":180,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000007","代码审查",[182,183,79,89,184,185,186,187,166,27,188,189,190,25,24,191,192,20,193,194],"lint","wiki lint","run","graph","audit","provenance","only","reports","files","read-only","links","frontmatter","section"]