[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71JRGRC3Y5BZR369BWD38QG":3,"skill-same:01M71JRGRC3Y5BZR369BWD38QG":79},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":5,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":48,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M71JRGRC3Y5BZR369BWD38QG","vault-resync",null,"Re-pull all of the user's external capture sources into their Obsidian vault inbox and refresh the Command Center dashboards. Use this whenever the user asks to \"re-sync\", \"resync\", \"pull new stuff\", \"update my inbox\u002Fvault\", \"refresh my tasks\", \"what's new in Feishu\u002FWeChat\u002Fmy tabs\", \"catch me up\", or \"pull from the providers again\" — even if they only name one source, default to refreshing all of them unless they scope it down. The sources are: Feishu (lark-cli), WeChat self-chat (chatlog), Zen browser tabs (session decode), and active Claude Code sessions (the AI build queue). This skill encodes hard-won auth\u002Fformat gotchas that are easy to get wrong — always consult it before touching these sources rather than improvising.","caezium\u002Fskills","caezium","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113233555?v=4","01M71JB77ZPBAWEK009Y2W8BP7","Henry Zhang","01M71JB792NVXCWSYD27HQ0964",3,"MIT","https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fvault-resync\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"vault resync","vault","wechat","chatlog","new","zen","command center","re","sources","scope","get","obsidian","default","up","only","claude code sessions","inbox","code","tasks","auth","2026-11-10 10:12:30",false,"---\nname: vault-resync\ndescription: >-\n  Re-pull all of the user's external capture sources into their Obsidian vault inbox and refresh\n  the Command Center dashboards. Use this whenever the user asks to \"re-sync\", \"resync\", \"pull\n  new stuff\", \"update my inbox\u002Fvault\", \"refresh my tasks\", \"what's new in Feishu\u002FWeChat\u002Fmy tabs\",\n  \"catch me up\", or \"pull from the providers again\" — even if they only name one source, default\n  to refreshing all of them unless they scope it down. The sources are: Feishu (lark-cli), WeChat\n  self-chat (chatlog), Zen browser tabs (session decode), and active Claude Code sessions (the AI\n  build queue). This skill encodes hard-won auth\u002Fformat gotchas that are easy to get wrong — always\n  consult it before touching these sources rather than improvising.\n---\n\n# Vault re-sync\n\nThis pulls the user's scattered capture sources into one place — the Obsidian vault inbox — and\nrefreshes the dashboards they read. The whole point of the vault system is that they shouldn't have\nto hold \"what's new across Feishu \u002F WeChat \u002F ~1500 browser tabs \u002F my Claude projects\" in their head.\nThis skill is the recurring sweep that keeps that promise.\n\n**User-specific values** (vault path, Feishu app details, the WeChat self-chat hint) live in\n`local.private.md` next to this SKILL.md — it's gitignored and machine-local, kept out of the public\nrepo on purpose. Read it at the start of a run. Where a value can be *discovered* at runtime instead\nof stored, prefer that (noted per-source below). `$VAULT` below = the vault root from the sidecar.\n\n## The four sources → where they land\n\n| Source | Tool | Output note |\n|---|---|---|\n| Feishu tasks + all-chat messages | `lark-cli` (read-only scopes) | `01_inbox\u002Ffeishu\u002Ffeishu-inbox-\u003Cdate>.md` + `feishu-messages-\u003Cdate>.md` |\n| WeChat self-saves | `chatlog` HTTP API | `01_inbox\u002Fwechat\u002Fwechat-inbox-\u003Cdate>.md` |\n| Zen browser tabs | `scripts\u002Fdecode_zen_tabs.py` | `01_inbox\u002Ftabs\u002Fzen-tabs-\u003Cdate>.md` |\n| Active Claude sessions | `list_sessions` MCP | `01_inbox\u002Fprojects\u002Fclaude-projects.md` (the AI Build Queue) |\n\n`\u003Cdate>` is today as `YYYY-MM-DD`. Always read the previous dated note first so you can frame the\npull as \"what's new since last sync\" rather than re-dumping everything.\n\n## Orchestration pattern (do it in this order)\n\n1. **Snapshot first.** `cd \"$VAULT\" && git add -A && git commit -m \"snapshot before re-sync\"`. This\n   gives a restore point before you write anything.\n2. **Pre-flight: disk space.** See \"Disk pre-flight\" — a full disk silently breaks everything,\n   including your own shell. Check before you start.\n3. **Fan out the slow pulls.** Feishu and WeChat each involve many API calls and per-conversation\n   summarization — launch them as **parallel background subagents** (one per source) using the prompts\n   in `references\u002Fsources.md`, so they run while you do the fast local work.\n4. **Do the fast local pulls inline** while the agents run: decode Zen tabs (one script call) and\n   rebuild the AI Build Queue from `list_sessions`.\n5. **Fold in the agent results** as they land. Read each agent's summary; don't re-read the full note\n   unless something looks off.\n6. **Update the Command Center.** Repoint the capture-source links in `homepage.md` to the new dated\n   notes, and surface any genuinely actionable finding (a deadline, an escalation) onto `Tasks Board.md`\n   with an area tag + due date — don't let a real action item rot inside a digest.\n7. **Commit + push.** `git add -A && git commit -m \"Re-sync all capture sources (\u003Cdate>): ...\" && git push`.\n   If push fails with an HTTP\u002F2 framing error, retry with `git -c http.version=HTTP\u002F1.1 push`.\n\nScale to what was asked. \"Re-sync everything\" → all four. \"What's new in Feishu\" → just that one,\nstill following its source rules.\n\n## Disk pre-flight\n\nA 100%-full disk on macOS makes the shell itself fail (`ENOSPC: no space left on device`) — commands\ncan't even write their output, so you'll be blocked before you start. If a trivial `Bash` call errors\nwith ENOSPC, the disk is the problem, not your command.\n\nThe user has **Burrow** for exactly this — its MCP tools run out-of-process so they work even when the\nshell can't. Use `burrow_doctor` (read-only health) and `burrow_analyze` (size-ranked tree) to see the\nsituation, and `burrow_clean` to clear caches. Caches rarely free enough alone; the big wins are usually\nVM images, app DB backups (e.g. `~\u002FLibrary\u002FApplication Support\u002FDayflow\u002Fbackups` + timestamped\n`Dayflow.backup-*` copies), and stale build dirs. **Only auto-delete caches.** For real user data — VMs,\nproject folders, app data — show the user the sizes and let them choose. Never nuke a directory you\ndidn't create without their say-so.\n\n## Per-source details\n\nEach source has non-obvious auth\u002Fformat traps. Read `references\u002Fsources.md` before pulling — it has the\nexact commands, the subagent prompts, and the gotchas. The traps that bite hardest:\n\n- **Feishu — read-only scopes ONLY.** Re-auth (only if needed) with\n  `lark-cli auth login --scope task:task:read,im:message:readonly,im:chat:read,contact:user.base:readonly`.\n  **Never use `--domain`** — that requests *write* scopes, and authorizing write scopes triggers a slow\n  enterprise admin review that has cost hours. A `needs_refresh` token auto-refreshes on the first valid\n  API call; only if that fails do you re-auth (you can drive the logged-in browser to click Authorize).\n  App\u002Fenterprise IDs and the dev-console URL are in `local.private.md`.\n- **WeChat — discover the self-chat at runtime.** It's the chat flagged `isSelf` in the chatlog session\n  list, NOT `filehelper` \u002F 文件传输助手 (which is empty). The `chatlog` server must be running\n  (`chatlog server`, binary at `~\u002Fgo\u002Fbin\u002Fchatlog`) on `http:\u002F\u002F127.0.0.1:5030`. Quote URLs in curl — a bare\n  `?` gets eaten by zsh globbing and looks like a dead server when it isn't.\n- **Zen tabs — use the bundled script.** `python3 scripts\u002Fdecode_zen_tabs.py --out \"$VAULT\u002F01_inbox\u002Ftabs\u002Fzen-tabs-\u003Cdate>.md\" --date \u003Cdate>`.\n  It handles the mozlz4 decode with no dependencies. Don't `pip install lz4` (PEP 668 blocks it).\n- **Claude sessions — dedupe by folder, flag status.** `list_sessions` returns ~85 with heavy duplication\n  (recurring \"weekly sync\" etc.) and many merged-PR sessions that are actually done. Group by `cwd`,\n  collapse dupes, flag ✅-done (merged PRs) as archive candidates, surface what's new since last sync.\n\n## Quality bars (what makes this \"the same high quality\")\n\n- **Dedupe and categorize, don't dump.** 1,500 raw URLs or 250 raw messages is just moving the mess.\n  Bucket, summarize, count. The note should be skimmable in 30 seconds.\n- **Surface deadlines as tasks.** A real commitment with a clock (a demo date, an escalating reminder)\n  belongs on the board with a 📅 due date, not buried in prose.\n- **Frame as a delta.** \"9 new since 06-23\" beats re-listing 259 old items. Read the prior note first.\n- **Keep Chinese text as-is** but make it scannable.\n- **Don't loop on Feishu auth.** If read-only re-auth still fails, stop and tell the user — repeated\n  login attempts re-trigger the admin-review trap. One clean attempt, then escalate.\n\nAfter a re-sync, give a tight recap: what each source surfaced, the count of new items, and the one or\ntwo things that actually need attention this week.\n","# Vault re-sync\n\nThis pulls the user's scattered capture sources into one place — the Obsidian vault inbox — and\nrefreshes the dashboards they read. The whole point of the vault system is that they shouldn't have\nto hold \"what's new across Feishu \u002F WeChat \u002F ~1500 browser tabs \u002F my Claude projects\" in their head.\nThis skill is the recurring sweep that keeps that promise.\n\n**User-specific values** (vault path, Feishu app details, the WeChat self-chat hint) live in\n`local.private.md` next to this SKILL.md — it's gitignored and machine-local, kept out of the public\nrepo on purpose. Read it at the start of a run. Where a value can be *discovered* at runtime instead\nof stored, prefer that (noted per-source below). `$VAULT` below = the vault root from the sidecar.\n\n## The four sources → where they land\n\n| Source | Tool | Output note |\n|---|---|---|\n| Feishu tasks + all-chat messages | `lark-cli` (read-only scopes) | `01_inbox\u002Ffeishu\u002Ffeishu-inbox-\u003Cdate>.md` + `feishu-messages-\u003Cdate>.md` |\n| WeChat self-saves | `chatlog` HTTP API | `01_inbox\u002Fwechat\u002Fwechat-inbox-\u003Cdate>.md` |\n| Zen browser tabs | `scripts\u002Fdecode_zen_tabs.py` | `01_inbox\u002Ftabs\u002Fzen-tabs-\u003Cdate>.md` |\n| Active Claude sessions | `list_sessions` MCP | `01_inbox\u002Fprojects\u002Fclaude-projects.md` (the AI Build Queue) |\n\n`\u003Cdate>` is today as `YYYY-MM-DD`. Always read the previous dated note first so you can frame the\npull as \"what's new since last sync\" rather than re-dumping everything.\n\n## Orchestration pattern (do it in this order)\n\n1. **Snapshot first.** `cd \"$VAULT\" && git add -A && git commit -m \"snapshot before re-sync\"`. This\n   gives a restore point before you write anything.\n2. **Pre-flight: disk space.** See \"Disk pre-flight\" — a full disk silently breaks everything,\n   including your own shell. Check before you start.\n3. **Fan out the slow pulls.** Feishu and WeChat each involve many API calls and per-conversation\n   summarization — launch them as **parallel background subagents** (one per source) using the prompts\n   in `references\u002Fsources.md`, so they run while you do the fast local work.\n4. **Do the fast local pulls inline** while the agents run: decode Zen tabs (one script call) and\n   rebuild the AI Build Queue from `list_sessions`.\n5. **Fold in the agent results** as they land. Read each agent's summary; don't re-read the full note\n   unless something looks off.\n6. **Update the Command Center.** Repoint the capture-source links in `homepage.md` to the new dated\n   notes, and surface any genuinely actionable finding (a deadline, an escalation) onto `Tasks Board.md`\n   with an area tag + due date — don't let a real action item rot inside a digest.\n7. **Commit + push.** `git add -A && git commit -m \"Re-sync all capture sources (\u003Cdate>): ...\" && git push`.\n   If push fails with an HTTP\u002F2 framing error, retry with `git -c http.version=HTTP\u002F1.1 push`.\n\nScale to what was asked. \"Re-sync everything\" → all four. \"What's new in Feishu\" → just that one,\nstill following its source rules.\n\n## Disk pre-flight\n\nA 100%-full disk on macOS makes the shell itself fail (`ENOSPC: no space left on device`) — commands\ncan't even write their output, so you'll be blocked before you start. If a trivial `Bash` call errors\nwith ENOSPC, the disk is the problem, not your command.\n\nThe user has **Burrow** for exactly this — its MCP tools run out-of-process so they work even when the\nshell can't. Use `burrow_doctor` (read-only health) and `burrow_analyze` (size-ranked tree) to see the\nsituation, and `burrow_clean` to clear caches. Caches rarely free enough alone; the big wins are usually\nVM images, app DB backups (e.g. `~\u002FLibrary\u002FApplication Support\u002FDayflow\u002Fbackups` + timestamped\n`Dayflow.backup-*` copies), and stale build dirs. **Only auto-delete caches.** For real user data — VMs,\nproject folders, app data — show the user the sizes and let them choose. Never nuke a directory you\ndidn't create without their say-so.\n\n## Per-source details\n\nEach source has non-obvious auth\u002Fformat traps. Read `references\u002Fsources.md` before pulling — it has the\nexact commands, the subagent prompts, and the gotchas. The traps that bite hardest:\n\n- **Feishu — read-only scopes ONLY.** Re-auth (only if needed) with\n  `lark-cli auth login --scope task:task:read,im:message:readonly,im:chat:read,contact:user.base:readonly`.\n  **Never use `--domain`** — that requests *write* scopes, and authorizing write scopes triggers a slow\n  enterprise admin review that has cost hours. A `needs_refresh` token auto-refreshes on the first valid\n  API call; only if that fails do you re-auth (you can drive the logged-in browser to click Authorize).\n  App\u002Fenterprise IDs and the dev-console URL are in `local.private.md`.\n- **WeChat — discover the self-chat at runtime.** It's the chat flagged `isSelf` in the chatlog session\n  list, NOT `filehelper` \u002F 文件传输助手 (which is empty). The `chatlog` server must be running\n  (`chatlog server`, binary at `~\u002Fgo\u002Fbin\u002Fchatlog`) on `http:\u002F\u002F127.0.0.1:5030`. Quote URLs in curl — a bare\n  `?` gets eaten by zsh globbing and looks like a dead server when it isn't.\n- **Zen tabs — use the bundled script.** `python3 scripts\u002Fdecode_zen_tabs.py --out \"$VAULT\u002F01_inbox\u002Ftabs\u002Fzen-tabs-\u003Cdate>.md\" --date \u003Cdate>`.\n  It handles the mozlz4 decode with no dependencies. Don't `pip install lz4` (PEP 668 blocks it).\n- **Claude sessions — dedupe by folder, flag status.** `list_sessions` returns ~85 with heavy duplication\n  (recurring \"weekly sync\" etc.) and many merged-PR sessions that are actually done. Group by `cwd`,\n  collapse dupes, flag ✅-done (merged PRs) as archive candidates, surface what's new since last sync.\n\n## Quality bars (what makes this \"the same high quality\")\n\n- **Dedupe and categorize, don't dump.** 1,500 raw URLs or 250 raw messages is just moving the mess.\n  Bucket, summarize, count. The note should be skimmable in 30 seconds.\n- **Surface deadlines as tasks.** A real commitment with a clock (a demo date, an escalating reminder)\n  belongs on the board with a 📅 due date, not buried in prose.\n- **Frame as a delta.** \"9 new since 06-23\" beats re-listing 259 old items. Read the prior note first.\n- **Keep Chinese text as-is** but make it scannable.\n- **Don't loop on Feishu auth.** If read-only re-auth still fails, stop and tell the user — repeated\n  login attempts re-trigger the admin-review trap. One clean attempt, then escalate.\n\nAfter a re-sync, give a tight recap: what each source surfaced, the count of new items, and the one or\ntwo things that actually need attention this week.\n",{"name":5,"description":7},"main","6ef866230c1ba3459fd08fc65141dfd37fffd41a",0,"https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills","https:\u002F\u002Fskills.henryzh.dev","https:\u002F\u002Fgithub.com\u002Fcaezium","henryzh.dev","quant, data science, full-stack, robotics.\r\nbuilding cool stuff","2026-08-24 19:21:44",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add caezium\u002Fskills --skill vault-resync",{"tool":59,"command":60},"bunx","bunx skills add caezium\u002Fskills --skill vault-resync",{"tool":62,"command":63},"pnpm","pnpm dlx skills add caezium\u002Fskills --skill vault-resync","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fvault-resync\u002FSKILL.md",true,[67,73],{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fsources.md","REFERENCE","参考文档",8226,"https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fvault-resync\u002Freferences\u002Fsources.md",{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"scripts\u002Fdecode_zen_tabs.py","SCRIPT","脚本",5585,"https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fvault-resync\u002Fscripts\u002Fdecode_zen_tabs.py",[80,104,132,148,167,188],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":96,"publishedAt":39},"01M71JT4RYCAS18RF6003YYR1D","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fwriting-for-agents\u002FSKILL.md",[86,91],{"categoryNo":87,"categoryName":88,"taxonomyType":89,"taxonomyTypeDesc":90},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":92,"categoryName":93,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[97,98,99,100,101,102,103],"writing for agents","for","writing","editing","use","documents","when",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":113,"publishedAt":39},"01M71JT0GES4AZ5ADH8EADNN1Z","wrangler","Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fwrangler\u002FSKILL.md",[110],{"categoryNo":111,"categoryName":112,"taxonomyType":89,"taxonomyTypeDesc":90},"01JBSEEDCAT000000000000010","后端与接口",[106,114,115,116,117,118,119,120,121,122,123,124,125,98,126,127,128,129,130,131],"cloudflare","d1","knowledge","workflows","cli","secrets","commands","syntax","cloudflare workers","r2","queues","running","containers","correct","load","workers","best practices","store",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":39},"01M71JSWX4R203M32K9A18AAW8","workers-best-practices","Reviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from Cloudflare docs over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fworkers-best-practices\u002FSKILL.md",[],[139,129,130,140,141,142,98,114,143,116,23,106,99,128,103,36,144,145,146,147],"workers best practices","observability","reviews","promises","worker","common","streaming","state","anti-patterns",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":154,"publishedAt":39},"01M71JST6P88MXGT2MWDTPJGEG","wizard","Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.","https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fwizard\u002FSKILL.md",[],[150,125,155,98,32,156,157,33,101,158,103,159,160,161,162,163,164,165,166,119],"setting","ci","provisioning infrastructure","invoke","Bash","one","interactive","can","credentials","dashboard","generate","human",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":171,"sourceHtmlUrl":172,"categories":173,"keywords":174,"publishedAt":39},"01M71JSQ95S7BQ61DAPN95X2W4","why","Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available evidence sources, searches each relevant category, and returns a cited read on decisions and tradeoffs. Use how for runtime behavior.","https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fwhy\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fwhy\u002FSKILL.md",[],[169,27,175,176,177,98,178,179,101,180,181,182,183,184,185,186,187],"thresholds","evidence","relevant","runtime","design","decisions","work","how","behavior","read","data","rationale","returns",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":192,"categories":193,"keywords":197,"publishedAt":39},"01M71JSMHFVSH8HK8GXN6YAX6J","week-prep","Generate a briefing with calendar, tasks, and attention flags. Use for \"week prep\", \"briefing\", or \"what's on this week\".","https:\u002F\u002Fgithub.com\u002Fcaezium\u002Fskills\u002Fblob\u002Fmain\u002Fweek-prep\u002FSKILL.md",[194],{"categoryNo":195,"categoryName":196,"taxonomyType":89,"taxonomyTypeDesc":90},"01JBSEEDCAT000000000000023","Skill与智能体开发",[198,199,200,201,29,98,202,203,204,205,101,159,37,206,207,165,208,184,209,210],"week prep","prep","deep","attention","search","messages","briefing","MCP","with","slack","calendar","flags","grep"]