[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AT1ACRY0EWQMSG4ERF9HHH":3,"skill-same:01M7AT1ACRY0EWQMSG4ERF9HHH":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},"01M7AT1ACRY0EWQMSG4ERF9HHH","wiki-rebuild",null,"Archive existing wiki knowledge and rebuild from scratch, or restore from a previous archive. Use this skill when the user wants to start fresh, rebuild the wiki from all sources, archive current knowledge before a major change, or restore an older version. Triggers on \"rebuild the wiki\", \"start over\", \"archive and rebuild\", \"restore from archive\", \"nuke and repave\", \"clean rebuild\". Also use when the wiki has drifted too far from sources and incremental fixes won't cut it.","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-rebuild\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: wiki-rebuild\ndescription: >\n  Archive existing wiki knowledge and rebuild from scratch, or restore from a previous archive.\n  Use this skill when the user wants to start fresh, rebuild the wiki from all sources, archive current\n  knowledge before a major change, or restore an older version. Triggers on \"rebuild the wiki\",\n  \"start over\", \"archive and rebuild\", \"restore from archive\", \"nuke and repave\", \"clean rebuild\".\n  Also use when the wiki has drifted too far from sources and incremental fixes won't cut it.\n---\n\n# Wiki Rebuild — Archive, Rebuild, Restore\n\nYou are performing a destructive operation on the wiki. Always archive first, always confirm with the user before proceeding.\n\n## Before You Start\n\n1. Read `.env` to get `OBSIDIAN_VAULT_PATH`\n2. Read `.manifest.json` to understand current state\n3. **Confirm the user's intent.** This skill supports three modes:\n   - **Archive only** — snapshot current wiki, no rebuild\n   - **Archive + Rebuild** — snapshot, then reprocess all sources from scratch\n   - **Restore** — bring back a previous archive\n\n## The Archive System\n\nArchives live at `$OBSIDIAN_VAULT_PATH\u002F_archives\u002F`. Each archive is a timestamped directory containing a full copy of the wiki state at that point.\n\n```\n$OBSIDIAN_VAULT_PATH\u002F\n├── _archives\u002F\n│   ├── 2026-04-01T10-30-00Z\u002F\n│   │   ├── archive-meta.json\n│   │   ├── concepts\u002F\n│   │   ├── entities\u002F\n│   │   ├── skills\u002F\n│   │   ├── references\u002F\n│   │   ├── synthesis\u002F\n│   │   ├── journal\u002F\n│   │   ├── projects\u002F\n│   │   ├── index.md\n│   │   ├── log.md\n│   │   └── .manifest.json\n│   └── 2026-03-15T08-00-00Z\u002F\n│       └── ...\n├── concepts\u002F          ← live wiki\n├── entities\u002F\n└── ...\n```\n\n### archive-meta.json\n\n```json\n{\n  \"archived_at\": \"2026-04-06T10:30:00Z\",\n  \"reason\": \"rebuild\",\n  \"total_pages\": 87,\n  \"total_sources\": 42,\n  \"total_projects\": 6,\n  \"vault_path\": \"\u002FUsers\u002Fname\u002FKnowledge\",\n  \"manifest_snapshot\": \".manifest.json\"\n}\n```\n\n## Mode 1: Archive Only\n\nWhen the user wants to snapshot the current state without rebuilding.\n\n### Steps:\n\n1. Create archive directory: `_archives\u002FYYYY-MM-DDTHH-MM-SSZ\u002F`\n2. Copy all category directories, `index.md`, `log.md`, `.manifest.json`, and `projects\u002F` into the archive\n3. Write `archive-meta.json` with reason `\"snapshot\"`\n4. Append to `log.md`:\n   ```\n   - [TIMESTAMP] ARCHIVE reason=\"snapshot\" pages=87 destination=\"_archives\u002F2026-04-06T10-30-00Z\"\n   ```\n5. Report: \"Archived 87 pages. Current wiki is untouched.\"\n\n## Mode 2: Archive + Rebuild\n\nWhen the user wants to start fresh. This is the full sequence:\n\n### Step 1: Archive current state\n\nSame as Mode 1 above, but with reason `\"rebuild\"`.\n\n### Step 2: Clear live wiki\n\nRemove all content from the category directories (`concepts\u002F`, `entities\u002F`, `skills\u002F`, etc.) and the `projects\u002F` directory. Keep:\n- `_archives\u002F` (obviously)\n- `.obsidian\u002F` (Obsidian config)\n- `.env` (if present in vault)\n\nReset `index.md` to the empty template. Reset `log.md` with just the rebuild entry. Delete `.manifest.json` (it'll be recreated during ingest).\n\n### Step 3: Rebuild\n\nTell the user the vault is cleared and ready for a full re-ingest. They can now run:\n\n1. `wiki-status` — to see all sources as \"new\"\n2. `claude-history-ingest` — to reprocess Claude history\n3. `codex-history-ingest` — to reprocess Codex session history\n4. `wiki-ingest` — to reprocess documents\n5. `data-ingest` — to reprocess any other data\n\nEach of these will rebuild the manifest as they go.\n\n**Important:** Don't run the ingest yourself automatically. The user should choose what to re-ingest and in what order. Some sources may no longer be relevant.\n\n### Step 4: Log the rebuild\n\nAppend to `log.md`:\n```\n- [TIMESTAMP] REBUILD archived_to=\"_archives\u002F2026-04-06T10-30-00Z\" previous_pages=87\n```\n\n## Mode 3: Restore from Archive\n\nWhen the user wants to go back to a previous state.\n\n### Step 1: List available archives\n\nRead `_archives\u002F` directory. For each archive, read `archive-meta.json` and present:\n\n```markdown\n## Available Archives\n\n| Date | Reason | Pages | Sources |\n|---|---|---|---|\n| 2026-04-06 10:30 | rebuild | 87 | 42 |\n| 2026-03-15 08:00 | snapshot | 65 | 31 |\n```\n\n### Step 2: Confirm which archive to restore\n\nAsk the user which archive they want. Warn them that restoring will overwrite the current live wiki.\n\n### Step 3: Archive current state first\n\nBefore restoring, archive the current state (reason: `\"pre-restore\"`) so nothing is lost.\n\n### Step 4: Restore\n\n1. Clear the live wiki (same as Mode 2, Step 2)\n2. Copy all content from the chosen archive back into the live wiki directories\n3. Restore `index.md`, `log.md`, and `.manifest.json` from the archive\n4. Append to `log.md`:\n   ```\n   - [TIMESTAMP] RESTORE from=\"_archives\u002F2026-03-15T08-00-00Z\" pages_restored=65\n   ```\n\n### Step 5: Report\n\nTell the user what was restored and suggest running `wiki-lint` to check for any issues with the restored state.\n\n## Safety Rules\n\n1. **Always archive before destructive operations.** No exceptions.\n2. **Always confirm with the user** before clearing the live wiki.\n3. **Never delete archives** unless the user explicitly asks. Archives are cheap insurance.\n4. **The `.obsidian\u002F` directory is sacred.** Never touch it during archive\u002Frebuild\u002Frestore — it contains the user's Obsidian settings, plugins, and themes.\n5. If something goes wrong mid-rebuild, the archive is there. Tell the user they can restore.\n","# Wiki Rebuild — Archive, Rebuild, Restore\n\nYou are performing a destructive operation on the wiki. Always archive first, always confirm with the user before proceeding.\n\n## Before You Start\n\n1. Read `.env` to get `OBSIDIAN_VAULT_PATH`\n2. Read `.manifest.json` to understand current state\n3. **Confirm the user's intent.** This skill supports three modes:\n   - **Archive only** — snapshot current wiki, no rebuild\n   - **Archive + Rebuild** — snapshot, then reprocess all sources from scratch\n   - **Restore** — bring back a previous archive\n\n## The Archive System\n\nArchives live at `$OBSIDIAN_VAULT_PATH\u002F_archives\u002F`. Each archive is a timestamped directory containing a full copy of the wiki state at that point.\n\n```\n$OBSIDIAN_VAULT_PATH\u002F\n├── _archives\u002F\n│   ├── 2026-04-01T10-30-00Z\u002F\n│   │   ├── archive-meta.json\n│   │   ├── concepts\u002F\n│   │   ├── entities\u002F\n│   │   ├── skills\u002F\n│   │   ├── references\u002F\n│   │   ├── synthesis\u002F\n│   │   ├── journal\u002F\n│   │   ├── projects\u002F\n│   │   ├── index.md\n│   │   ├── log.md\n│   │   └── .manifest.json\n│   └── 2026-03-15T08-00-00Z\u002F\n│       └── ...\n├── concepts\u002F          ← live wiki\n├── entities\u002F\n└── ...\n```\n\n### archive-meta.json\n\n```json\n{\n  \"archived_at\": \"2026-04-06T10:30:00Z\",\n  \"reason\": \"rebuild\",\n  \"total_pages\": 87,\n  \"total_sources\": 42,\n  \"total_projects\": 6,\n  \"vault_path\": \"\u002FUsers\u002Fname\u002FKnowledge\",\n  \"manifest_snapshot\": \".manifest.json\"\n}\n```\n\n## Mode 1: Archive Only\n\nWhen the user wants to snapshot the current state without rebuilding.\n\n### Steps:\n\n1. Create archive directory: `_archives\u002FYYYY-MM-DDTHH-MM-SSZ\u002F`\n2. Copy all category directories, `index.md`, `log.md`, `.manifest.json`, and `projects\u002F` into the archive\n3. Write `archive-meta.json` with reason `\"snapshot\"`\n4. Append to `log.md`:\n   ```\n   - [TIMESTAMP] ARCHIVE reason=\"snapshot\" pages=87 destination=\"_archives\u002F2026-04-06T10-30-00Z\"\n   ```\n5. Report: \"Archived 87 pages. Current wiki is untouched.\"\n\n## Mode 2: Archive + Rebuild\n\nWhen the user wants to start fresh. This is the full sequence:\n\n### Step 1: Archive current state\n\nSame as Mode 1 above, but with reason `\"rebuild\"`.\n\n### Step 2: Clear live wiki\n\nRemove all content from the category directories (`concepts\u002F`, `entities\u002F`, `skills\u002F`, etc.) and the `projects\u002F` directory. Keep:\n- `_archives\u002F` (obviously)\n- `.obsidian\u002F` (Obsidian config)\n- `.env` (if present in vault)\n\nReset `index.md` to the empty template. Reset `log.md` with just the rebuild entry. Delete `.manifest.json` (it'll be recreated during ingest).\n\n### Step 3: Rebuild\n\nTell the user the vault is cleared and ready for a full re-ingest. They can now run:\n\n1. `wiki-status` — to see all sources as \"new\"\n2. `claude-history-ingest` — to reprocess Claude history\n3. `codex-history-ingest` — to reprocess Codex session history\n4. `wiki-ingest` — to reprocess documents\n5. `data-ingest` — to reprocess any other data\n\nEach of these will rebuild the manifest as they go.\n\n**Important:** Don't run the ingest yourself automatically. The user should choose what to re-ingest and in what order. Some sources may no longer be relevant.\n\n### Step 4: Log the rebuild\n\nAppend to `log.md`:\n```\n- [TIMESTAMP] REBUILD archived_to=\"_archives\u002F2026-04-06T10-30-00Z\" previous_pages=87\n```\n\n## Mode 3: Restore from Archive\n\nWhen the user wants to go back to a previous state.\n\n### Step 1: List available archives\n\nRead `_archives\u002F` directory. For each archive, read `archive-meta.json` and present:\n\n```markdown\n## Available Archives\n\n| Date | Reason | Pages | Sources |\n|---|---|---|---|\n| 2026-04-06 10:30 | rebuild | 87 | 42 |\n| 2026-03-15 08:00 | snapshot | 65 | 31 |\n```\n\n### Step 2: Confirm which archive to restore\n\nAsk the user which archive they want. Warn them that restoring will overwrite the current live wiki.\n\n### Step 3: Archive current state first\n\nBefore restoring, archive the current state (reason: `\"pre-restore\"`) so nothing is lost.\n\n### Step 4: Restore\n\n1. Clear the live wiki (same as Mode 2, Step 2)\n2. Copy all content from the chosen archive back into the live wiki directories\n3. Restore `index.md`, `log.md`, and `.manifest.json` from the archive\n4. Append to `log.md`:\n   ```\n   - [TIMESTAMP] RESTORE from=\"_archives\u002F2026-03-15T08-00-00Z\" pages_restored=65\n   ```\n\n### Step 5: Report\n\nTell the user what was restored and suggest running `wiki-lint` to check for any issues with the restored state.\n\n## Safety Rules\n\n1. **Always archive before destructive operations.** No exceptions.\n2. **Always confirm with the user** before clearing the live wiki.\n3. **Never delete archives** unless the user explicitly asks. Archives are cheap insurance.\n4. **The `.obsidian\u002F` directory is sacred.** Never touch it during archive\u002Frebuild\u002Frestore — it contains the user's Obsidian settings, plugins, and themes.\n5. If something goes wrong mid-rebuild, the archive is there. Tell the user they can restore.\n",{"name":5,"description":7},"main","3c24fc2c035029b08c7326774bee3fef8fb95566",".agents\u002Fskills\u002Fwiki-rebuild",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-rebuild",{"tool":37,"command":38},"bunx","bunx skills add saski\u002Farnesto --skill wiki-rebuild",{"tool":40,"command":41},"pnpm","pnpm dlx skills add saski\u002Farnesto --skill wiki-rebuild","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwiki-rebuild\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",[],[]]