[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79P9E8JCW4R13KF2MW2EV6Z":3,"skill-same:01M79P9E8JCW4R13KF2MW2EV6Z":126},{"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":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M79P9E8JCW4R13KF2MW2EV6Z","notion-meeting-intelligence",null,"Prepare meeting materials with Notion context and Codex research; use when gathering context, drafting agendas\u002Fpre-reads, and tailoring materials to attendees.","MeghVyas3132\u002FClaude-Code-Skills","MeghVyas3132","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F213562095?v=4","01M79MBRQ3EM1GSWXK3QVWPYK6","Megh Vyas","01M79MBRQRZNC3QS0FS1KC6Z09",0,"MIT","https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002F_other-tools\u002Fcodex\u002Fnotion\u002Fnotion-meeting-intelligence\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002F_other-tools\u002Fcodex\u002Fnotion\u002Fnotion-meeting-intelligence\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: notion-meeting-intelligence\ndescription: Prepare meeting materials with Notion context and Codex 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 Codex 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 Codex 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 Codex prompts for it.\n3. Restart Codex or the current 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 Codex 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 Codex 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 Codex 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 Codex prompts for it.\n3. Restart Codex or the current 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 Codex 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","12a76cdd6f897f0872b282adeec07c7a07cf6bcc","_other-tools\u002Fcodex\u002Fnotion\u002Fnotion-meeting-intelligence","https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills","https:\u002F\u002Fgithub.com\u002FMeghVyas3132","https:\u002F\u002Fmegh.tech","Entrepreneur \u002F Platform Engineer \u002F DevOps \u002F Backend developer \u002F System Architect \u002F Salesforce admin-dev \u002F AI Engineer \u002F Junior SRE","2026-07-25 05:29:37",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add MeghVyas3132\u002FClaude-Code-Skills --skill notion-meeting-intelligence",{"tool":41,"command":42},"bunx","bunx skills add MeghVyas3132\u002FClaude-Code-Skills --skill notion-meeting-intelligence",{"tool":44,"command":45},"pnpm","pnpm dlx skills add MeghVyas3132\u002FClaude-Code-Skills --skill notion-meeting-intelligence","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002F_other-tools\u002Fcodex\u002Fnotion\u002Fnotion-meeting-intelligence\u002FSKILL.md",true,[49,55,61,65,69,73,77,81,85,89,93,98,102,106,110,114,118,122],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"agents\u002Fopenai.yaml","REFERENCE","参考文档",327,"https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002F_other-tools\u002Fcodex\u002Fnotion\u002Fnotion-meeting-intelligence\u002Fagents\u002Fopenai.yaml",{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"assets\u002Fnotion-small.svg","ASSET","资产文件",15777,"https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002F_other-tools\u002Fcodex\u002Fnotion\u002Fnotion-meeting-intelligence\u002Fassets\u002Fnotion-small.svg",{"path":62,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":63,"sourceHtmlUrl":64},"assets\u002Fnotion.png",8526,"https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002F_other-tools\u002Fcodex\u002Fnotion\u002Fnotion-meeting-intelligence\u002Fassets\u002Fnotion.png",{"path":66,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":67,"sourceHtmlUrl":68},"evaluations\u002Fdecision-meeting-prep.json",3412,"https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002F_other-tools\u002Fcodex\u002Fnotion\u002Fnotion-meeting-intelligence\u002Fevaluations\u002Fdecision-meeting-prep.json",{"path":70,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":71,"sourceHtmlUrl":72},"evaluations\u002FREADME.md",3967,"https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002F_other-tools\u002Fcodex\u002Fnotion\u002Fnotion-meeting-intelligence\u002Fevaluations\u002FREADME.md",{"path":74,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":75,"sourceHtmlUrl":76},"evaluations\u002Fstatus-meeting-prep.json",3276,"https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002F_other-tools\u002Fcodex\u002Fnotion\u002Fnotion-meeting-intelligence\u002Fevaluations\u002Fstatus-meeting-prep.json",{"path":78,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":79,"sourceHtmlUrl":80},"examples\u002Fcustomer-meeting.md",3313,"https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002F_other-tools\u002Fcodex\u002Fnotion\u002Fnotion-meeting-intelligence\u002Fexamples\u002Fcustomer-meeting.md",{"path":82,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":83,"sourceHtmlUrl":84},"examples\u002Fexecutive-review.md",2473,"https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002F_other-tools\u002Fcodex\u002Fnotion\u002Fnotion-meeting-intelligence\u002Fexamples\u002Fexecutive-review.md",{"path":86,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":87,"sourceHtmlUrl":88},"examples\u002Fproject-decision.md",12783,"https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002F_other-tools\u002Fcodex\u002Fnotion\u002Fnotion-meeting-intelligence\u002Fexamples\u002Fproject-decision.md",{"path":90,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":91,"sourceHtmlUrl":92},"examples\u002Fsprint-planning.md",2550,"https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002F_other-tools\u002Fcodex\u002Fnotion\u002Fnotion-meeting-intelligence\u002Fexamples\u002Fsprint-planning.md",{"path":94,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":97,"sourceHtmlUrl":16},"LICENSE.txt","LICENSE","许可证",1057,{"path":99,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":100,"sourceHtmlUrl":101},"reference\u002Fbrainstorming-template.md",1479,"https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002F_other-tools\u002Fcodex\u002Fnotion\u002Fnotion-meeting-intelligence\u002Freference\u002Fbrainstorming-template.md",{"path":103,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":104,"sourceHtmlUrl":105},"reference\u002Fdecision-meeting-template.md",1824,"https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002F_other-tools\u002Fcodex\u002Fnotion\u002Fnotion-meeting-intelligence\u002Freference\u002Fdecision-meeting-template.md",{"path":107,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":108,"sourceHtmlUrl":109},"reference\u002Fone-on-one-template.md",931,"https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002F_other-tools\u002Fcodex\u002Fnotion\u002Fnotion-meeting-intelligence\u002Freference\u002Fone-on-one-template.md",{"path":111,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":112,"sourceHtmlUrl":113},"reference\u002Fretrospective-template.md",939,"https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002F_other-tools\u002Fcodex\u002Fnotion\u002Fnotion-meeting-intelligence\u002Freference\u002Fretrospective-template.md",{"path":115,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":116,"sourceHtmlUrl":117},"reference\u002Fsprint-planning-template.md",1300,"https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002F_other-tools\u002Fcodex\u002Fnotion\u002Fnotion-meeting-intelligence\u002Freference\u002Fsprint-planning-template.md",{"path":119,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":120,"sourceHtmlUrl":121},"reference\u002Fstatus-update-template.md",1355,"https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002F_other-tools\u002Fcodex\u002Fnotion\u002Fnotion-meeting-intelligence\u002Freference\u002Fstatus-update-template.md",{"path":123,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":124,"sourceHtmlUrl":125},"reference\u002Ftemplate-selection-guide.md",1947,"https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002F_other-tools\u002Fcodex\u002Fnotion\u002Fnotion-meeting-intelligence\u002Freference\u002Ftemplate-selection-guide.md",[127,136,143,150,157,164],{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":131,"licenseFileUrl":132,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":20},"01M79QXVKBA07BMENY2S4C9B0D","skill-creator","Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":142,"publishedAt":20},"01M79QXPTA7529Z7QX9TYC9X8M","skill-audit","Pre-install security scanner for AI agent skills. 7.5% of 14,706 skills are malicious. Audit before you trust.","https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002Fskill-audit\u002FSKILL.md",[],[],{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":149,"publishedAt":20},"01M79QWZ2BB5GTX3PCHEEDG3A2","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002Freact-best-practices\u002FSKILL.md",[],[],{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":131,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":156,"publishedAt":20},"01M79QWAADBR52R570H6N25F47","impeccable","Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.","https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002Fimpeccable\u002FSKILL.md",[],[],{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":163,"publishedAt":20},"01M79QTGQJGPXPJDB09WBZHRND","vercel-composition-patterns","React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.","https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002Fcomposition-patterns\u002FSKILL.md",[],[],{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":170,"publishedAt":20},"01M79QT5TCZBBKP5ECWE0QD9PT","bumblebee","Run Bumblebee supply-chain inventory and exposure scans on macOS\u002FLinux to detect compromised packages, extensions, and MCP host configs.","https:\u002F\u002Fgithub.com\u002FMeghVyas3132\u002FClaude-Code-Skills\u002Fblob\u002Fmain\u002Fbumblebee\u002FSKILL.md",[],[]]