[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77RC89FVPD7KMMXBGCV19AE":3,"skill-same:01M77RC89FVPD7KMMXBGCV19AE":59},{"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":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M77RC89FVPD7KMMXBGCV19AE","architecture",null,"Project architecture and file structure conventions for all process types.\nUse when: (1) Creating new files or modules, (2) Deciding where code should go,\n(3) Converting single-file components to directories, (4) Reviewing code for structure compliance,\n(5) Adding new bridges, services, agents, or workers.","finewood2008\u002Fcentaurai-team","finewood2008","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F212194470?v=4","01M75HGRZJ31P9W3T90VHFS1X8","Finewood","01M77RC50EAM5Q4E71MX8JRG7P",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Ffinewood2008\u002Fcentaurai-team\u002Fblob\u002Fteam\u002F.claude\u002Fskills\u002Farchitecture\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: architecture\ndescription: |\n  Project architecture and file structure conventions for all process types.\n  Use when: (1) Creating new files or modules, (2) Deciding where code should go,\n  (3) Converting single-file components to directories, (4) Reviewing code for structure compliance,\n  (5) Adding new bridges, services, agents, or workers.\n---\n\n# Architecture Skill\n\nDetermine correct file placement and structure for an Electron multi-process project.\n\n## Detailed References\n\n- **Renderer layer** (components, hooks, utils, pages, CSS): [references\u002Frenderer.md](references\u002Frenderer.md)\n- **Main process & shared layer** (bridges, services, worker, preload): [references\u002Fprocess.md](references\u002Fprocess.md)\n- **Project root & monorepo layout** (directory structure, migration status): [references\u002Fproject-layout.md](references\u002Fproject-layout.md)\n\n---\n\n## Decision Tree — Where Does New Code Go?\n\n```\nIs it UI (React components, hooks, pages)?\n  └── YES → packages\u002Fdesktop\u002Fsrc\u002Frenderer\u002F              → see references\u002Frenderer.md\n\nIs it an IPC handler responding to renderer calls?\n  └── YES → packages\u002Fdesktop\u002Fsrc\u002Fprocess\u002Fbridge\u002F        → see references\u002Fprocess.md\n\nIs it business logic running in the main process?\n  └── YES → packages\u002Fdesktop\u002Fsrc\u002Fprocess\u002Fservices\u002F      → see references\u002Fprocess.md\n\nIs it an AI platform connection (API client, message protocol)?\n  └── YES → packages\u002Fdesktop\u002Fsrc\u002Fprocess\u002Fagent\u002F\u003Cplatform>\u002F\n\nIs it a background task that runs in a worker thread?\n  └── YES → packages\u002Fdesktop\u002Fsrc\u002Fprocess\u002Fworker\u002F\n\nIs it used by BOTH main and renderer processes?\n  └── YES → packages\u002Fdesktop\u002Fsrc\u002Fcommon\u002F\n\nIs it an HTTP\u002FWebSocket endpoint?\n  └── YES → packages\u002Fdesktop\u002Fsrc\u002Fprocess\u002Fwebserver\u002F\n\nIs it a plugin\u002Fextension resolver or loader?\n  └── YES → packages\u002Fdesktop\u002Fsrc\u002Fprocess\u002Fextensions\u002F\n\nIs it a messaging channel (Lark, DingTalk, Telegram)?\n  └── YES → packages\u002Fdesktop\u002Fsrc\u002Fprocess\u002Fchannels\u002F\n```\n\n---\n\n## Process Boundary Rules\n\n**Hard rules — violating them causes runtime crashes.**\n\n| Process                                             | Can use                                                    | Cannot use                                      |\n| --------------------------------------------------- | ---------------------------------------------------------- | ----------------------------------------------- |\n| **Main** (`packages\u002Fdesktop\u002Fsrc\u002Fprocess\u002F`)          | Node.js, Electron main APIs, `fs`, `path`, `child_process` | DOM APIs (`document`, `window`, React)          |\n| **Renderer** (`packages\u002Fdesktop\u002Fsrc\u002Frenderer\u002F`)     | DOM APIs, React, browser APIs                              | Node.js APIs (`fs`, `path`), Electron main APIs |\n| **Worker** (`packages\u002Fdesktop\u002Fsrc\u002Fprocess\u002Fworker\u002F`) | Node.js APIs                                               | DOM APIs, Electron APIs                         |\n| **Preload** (`packages\u002Fdesktop\u002Fsrc\u002Fpreload\u002F`)       | `contextBridge`, `ipcRenderer`                             | DOM manipulation, Node.js `fs`                  |\n\nCross-process communication:\n\n- Main ↔ Renderer: IPC via `packages\u002Fdesktop\u002Fsrc\u002Fpreload\u002F` + `packages\u002Fdesktop\u002Fsrc\u002Fprocess\u002Fbridge\u002F*.ts`\n- Main ↔ Worker: fork protocol via `packages\u002Fdesktop\u002Fsrc\u002Fprocess\u002Fworker\u002FWorkerProtocol.ts`\n\n```typescript\n\u002F\u002F NEVER in renderer\nimport { something } from '@process\u002Fservices\u002Ffoo'; \u002F\u002F crashes at runtime\n\n\u002F\u002F Use IPC instead\nconst result = await window.api.someMethod(); \u002F\u002F goes through preload\n```\n\n---\n\n## Naming Conventions\n\n### Directories\n\n| Scope                              | Convention | Reason                                                  |\n| ---------------------------------- | ---------- | ------------------------------------------------------- |\n| **Renderer** component\u002Fmodule dirs | PascalCase | React convention — dir name = component name            |\n| **Everything else**                | lowercase  | Node.js convention                                      |\n| **Categorical dirs** (everywhere)  | lowercase  | `components\u002F`, `hooks\u002F`, `utils\u002F`, `services\u002F`          |\n| **Platform dirs** (everywhere)     | lowercase  | `acp\u002F`, `codex\u002F`, `gemini\u002F` — cross-process consistency |\n\n> Quick test: \"Inside `packages\u002Fdesktop\u002Fsrc\u002Frenderer\u002F` AND represents a specific component\u002Ffeature (not a category)?\" → PascalCase. Otherwise → lowercase.\n\n### Files\n\n| Content                   | Convention                      | Examples                              |\n| ------------------------- | ------------------------------- | ------------------------------------- |\n| React components, classes | PascalCase                      | `SettingsModal.tsx`, `CronService.ts` |\n| Hooks                     | camelCase with `use` prefix     | `useTheme.ts`, `useCronJobs.ts`       |\n| Utilities, helpers        | camelCase                       | `formatDate.ts`, `cronUtils.ts`       |\n| Entry points              | `index.ts` \u002F `index.tsx`        | Required for directory-based modules  |\n| Config, types, constants  | camelCase                       | `types.ts`, `constants.ts`            |\n| Styles                    | kebab-case or `Name.module.css` | `chat-layout.css`                     |\n\n---\n\n## Structural Rules\n\n1. **Directory size limit**: Max **10** direct children. Split into subdirectories by responsibility when approaching.\n2. **No single-file directories**: Merge into parent or related directory.\n3. **Single file vs directory**: If a component needs a private sub-component or hook, convert to a directory with `index.tsx`.\n4. **Page-private first**: Start code in `pages\u002F\u003CPageName>\u002F`. Promote to shared only when a second consumer appears.\n\n## Test File Mapping\n\nTests mirror source files in `tests\u002F` subdirectories:\n\n| Source                                                       | Test                                            |\n| ------------------------------------------------------------ | ----------------------------------------------- |\n| `packages\u002Fdesktop\u002Fsrc\u002Fprocess\u002Fservices\u002FCronService.ts`       | `tests\u002Funit\u002FcronService.test.ts`                |\n| `packages\u002Fdesktop\u002Fsrc\u002Frenderer\u002Fhooks\u002Fui\u002FuseAutoScroll.ts`    | `tests\u002Funit\u002FuseAutoScroll.dom.test.ts`          |\n| `packages\u002Fdesktop\u002Fsrc\u002Fprocess\u002Fextensions\u002FExtensionLoader.ts` | `tests\u002Funit\u002Fextensions\u002FextensionLoader.test.ts` |\n\nWhen `tests\u002Funit\u002F` exceeds 10 direct children, group into subdirectories matching source structure.\n\n---\n\n## Quick Checklist\n\n- [ ] Code is in the correct process directory (no cross-process imports)\n- [ ] Renderer code does not use Node.js APIs\n- [ ] Main process code does not use DOM APIs\n- [ ] New IPC channels are bridged through `preload.ts`\n- [ ] Renderer component\u002Fmodule dirs use PascalCase; categorical dirs use lowercase\n- [ ] Platform dirs use lowercase everywhere\n- [ ] Directory-based modules have `index.tsx` \u002F `index.ts` entry point\n- [ ] Page-private code is under `pages\u002F\u003CPageName>\u002F`, not in shared dirs\n- [ ] No single-file directories\n- [ ] No directory exceeds 10 direct children\n- [ ] New source files are auto-included in coverage — verify they are not accidentally excluded in `vitest.config.ts` → `coverage.exclude`\n- [ ] New services separate pure logic from IO\n","# Architecture Skill\n\nDetermine correct file placement and structure for an Electron multi-process project.\n\n## Detailed References\n\n- **Renderer layer** (components, hooks, utils, pages, CSS): [references\u002Frenderer.md](references\u002Frenderer.md)\n- **Main process & shared layer** (bridges, services, worker, preload): [references\u002Fprocess.md](references\u002Fprocess.md)\n- **Project root & monorepo layout** (directory structure, migration status): [references\u002Fproject-layout.md](references\u002Fproject-layout.md)\n\n---\n\n## Decision Tree — Where Does New Code Go?\n\n```\nIs it UI (React components, hooks, pages)?\n  └── YES → packages\u002Fdesktop\u002Fsrc\u002Frenderer\u002F              → see references\u002Frenderer.md\n\nIs it an IPC handler responding to renderer calls?\n  └── YES → packages\u002Fdesktop\u002Fsrc\u002Fprocess\u002Fbridge\u002F        → see references\u002Fprocess.md\n\nIs it business logic running in the main process?\n  └── YES → packages\u002Fdesktop\u002Fsrc\u002Fprocess\u002Fservices\u002F      → see references\u002Fprocess.md\n\nIs it an AI platform connection (API client, message protocol)?\n  └── YES → packages\u002Fdesktop\u002Fsrc\u002Fprocess\u002Fagent\u002F\u003Cplatform>\u002F\n\nIs it a background task that runs in a worker thread?\n  └── YES → packages\u002Fdesktop\u002Fsrc\u002Fprocess\u002Fworker\u002F\n\nIs it used by BOTH main and renderer processes?\n  └── YES → packages\u002Fdesktop\u002Fsrc\u002Fcommon\u002F\n\nIs it an HTTP\u002FWebSocket endpoint?\n  └── YES → packages\u002Fdesktop\u002Fsrc\u002Fprocess\u002Fwebserver\u002F\n\nIs it a plugin\u002Fextension resolver or loader?\n  └── YES → packages\u002Fdesktop\u002Fsrc\u002Fprocess\u002Fextensions\u002F\n\nIs it a messaging channel (Lark, DingTalk, Telegram)?\n  └── YES → packages\u002Fdesktop\u002Fsrc\u002Fprocess\u002Fchannels\u002F\n```\n\n---\n\n## Process Boundary Rules\n\n**Hard rules — violating them causes runtime crashes.**\n\n| Process                                             | Can use                                                    | Cannot use                                      |\n| --------------------------------------------------- | ---------------------------------------------------------- | ----------------------------------------------- |\n| **Main** (`packages\u002Fdesktop\u002Fsrc\u002Fprocess\u002F`)          | Node.js, Electron main APIs, `fs`, `path`, `child_process` | DOM APIs (`document`, `window`, React)          |\n| **Renderer** (`packages\u002Fdesktop\u002Fsrc\u002Frenderer\u002F`)     | DOM APIs, React, browser APIs                              | Node.js APIs (`fs`, `path`), Electron main APIs |\n| **Worker** (`packages\u002Fdesktop\u002Fsrc\u002Fprocess\u002Fworker\u002F`) | Node.js APIs                                               | DOM APIs, Electron APIs                         |\n| **Preload** (`packages\u002Fdesktop\u002Fsrc\u002Fpreload\u002F`)       | `contextBridge`, `ipcRenderer`                             | DOM manipulation, Node.js `fs`                  |\n\nCross-process communication:\n\n- Main ↔ Renderer: IPC via `packages\u002Fdesktop\u002Fsrc\u002Fpreload\u002F` + `packages\u002Fdesktop\u002Fsrc\u002Fprocess\u002Fbridge\u002F*.ts`\n- Main ↔ Worker: fork protocol via `packages\u002Fdesktop\u002Fsrc\u002Fprocess\u002Fworker\u002FWorkerProtocol.ts`\n\n```typescript\n\u002F\u002F NEVER in renderer\nimport { something } from '@process\u002Fservices\u002Ffoo'; \u002F\u002F crashes at runtime\n\n\u002F\u002F Use IPC instead\nconst result = await window.api.someMethod(); \u002F\u002F goes through preload\n```\n\n---\n\n## Naming Conventions\n\n### Directories\n\n| Scope                              | Convention | Reason                                                  |\n| ---------------------------------- | ---------- | ------------------------------------------------------- |\n| **Renderer** component\u002Fmodule dirs | PascalCase | React convention — dir name = component name            |\n| **Everything else**                | lowercase  | Node.js convention                                      |\n| **Categorical dirs** (everywhere)  | lowercase  | `components\u002F`, `hooks\u002F`, `utils\u002F`, `services\u002F`          |\n| **Platform dirs** (everywhere)     | lowercase  | `acp\u002F`, `codex\u002F`, `gemini\u002F` — cross-process consistency |\n\n> Quick test: \"Inside `packages\u002Fdesktop\u002Fsrc\u002Frenderer\u002F` AND represents a specific component\u002Ffeature (not a category)?\" → PascalCase. Otherwise → lowercase.\n\n### Files\n\n| Content                   | Convention                      | Examples                              |\n| ------------------------- | ------------------------------- | ------------------------------------- |\n| React components, classes | PascalCase                      | `SettingsModal.tsx`, `CronService.ts` |\n| Hooks                     | camelCase with `use` prefix     | `useTheme.ts`, `useCronJobs.ts`       |\n| Utilities, helpers        | camelCase                       | `formatDate.ts`, `cronUtils.ts`       |\n| Entry points              | `index.ts` \u002F `index.tsx`        | Required for directory-based modules  |\n| Config, types, constants  | camelCase                       | `types.ts`, `constants.ts`            |\n| Styles                    | kebab-case or `Name.module.css` | `chat-layout.css`                     |\n\n---\n\n## Structural Rules\n\n1. **Directory size limit**: Max **10** direct children. Split into subdirectories by responsibility when approaching.\n2. **No single-file directories**: Merge into parent or related directory.\n3. **Single file vs directory**: If a component needs a private sub-component or hook, convert to a directory with `index.tsx`.\n4. **Page-private first**: Start code in `pages\u002F\u003CPageName>\u002F`. Promote to shared only when a second consumer appears.\n\n## Test File Mapping\n\nTests mirror source files in `tests\u002F` subdirectories:\n\n| Source                                                       | Test                                            |\n| ------------------------------------------------------------ | ----------------------------------------------- |\n| `packages\u002Fdesktop\u002Fsrc\u002Fprocess\u002Fservices\u002FCronService.ts`       | `tests\u002Funit\u002FcronService.test.ts`                |\n| `packages\u002Fdesktop\u002Fsrc\u002Frenderer\u002Fhooks\u002Fui\u002FuseAutoScroll.ts`    | `tests\u002Funit\u002FuseAutoScroll.dom.test.ts`          |\n| `packages\u002Fdesktop\u002Fsrc\u002Fprocess\u002Fextensions\u002FExtensionLoader.ts` | `tests\u002Funit\u002Fextensions\u002FextensionLoader.test.ts` |\n\nWhen `tests\u002Funit\u002F` exceeds 10 direct children, group into subdirectories matching source structure.\n\n---\n\n## Quick Checklist\n\n- [ ] Code is in the correct process directory (no cross-process imports)\n- [ ] Renderer code does not use Node.js APIs\n- [ ] Main process code does not use DOM APIs\n- [ ] New IPC channels are bridged through `preload.ts`\n- [ ] Renderer component\u002Fmodule dirs use PascalCase; categorical dirs use lowercase\n- [ ] Platform dirs use lowercase everywhere\n- [ ] Directory-based modules have `index.tsx` \u002F `index.ts` entry point\n- [ ] Page-private code is under `pages\u002F\u003CPageName>\u002F`, not in shared dirs\n- [ ] No single-file directories\n- [ ] No directory exceeds 10 direct children\n- [ ] New source files are auto-included in coverage — verify they are not accidentally excluded in `vitest.config.ts` → `coverage.exclude`\n- [ ] New services separate pure logic from IO\n",{"name":5,"description":7},"team","a9a9464c62247a811d9231c636a0941e0fd9ae05",".claude\u002Fskills\u002Farchitecture","https:\u002F\u002Fgithub.com\u002Ffinewood2008\u002Fcentaurai-team","https:\u002F\u002Fgithub.com\u002Ffinewood2008","Founder & CEO of Centaur AI · Humans lead, AI executes — the Centaur Loop is the smallest work unit for building AI employees.","2026-07-14 22:41:28",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add finewood2008\u002Fcentaurai-team --skill architecture",{"tool":37,"command":38},"bunx","bunx skills add finewood2008\u002Fcentaurai-team --skill architecture",{"tool":40,"command":41},"pnpm","pnpm dlx skills add finewood2008\u002Fcentaurai-team --skill architecture","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ffinewood2008\u002Fcentaurai-team\u002Fblob\u002Fteam\u002F.claude\u002Fskills\u002Farchitecture\u002FSKILL.md",true,[45,51,55],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"references\u002Fprocess.md","REFERENCE","参考文档",4710,"https:\u002F\u002Fgithub.com\u002Ffinewood2008\u002Fcentaurai-team\u002Fblob\u002Fteam\u002F.claude\u002Fskills\u002Farchitecture\u002Freferences\u002Fprocess.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fproject-layout.md",3269,"https:\u002F\u002Fgithub.com\u002Ffinewood2008\u002Fcentaurai-team\u002Fblob\u002Fteam\u002F.claude\u002Fskills\u002Farchitecture\u002Freferences\u002Fproject-layout.md",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Frenderer.md",7394,"https:\u002F\u002Fgithub.com\u002Ffinewood2008\u002Fcentaurai-team\u002Fblob\u002Fteam\u002F.claude\u002Fskills\u002Farchitecture\u002Freferences\u002Frenderer.md",[60,68,75,82,89,96],{"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":64,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M77RFHB8MZ42KXGPY38CXCAQ","团队周报","Use when generating structured weekly team reports from git commits, task boards, and meeting notes. Auto-aggregates work done, work planned, blockers, and metrics. Chinese output by default. Trigger on: weekly report, 周报, sprint review, 本周总结, team update, status report.","MIT","https:\u002F\u002Fgithub.com\u002Ffinewood2008\u002Fcentaurai-team\u002Fblob\u002Fteam\u002Fskills\u002Fbuiltin\u002Fteam\u002Fteam-weekly-report\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":64,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M77RFBY70Q5R4YN8A3JD7X5G","中英互译","Use when translating content between Chinese and English for business, technical, or marketing purposes. Handles docs, emails, UI strings, marketing copy, and technical documentation with domain-aware terminology. Trigger on: 翻译, translate, 中译英, 英译中, i18n, localization, English version, 中文版.","https:\u002F\u002Fgithub.com\u002Ffinewood2008\u002Fcentaurai-team\u002Fblob\u002Fteam\u002Fskills\u002Fbuiltin\u002Fteam\u002Fteam-translation\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":64,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M77RF6YBVG39A4QQQEGY8Q6N","社媒规划","Use when planning, drafting, or scheduling social media content for WeChat Official Account, Twitter\u002FX, and Xiaohongshu. Generates content calendars with platform-adapted copy, publishing schedules, and performance tracking. Trigger on: social media, 公众号, 推文, content calendar, 社媒, 发布计划.","https:\u002F\u002Fgithub.com\u002Ffinewood2008\u002Fcentaurai-team\u002Fblob\u002Fteam\u002Fskills\u002Fbuiltin\u002Fteam\u002Fteam-social-planner\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":64,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M77RF2JR9BZ9QKXY101Z80F8","项目任务看板","Use when managing team projects, tasks, or sprint tracking with a lightweight markdown kanban board. Create, update, assign, and track tasks across team members without external tools. Trigger on: task board, kanban, sprint planning, assign task, task status, project progress.","https:\u002F\u002Fgithub.com\u002Ffinewood2008\u002Fcentaurai-team\u002Fblob\u002Fteam\u002Fskills\u002Fbuiltin\u002Fteam\u002Fteam-project-tracker\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":64,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M77REYK38P4W54XQVFFV0GF2","新人入职","Use when onboarding a new team member to the company, project, or development environment. Covers environment setup, account provisioning, access permissions, first-day tasks, and knowledge base orientation. Trigger on: onboarding, 入职, new employee, 新人, setup workstation, 环境配置, first day.","https:\u002F\u002Fgithub.com\u002Ffinewood2008\u002Fcentaurai-team\u002Fblob\u002Fteam\u002Fskills\u002Fbuiltin\u002Fteam\u002Fteam-onboarding\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":64,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M77RESXY98BF66BSTPZADB4W","会议纪要","Use when recording, structuring, or extracting action items from team meetings. Creates standardized meeting minutes with decisions, action items with owners and deadlines, and follow-up tracking. Trigger on: meeting notes, 会议纪要, meeting minutes, 开会记录, standup notes, decision log, 会议记录.","https:\u002F\u002Fgithub.com\u002Ffinewood2008\u002Fcentaurai-team\u002Fblob\u002Fteam\u002Fskills\u002Fbuiltin\u002Fteam\u002Fteam-meeting-minutes\u002FSKILL.md",[],[]]