[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ED3YVQ6TPJB7ZETNSQWA4D":3,"skill-same:01M7ED3YVQ6TPJB7ZETNSQWA4D":128},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M7ED3YVQ6TPJB7ZETNSQWA4D","notion-meeting-intelligence",null,"Prepare meeting materials with Notion context and supplemental research; use when gathering context, drafting agendas\u002Fpre-reads, and tailoring materials to attendees.","kael-odin\u002Fcodex-plugins-zh","kael-odin","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F166499071?v=4","01M7EBHJT87XN88WT3PEQ8ZGZK","Kael Odin","01M7EBHJVC91GD7PGJN3ZB14SG",37,"MIT","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fnotion\u002Fskills\u002Fnotion-meeting-intelligence\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fnotion\u002Fskills\u002Fnotion-meeting-intelligence\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: notion-meeting-intelligence\ndescription: Prepare meeting materials with Notion context and supplemental research; use when gathering context, drafting agendas\u002Fpre-reads, and tailoring materials to attendees.\nmetadata:\n  short-description: Prep meetings with Notion context and tailored agendas\n---\n\n# Meeting Intelligence\n\nPrep meetings by pulling Notion context, tailoring agendas\u002Fpre-reads, and enriching with supplemental research.\n\n## Quick start\n1) Confirm meeting goal, attendees, date\u002Ftime, and decisions needed.\n2) Gather context: search with `Notion:search`, then fetch with `Notion:fetch` (prior notes, specs, OKRs, decisions).\n3) Pick the right template via `reference\u002Ftemplate-selection-guide.md` (status, decision, planning, retro, 1:1, brainstorming).\n4) Draft agenda\u002Fpre-read in Notion with `Notion:notion-create-pages`, embedding source links and owner\u002Ftimeboxes.\n5) Enrich with supplemental research (industry insights, benchmarks, risks) and update the page with `Notion:notion-update-page` as plans change.\n\n## Tool-call guardrails\n- Notion tool availability can vary by workspace. If a Notion MCP call returns `Tool \u003Cname> not found`, treat that tool as unavailable for the rest of the current task. Do not retry it with different arguments or call it again later; use `Notion:search` and `Notion:fetch` where sufficient.\n- Use one literal search query per `Notion:search` call and include `filters: {}` when no narrower filter is needed.\n- Only fetch Notion page, database, or data-source URLs\u002FIDs; external connected-source search results are not valid `Notion:fetch` inputs.\n- Create meeting pages with an explicit `parent` and a `pages` array.\n- Query databases with `Notion:notion-query-data-sources` under a top-level `data` object, using fetched `collection:\u002F\u002F...` URLs as table names.\n- When editing a page, fetch its current content first and use `Notion:notion-update-page` with supported commands such as `update_content` or `update_properties`; on the current deployed surface, use `properties: {}` for `update_content` and `content_updates: []` for `update_properties`. Do not invent insertion-only commands.\n\n## Workflow\n### 0) If Notion tools are unavailable, pause and ask the user to connect the Notion app:\n1. Enable the bundled Notion app for this plugin or session.\n2. Complete the Notion auth flow if prompted.\n3. Start a new session if the tools still do not appear.\n\nAfter the app is connected, finish your answer and tell the user to retry so they can continue with Step 1.\n\n### 1) Gather inputs\n- Ask for objective, desired outcomes\u002Fdecisions, attendees, duration, date\u002Ftime, and prior materials.\n- Search Notion for relevant docs, past notes, specs, and action items (`Notion:search`), then fetch key pages (`Notion:fetch`).\n- Capture blockers\u002Frisks and open questions up front.\n\n### 2) Choose format\n- Status\u002Fupdate → status template.\n- Decision\u002Fapproval → decision template.\n- Planning (sprint\u002Fproject) → planning template.\n- Retro\u002Ffeedback → retrospective template.\n- 1:1 → one-on-one template.\n- Ideation → brainstorming template.\n- Use `reference\u002Ftemplate-selection-guide.md` to confirm.\n\n### 3) Build the agenda\u002Fpre-read\n- Start from the chosen template in `reference\u002F` and adapt sections (context, goals, agenda, owner\u002Ftime per item, decisions, risks, prep asks).\n- Include links to pulled Notion pages and any required pre-reading.\n- Assign owners for each agenda item; call out timeboxes and expected outputs.\n\n### 4) Enrich with research\n- Add concise supplemental research where helpful: market\u002Findustry facts, benchmarks, risks, best practices.\n- Keep claims cited with source links; separate fact from opinion.\n\n### 5) Finalize and share\n- Add next steps and owners for follow-ups.\n- If tasks arise, create\u002Flink tasks in the relevant Notion database.\n- Update the page via `Notion:notion-update-page` when details change; keep a brief changelog if multiple edits.\n\n## References and examples\n- `reference\u002F` — template picker and meeting templates (e.g., `template-selection-guide.md`, `status-update-template.md`, `decision-meeting-template.md`, `sprint-planning-template.md`, `one-on-one-template.md`, `retrospective-template.md`, `brainstorming-template.md`).\n- `examples\u002F` — end-to-end meeting preps (e.g., `executive-review.md`, `project-decision.md`, `sprint-planning.md`, `customer-meeting.md`).\n","# Meeting Intelligence\n\nPrep meetings by pulling Notion context, tailoring agendas\u002Fpre-reads, and enriching with supplemental research.\n\n## Quick start\n1) Confirm meeting goal, attendees, date\u002Ftime, and decisions needed.\n2) Gather context: search with `Notion:search`, then fetch with `Notion:fetch` (prior notes, specs, OKRs, decisions).\n3) Pick the right template via `reference\u002Ftemplate-selection-guide.md` (status, decision, planning, retro, 1:1, brainstorming).\n4) Draft agenda\u002Fpre-read in Notion with `Notion:notion-create-pages`, embedding source links and owner\u002Ftimeboxes.\n5) Enrich with supplemental research (industry insights, benchmarks, risks) and update the page with `Notion:notion-update-page` as plans change.\n\n## Tool-call guardrails\n- Notion tool availability can vary by workspace. If a Notion MCP call returns `Tool \u003Cname> not found`, treat that tool as unavailable for the rest of the current task. Do not retry it with different arguments or call it again later; use `Notion:search` and `Notion:fetch` where sufficient.\n- Use one literal search query per `Notion:search` call and include `filters: {}` when no narrower filter is needed.\n- Only fetch Notion page, database, or data-source URLs\u002FIDs; external connected-source search results are not valid `Notion:fetch` inputs.\n- Create meeting pages with an explicit `parent` and a `pages` array.\n- Query databases with `Notion:notion-query-data-sources` under a top-level `data` object, using fetched `collection:\u002F\u002F...` URLs as table names.\n- When editing a page, fetch its current content first and use `Notion:notion-update-page` with supported commands such as `update_content` or `update_properties`; on the current deployed surface, use `properties: {}` for `update_content` and `content_updates: []` for `update_properties`. Do not invent insertion-only commands.\n\n## Workflow\n### 0) If Notion tools are unavailable, pause and ask the user to connect the Notion app:\n1. Enable the bundled Notion app for this plugin or session.\n2. Complete the Notion auth flow if prompted.\n3. Start a new session if the tools still do not appear.\n\nAfter the app is connected, finish your answer and tell the user to retry so they can continue with Step 1.\n\n### 1) Gather inputs\n- Ask for objective, desired outcomes\u002Fdecisions, attendees, duration, date\u002Ftime, and prior materials.\n- Search Notion for relevant docs, past notes, specs, and action items (`Notion:search`), then fetch key pages (`Notion:fetch`).\n- Capture blockers\u002Frisks and open questions up front.\n\n### 2) Choose format\n- Status\u002Fupdate → status template.\n- Decision\u002Fapproval → decision template.\n- Planning (sprint\u002Fproject) → planning template.\n- Retro\u002Ffeedback → retrospective template.\n- 1:1 → one-on-one template.\n- Ideation → brainstorming template.\n- Use `reference\u002Ftemplate-selection-guide.md` to confirm.\n\n### 3) Build the agenda\u002Fpre-read\n- Start from the chosen template in `reference\u002F` and adapt sections (context, goals, agenda, owner\u002Ftime per item, decisions, risks, prep asks).\n- Include links to pulled Notion pages and any required pre-reading.\n- Assign owners for each agenda item; call out timeboxes and expected outputs.\n\n### 4) Enrich with research\n- Add concise supplemental research where helpful: market\u002Findustry facts, benchmarks, risks, best practices.\n- Keep claims cited with source links; separate fact from opinion.\n\n### 5) Finalize and share\n- Add next steps and owners for follow-ups.\n- If tasks arise, create\u002Flink tasks in the relevant Notion database.\n- Update the page via `Notion:notion-update-page` when details change; keep a brief changelog if multiple edits.\n\n## References and examples\n- `reference\u002F` — template picker and meeting templates (e.g., `template-selection-guide.md`, `status-update-template.md`, `decision-meeting-template.md`, `sprint-planning-template.md`, `one-on-one-template.md`, `retrospective-template.md`, `brainstorming-template.md`).\n- `examples\u002F` — end-to-end meeting preps (e.g., `executive-review.md`, `project-decision.md`, `sprint-planning.md`, `customer-meeting.md`).\n",{"name":5,"metadata":25,"description":7},{"short-description":26},"Prep meetings with Notion context and tailored agendas","main","e3091d1b371a9dcd9455d333175f948b286fdfcf","plugins\u002Fnotion\u002Fskills\u002Fnotion-meeting-intelligence",1,"https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh","https:\u002F\u002Fkael-odin.github.io\u002Fcodex-plugins-zh\u002F","https:\u002F\u002Fgithub.com\u002Fkael-odin","https:\u002F\u002Fkael-odin.github.io\u002Fodin-valhalla\u002F","Full-stack development • Open-source • System engineering\r\nTurning ideas into repositories.","2026-11-08 17:05:36",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add kael-odin\u002Fcodex-plugins-zh --skill notion-meeting-intelligence",{"tool":43,"command":44},"bunx","bunx skills add kael-odin\u002Fcodex-plugins-zh --skill notion-meeting-intelligence",{"tool":46,"command":47},"pnpm","pnpm dlx skills add kael-odin\u002Fcodex-plugins-zh --skill notion-meeting-intelligence","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fnotion\u002Fskills\u002Fnotion-meeting-intelligence\u002FSKILL.md",true,[51,57,63,67,71,75,79,83,87,91,95,100,104,108,112,116,120,124],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"agents\u002Fopenai.yaml","REFERENCE","参考文档",327,"https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fnotion\u002Fskills\u002Fnotion-meeting-intelligence\u002Fagents\u002Fopenai.yaml",{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"assets\u002Fnotion-small.svg","ASSET","资产文件",1561,"https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fnotion\u002Fskills\u002Fnotion-meeting-intelligence\u002Fassets\u002Fnotion-small.svg",{"path":64,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":65,"sourceHtmlUrl":66},"assets\u002Fnotion.png",8526,"https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fnotion\u002Fskills\u002Fnotion-meeting-intelligence\u002Fassets\u002Fnotion.png",{"path":68,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":69,"sourceHtmlUrl":70},"evaluations\u002Fdecision-meeting-prep.json",3454,"https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fnotion\u002Fskills\u002Fnotion-meeting-intelligence\u002Fevaluations\u002Fdecision-meeting-prep.json",{"path":72,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":73,"sourceHtmlUrl":74},"evaluations\u002FREADME.md",4052,"https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fnotion\u002Fskills\u002Fnotion-meeting-intelligence\u002Fevaluations\u002FREADME.md",{"path":76,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":77,"sourceHtmlUrl":78},"evaluations\u002Fstatus-meeting-prep.json",3304,"https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fnotion\u002Fskills\u002Fnotion-meeting-intelligence\u002Fevaluations\u002Fstatus-meeting-prep.json",{"path":80,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":81,"sourceHtmlUrl":82},"examples\u002Fcustomer-meeting.md",3320,"https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fnotion\u002Fskills\u002Fnotion-meeting-intelligence\u002Fexamples\u002Fcustomer-meeting.md",{"path":84,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":85,"sourceHtmlUrl":86},"examples\u002Fexecutive-review.md",2480,"https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fnotion\u002Fskills\u002Fnotion-meeting-intelligence\u002Fexamples\u002Fexecutive-review.md",{"path":88,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":89,"sourceHtmlUrl":90},"examples\u002Fproject-decision.md",12783,"https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fnotion\u002Fskills\u002Fnotion-meeting-intelligence\u002Fexamples\u002Fproject-decision.md",{"path":92,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":93,"sourceHtmlUrl":94},"examples\u002Fsprint-planning.md",2550,"https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fnotion\u002Fskills\u002Fnotion-meeting-intelligence\u002Fexamples\u002Fsprint-planning.md",{"path":96,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":99,"sourceHtmlUrl":16},"LICENSE.txt","LICENSE","许可证",1057,{"path":101,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":102,"sourceHtmlUrl":103},"reference\u002Fbrainstorming-template.md",1479,"https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fnotion\u002Fskills\u002Fnotion-meeting-intelligence\u002Freference\u002Fbrainstorming-template.md",{"path":105,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":106,"sourceHtmlUrl":107},"reference\u002Fdecision-meeting-template.md",1824,"https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fnotion\u002Fskills\u002Fnotion-meeting-intelligence\u002Freference\u002Fdecision-meeting-template.md",{"path":109,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":110,"sourceHtmlUrl":111},"reference\u002Fone-on-one-template.md",931,"https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fnotion\u002Fskills\u002Fnotion-meeting-intelligence\u002Freference\u002Fone-on-one-template.md",{"path":113,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":114,"sourceHtmlUrl":115},"reference\u002Fretrospective-template.md",939,"https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fnotion\u002Fskills\u002Fnotion-meeting-intelligence\u002Freference\u002Fretrospective-template.md",{"path":117,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":118,"sourceHtmlUrl":119},"reference\u002Fsprint-planning-template.md",1300,"https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fnotion\u002Fskills\u002Fnotion-meeting-intelligence\u002Freference\u002Fsprint-planning-template.md",{"path":121,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":122,"sourceHtmlUrl":123},"reference\u002Fstatus-update-template.md",1355,"https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fnotion\u002Fskills\u002Fnotion-meeting-intelligence\u002Freference\u002Fstatus-update-template.md",{"path":125,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":126,"sourceHtmlUrl":127},"reference\u002Ftemplate-selection-guide.md",1954,"https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fnotion\u002Fskills\u002Fnotion-meeting-intelligence\u002Freference\u002Ftemplate-selection-guide.md",[129,138,145,153,160,167],{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":133,"licenseFileUrl":134,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":20},"01M7EDVCKB89EF755PQMKV1BZA","android-emulator-qa","Use when validating Android feature flows in an emulator with adb-driven launch, input, UI-tree inspection, screenshots, and logcat capture.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Ftest-android-apps\u002Fskills\u002Fandroid-emulator-qa\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Ftest-android-apps\u002Fskills\u002Fandroid-emulator-qa\u002FSKILL.md",[],[],{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":20},"01M7EDPX7WHN6HQZ0QKWB0BGVZ","supabase-postgres-best-practices","Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fsupabase\u002Fskills\u002Fsupabase-postgres-best-practices\u002FSKILL.md",[],[],{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":133,"licenseFileUrl":149,"sourceHtmlUrl":150,"categories":151,"keywords":152,"publishedAt":20},"01M7EDHHD98T8ZH09F40Q973G3","sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fsentry\u002Fskills\u002Fsentry\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fsentry\u002Fskills\u002Fsentry\u002FSKILL.md",[],[],{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":159,"publishedAt":20},"01M7EDH3SGVMS1AFS6Q40B5J48","render-workflows","搭建、开发、测试和部署 Render Workflows。涵盖首次脚手架搭建（通过 CLI 或手动方式）、SDK 安装（Python 或 TypeScript）、任务模式（重试、子任务、扇出）、本地开发、控制台部署和故障排查。适用于用户首次搭建 Render Workflows、构建工作流服务、添加或修改工作流任务、本地测试工作流或部署到 Render 的场景。","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Frender\u002Fskills\u002Frender-workflows\u002FSKILL.md",[],[],{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":166,"publishedAt":20},"01M7EDH0CYEKQ4VVARHZAQ43S8","render-web-services","配置 Render web service——端口绑定、TLS、健康检查、自定义域名、自动部署、PR 预览、持久化磁盘及部署生命周期。当用户需要搭建 web service、修复健康检查失败、添加自定义域名、配置零停机部署，或排查端口绑定问题时使用。","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Frender\u002Fskills\u002Frender-web-services\u002FSKILL.md",[],[],{"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":6,"sourceHtmlUrl":171,"categories":172,"keywords":173,"publishedAt":20},"01M7EDGVDYFBG1CKSNMQ2DD336","render-static-sites","在 Render 全球 CDN 上部署并配置静态站点——构建命令、发布路径、SPA 路由、重定向、自定义 header 及 PR 预览。当用户需要部署静态站点、搭建 React\u002FVue\u002FHugo\u002FGatsby 前端、配置 SPA 回退路由、添加重定向规则、自定义响应 header，或在静态站点与 web service 之间为前端做选择时使用。触发词:static site、CDN、SPA、single-page app、React deploy、Vue deploy、Hugo、Gatsby、Docusaurus、Jekyll、staticPublishPath。","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Frender\u002Fskills\u002Frender-static-sites\u002FSKILL.md",[],[]]