[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AT2335QB32671TKSFTXS50":3,"skill-same:01M7AT2335QB32671TKSFTXS50":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7AT2335QB32671TKSFTXS50","wiki-synthesize",null,"Systematically discover synthesis opportunities across the Obsidian wiki — pairs or clusters of concepts that co-occur frequently across pages but have no synthesis page connecting them. Creates new synthesis\u002F pages that draw explicit cross-cutting conclusions. Use when the user says \"synthesize my wiki\", \"create synthesis pages\", \"what concepts keep coming up together\", \"\u002Fwiki-synthesize\", or after a large ingest when the vault has grown significantly.","saski\u002Farnesto","saski","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F140356?v=4","01M7ASBDSNXTRYDYB4K1PEA1RV","01M7ASBDTAKBDAAV99S1GE7HK6",6,"Unlicense","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwiki-synthesize\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: wiki-synthesize\ndescription: >\n  Systematically discover synthesis opportunities across the Obsidian wiki — pairs or clusters of\n  concepts that co-occur frequently across pages but have no synthesis page connecting them. Creates\n  new synthesis\u002F pages that draw explicit cross-cutting conclusions. Use when the user says \"synthesize\n  my wiki\", \"create synthesis pages\", \"what concepts keep coming up together\", \"\u002Fwiki-synthesize\", or after\n  a large ingest when the vault has grown significantly.\n---\n\n# Wiki Synthesize — First-Class Synthesis Discovery\n\nYou are scanning the wiki for concepts that co-occur across many pages but have no dedicated synthesis page connecting them. Your job is to surface these gaps and fill the most valuable ones with cross-cutting synthesis pages.\n\n## Before You Start\n\n1. Read `~\u002F.obsidian-wiki\u002Fconfig` (preferred) or `.env` (fallback) to get `OBSIDIAN_VAULT_PATH`.\n2. Read `index.md` to get the full page inventory.\n3. Read `hot.md` if it exists — it surfaces recent activity and active threads that may already point to synthesis opportunities.\n4. Read `_meta\u002Ftaxonomy.md` to understand the tag vocabulary.\n\n## Step 1: Build the Co-occurrence Map\n\nScan every non-special page in the vault (skip `index.md`, `log.md`, `hot.md`, `_insights.md`, `_meta\u002F*`, `_archives\u002F*`, `_raw\u002F*`).\n\nFor each page, collect:\n- All `[[wikilinks]]` it contains (outgoing links)\n- Its `tags` frontmatter\n- Its `category` frontmatter\n\nBuild a co-occurrence matrix: for every pair of concept\u002Fentity pages (A, B), count how many other pages link to **both** A and B. This is their co-occurrence score.\n\nYou don't need to be exhaustive — aim for the top 20-30 pairs by co-occurrence score. Use Grep to find backlinks efficiently:\n\n```bash\ngrep -rl \"\\[\\[ConceptA\\]\\]\" \"$OBSIDIAN_VAULT_PATH\" --include=\"*.md\"\n```\n\nRun this for your top candidate concepts and intersect the result sets.\n\n## Step 2: Filter Out Already-Synthesized Pairs\n\nCheck the `synthesis\u002F` directory for existing pages. For each existing synthesis page:\n- Read its `sources` frontmatter or its body for `[[wikilinks]]`\n- Mark those concept pairs as already covered\n\nRemove covered pairs from your candidate list.\n\n## Step 3: Score and Rank Candidates\n\nFor each remaining candidate pair (or cluster of 3+), assign a synthesis value score:\n\n| Signal | Points |\n|---|---|\n| Co-occurrence count ≥ 5 | +3 |\n| Co-occurrence count 3-4 | +2 |\n| Co-occurrence count 1-2 | +1 |\n| Concepts are in different categories (cross-domain) | +2 |\n| Concepts share tags but live in different folders | +1 |\n| One or both concepts are tagged as hubs in `_insights.md` | +1 |\n| A synthesis would resolve a flagged contradiction | +2 |\n\nPick the top 5 candidates. If the user asked for a specific topic (\"synthesize everything about observability\"), filter candidates to that domain first.\n\n## Step 4: Draft Synthesis Pages\n\nFor each top candidate, create a page in `synthesis\u002F` using this template:\n\n```markdown\n---\ntitle: \u003CConcept A> × \u003CConcept B>\ncategory: synthesis\ntags: [\u003Cshared tags>, \u003Cdomain tags>]\nsources: [\u003Call pages that link to both>]\ncreated: TIMESTAMP\nupdated: TIMESTAMP\nsummary: \"Cross-cutting synthesis of how \u003CA> and \u003CB> interact, with implications for \u003Cdomain>.\"\nprovenance:\n  extracted: 0.2\n  inferred: 0.7\n  ambiguous: 0.1\n---\n\n# \u003CConcept A> × \u003CConcept B>\n\n## The Connection\n\n*What makes these two concepts worth synthesizing together — the non-obvious relationship that pages about each individually don't capture.*\n\n## Where They Co-occur\n\n*The pages and contexts where both appear. What situations bring them together.*\n\n## Cross-cutting Insight\n\n*The conclusion that only becomes visible when you look at both together. This is the point of the page — the thing you couldn't see from either concept page alone.*\n\n## Tensions and Trade-offs\n\n*Where the two concepts pull in opposite directions. Unresolved contradictions. Cases where applying one undermines the other.*\n\n## Open Questions\n\n*What this synthesis surfaces that the wiki doesn't yet have an answer for. Good candidates for future research.*\n\n## Related\n\n- [[\u003CConcept A>]]\n- [[\u003CConcept B>]]\n- [[\u003Cother related pages>]]\n```\n\n**Synthesis pages are mostly `^[inferred]`.** You are drawing connections across sources — that's synthesis by definition. Apply `^[inferred]` to cross-cutting conclusions and `^[ambiguous]` where sources disagree.\n\n**The title format is `A × B`** — this signals to readers that it's a synthesis page, not a page about either concept alone.\n\n## Step 5: Back-link from Source Pages\n\nFor each synthesis page you created, add a link to it from the two (or more) concept pages it synthesizes. In the concept page, add to its `## Related` section:\n\n```markdown\n- [[Concept A × Concept B]] — synthesis\n```\n\nIf the concept page has no `## Related` section, add one at the bottom.\n\n## Step 6: Report Synthesis Opportunities Not Taken\n\nAfter creating pages for the top 5, list the next 10 candidates in your output — pairs that scored well but you didn't write pages for. This gives the user visibility into what the wiki thinks is worth exploring without forcing every synthesis in one run.\n\nFormat:\n```\nSkipped (consider next time):\n- [[Caching]] × [[Consistency]] — co-occurs in 4 pages, cross-domain\n- [[Testing]] × [[Observability]] — co-occurs in 3 pages, shares tags\n...\n```\n\n## Step 7: Update Special Files\n\n**`index.md`** — Add entries for all new synthesis pages.\n\n**`log.md`** — Append:\n```\n- [TIMESTAMP] WIKI_SYNTHESIZE pages_scanned=N synthesis_created=M candidates_skipped=K\n```\n\n**`hot.md`** — Read `$OBSIDIAN_VAULT_PATH\u002Fhot.md` (create from the template in `wiki-ingest` if missing). Update **Recent Activity** with what was synthesized — e.g. \"Synthesized 5 cross-cutting pages: Caching × Consistency, Testing × Observability, …\". Update **Active Threads** with any open questions the synthesis surfaced. Update `updated` timestamp.\n\n## Quality Checklist\n\n- [ ] Every synthesis page has a `summary:` field (≤200 chars)\n- [ ] Every synthesis page links back to its source concepts\n- [ ] Source concept pages link forward to the synthesis page\n- [ ] No synthesis page just restates what's already on the source pages — it must add a cross-cutting insight\n- [ ] `index.md` and `log.md` updated\n- [ ] `hot.md` updated\n\n## Tips\n\n- **A synthesis page that only summarizes its sources is useless.** The value is the connection — the thing neither source page says explicitly.\n- **Don't synthesize for synthesis's sake.** If two concepts just happen to appear together a lot without a real conceptual link, skip them.\n- **Three-way syntheses are powerful but rare.** Only create them when three concepts form a genuine triangle of mutual influence — not just because all three appear in the same project page.\n- **Check `_insights.md` first.** The wiki-status skill may have already flagged synthesis candidates there — start with those before running the co-occurrence scan from scratch.\n","# Wiki Synthesize — First-Class Synthesis Discovery\n\nYou are scanning the wiki for concepts that co-occur across many pages but have no dedicated synthesis page connecting them. Your job is to surface these gaps and fill the most valuable ones with cross-cutting synthesis pages.\n\n## Before You Start\n\n1. Read `~\u002F.obsidian-wiki\u002Fconfig` (preferred) or `.env` (fallback) to get `OBSIDIAN_VAULT_PATH`.\n2. Read `index.md` to get the full page inventory.\n3. Read `hot.md` if it exists — it surfaces recent activity and active threads that may already point to synthesis opportunities.\n4. Read `_meta\u002Ftaxonomy.md` to understand the tag vocabulary.\n\n## Step 1: Build the Co-occurrence Map\n\nScan every non-special page in the vault (skip `index.md`, `log.md`, `hot.md`, `_insights.md`, `_meta\u002F*`, `_archives\u002F*`, `_raw\u002F*`).\n\nFor each page, collect:\n- All `[[wikilinks]]` it contains (outgoing links)\n- Its `tags` frontmatter\n- Its `category` frontmatter\n\nBuild a co-occurrence matrix: for every pair of concept\u002Fentity pages (A, B), count how many other pages link to **both** A and B. This is their co-occurrence score.\n\nYou don't need to be exhaustive — aim for the top 20-30 pairs by co-occurrence score. Use Grep to find backlinks efficiently:\n\n```bash\ngrep -rl \"\\[\\[ConceptA\\]\\]\" \"$OBSIDIAN_VAULT_PATH\" --include=\"*.md\"\n```\n\nRun this for your top candidate concepts and intersect the result sets.\n\n## Step 2: Filter Out Already-Synthesized Pairs\n\nCheck the `synthesis\u002F` directory for existing pages. For each existing synthesis page:\n- Read its `sources` frontmatter or its body for `[[wikilinks]]`\n- Mark those concept pairs as already covered\n\nRemove covered pairs from your candidate list.\n\n## Step 3: Score and Rank Candidates\n\nFor each remaining candidate pair (or cluster of 3+), assign a synthesis value score:\n\n| Signal | Points |\n|---|---|\n| Co-occurrence count ≥ 5 | +3 |\n| Co-occurrence count 3-4 | +2 |\n| Co-occurrence count 1-2 | +1 |\n| Concepts are in different categories (cross-domain) | +2 |\n| Concepts share tags but live in different folders | +1 |\n| One or both concepts are tagged as hubs in `_insights.md` | +1 |\n| A synthesis would resolve a flagged contradiction | +2 |\n\nPick the top 5 candidates. If the user asked for a specific topic (\"synthesize everything about observability\"), filter candidates to that domain first.\n\n## Step 4: Draft Synthesis Pages\n\nFor each top candidate, create a page in `synthesis\u002F` using this template:\n\n```markdown\n---\ntitle: \u003CConcept A> × \u003CConcept B>\ncategory: synthesis\ntags: [\u003Cshared tags>, \u003Cdomain tags>]\nsources: [\u003Call pages that link to both>]\ncreated: TIMESTAMP\nupdated: TIMESTAMP\nsummary: \"Cross-cutting synthesis of how \u003CA> and \u003CB> interact, with implications for \u003Cdomain>.\"\nprovenance:\n  extracted: 0.2\n  inferred: 0.7\n  ambiguous: 0.1\n---\n\n# \u003CConcept A> × \u003CConcept B>\n\n## The Connection\n\n*What makes these two concepts worth synthesizing together — the non-obvious relationship that pages about each individually don't capture.*\n\n## Where They Co-occur\n\n*The pages and contexts where both appear. What situations bring them together.*\n\n## Cross-cutting Insight\n\n*The conclusion that only becomes visible when you look at both together. This is the point of the page — the thing you couldn't see from either concept page alone.*\n\n## Tensions and Trade-offs\n\n*Where the two concepts pull in opposite directions. Unresolved contradictions. Cases where applying one undermines the other.*\n\n## Open Questions\n\n*What this synthesis surfaces that the wiki doesn't yet have an answer for. Good candidates for future research.*\n\n## Related\n\n- [[\u003CConcept A>]]\n- [[\u003CConcept B>]]\n- [[\u003Cother related pages>]]\n```\n\n**Synthesis pages are mostly `^[inferred]`.** You are drawing connections across sources — that's synthesis by definition. Apply `^[inferred]` to cross-cutting conclusions and `^[ambiguous]` where sources disagree.\n\n**The title format is `A × B`** — this signals to readers that it's a synthesis page, not a page about either concept alone.\n\n## Step 5: Back-link from Source Pages\n\nFor each synthesis page you created, add a link to it from the two (or more) concept pages it synthesizes. In the concept page, add to its `## Related` section:\n\n```markdown\n- [[Concept A × Concept B]] — synthesis\n```\n\nIf the concept page has no `## Related` section, add one at the bottom.\n\n## Step 6: Report Synthesis Opportunities Not Taken\n\nAfter creating pages for the top 5, list the next 10 candidates in your output — pairs that scored well but you didn't write pages for. This gives the user visibility into what the wiki thinks is worth exploring without forcing every synthesis in one run.\n\nFormat:\n```\nSkipped (consider next time):\n- [[Caching]] × [[Consistency]] — co-occurs in 4 pages, cross-domain\n- [[Testing]] × [[Observability]] — co-occurs in 3 pages, shares tags\n...\n```\n\n## Step 7: Update Special Files\n\n**`index.md`** — Add entries for all new synthesis pages.\n\n**`log.md`** — Append:\n```\n- [TIMESTAMP] WIKI_SYNTHESIZE pages_scanned=N synthesis_created=M candidates_skipped=K\n```\n\n**`hot.md`** — Read `$OBSIDIAN_VAULT_PATH\u002Fhot.md` (create from the template in `wiki-ingest` if missing). Update **Recent Activity** with what was synthesized — e.g. \"Synthesized 5 cross-cutting pages: Caching × Consistency, Testing × Observability, …\". Update **Active Threads** with any open questions the synthesis surfaced. Update `updated` timestamp.\n\n## Quality Checklist\n\n- [ ] Every synthesis page has a `summary:` field (≤200 chars)\n- [ ] Every synthesis page links back to its source concepts\n- [ ] Source concept pages link forward to the synthesis page\n- [ ] No synthesis page just restates what's already on the source pages — it must add a cross-cutting insight\n- [ ] `index.md` and `log.md` updated\n- [ ] `hot.md` updated\n\n## Tips\n\n- **A synthesis page that only summarizes its sources is useless.** The value is the connection — the thing neither source page says explicitly.\n- **Don't synthesize for synthesis's sake.** If two concepts just happen to appear together a lot without a real conceptual link, skip them.\n- **Three-way syntheses are powerful but rare.** Only create them when three concepts form a genuine triangle of mutual influence — not just because all three appear in the same project page.\n- **Check `_insights.md` first.** The wiki-status skill may have already flagged synthesis candidates there — start with those before running the co-occurrence scan from scratch.\n",{"name":5,"description":7},"main","3c24fc2c035029b08c7326774bee3fef8fb95566",".agents\u002Fskills\u002Fwiki-synthesize",0,"https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto","https:\u002F\u002Fgithub.com\u002Fsaski","http:\u002F\u002Fsaski.com","2026-11-12 20:09:16",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add saski\u002Farnesto --skill wiki-synthesize",{"tool":37,"command":38},"bunx","bunx skills add saski\u002Farnesto --skill wiki-synthesize",{"tool":40,"command":41},"pnpm","pnpm dlx skills add saski\u002Farnesto --skill wiki-synthesize","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwiki-synthesize\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":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M7AT7F5FSHNAMFMF01N0QA1X","visualize","Use \u002Fvisualize for creating compact charts, diagrams, or other visuals inline as part of the conversation itself. It chooses among Markdown tables, Mermaid, inline HTML, and other supported in-transcript forms. Use Canvas for durable artifacts outside the transcript that users may revisit, refine, or share.","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fvisualize\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"01M7AT79MHSAR3JDDMP7DGERM9","update-cursor-settings","Modify Cursor\u002FVSCode user settings in settings.json. Use when you want to change editor settings, preferences, configuration, themes, font size, tab size, format on save, auto save, keybindings, or any settings.json values.","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fupdate-cursor-settings\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M7AT73WF3Y22E0FKYAMCCJES","update-cli-config","View and modify Cursor CLI configuration settings in ~\u002F.cursor\u002Fcli-config.json. Use when the user wants to change CLI settings, configure permissions, switch approval mode, enable vim mode, toggle display options, configure sandbox, or manage any CLI preferences.","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fupdate-cli-config\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M7AT6F3FBP85AJJ5BJNR8B5W","statusline","Configure a custom status line in the CLI. Use when the user mentions status line, statusline, statusLine, CLI status bar, prompt footer customization, or wants to add session context above the prompt.","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fstatusline\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M7AT6D24QFS5XRAFN8S5XJ7W","split-to-prs","Split current work into small reviewable PRs. Use when the user asks to split a chat, set of changes, branch, or PR.","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fsplit-to-prs\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M7AT69FYFN84XZKW452JV5DF","shell","Runs the rest of a \u002Fshell request as a literal shell command. Use only when the user explicitly invokes \u002Fshell and wants the following text executed directly in the terminal.","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fshell\u002FSKILL.md",[],[]]