[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-openai-outlook-calendar-group-scheduler":3,"mdc-5v1eo4-key":36,"related-repo-openai-outlook-calendar-group-scheduler":311,"related-org-openai-outlook-calendar-group-scheduler":435},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":25,"repoUrl":26,"updatedAt":27,"license":28,"forks":29,"topics":30,"repo":31,"sourceUrl":34,"mdContent":35},"outlook-calendar-group-scheduler","schedule group meetings with Outlook Calendar","Find and rank good meeting times for several people using Outlook Calendar data. Use when the user wants to schedule a meeting, compare candidate slots across attendees, find the best compromise time, or add a room\u002Fresource check after narrowing the attendee-compatible options.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},"openai","OpenAI","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fopenai.png",[12,16,19,22],{"name":13,"slug":14,"type":15},"Productivity","productivity","tag",{"name":17,"slug":18,"type":15},"Outlook Calendar","outlook-calendar",{"name":20,"slug":21,"type":15},"Meetings","meetings",{"name":23,"slug":24,"type":15},"Task Management","task-management",3992,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins","2026-04-06T18:42:40.873014",null,465,[],{"repoUrl":26,"stars":25,"forks":29,"topics":32,"description":33},[],"OpenAI Plugins","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins\u002Ftree\u002FHEAD\u002Fplugins\u002Foutlook-calendar\u002Fskills\u002Foutlook-calendar-group-scheduler","---\nname: outlook-calendar-group-scheduler\ndescription: Find and rank good meeting times for several people using Outlook Calendar data. Use when the user wants to schedule a meeting, compare candidate slots across attendees, find the best compromise time, or add a room\u002Fresource check after narrowing the attendee-compatible options.\n---\n\n# Outlook Calendar Group Scheduler\n\nUse this skill when the scheduling problem is the task.\n\n## Relevant Actions\n\n- Use `get_schedule` for attendee and room\u002Fresource free-busy windows once you know the concrete schedule identifiers.\n- Use `find_available_slots` when the problem is mostly about the user's own calendar and buffered openings.\n- Use `search_events` or `list_events` when you need conflict context before ranking options.\n- Use `create_event` only after the winning slot and attendee set are settled.\n\n## Outlook Product Framing\n\n- Treat free\u002Fbusy visibility, work hours, and work location as first-class scheduling evidence when full event detail is unavailable.\n- Treat attendee response state and organizer logistics as part of scheduling, not just the final event body.\n- When rooms or resources are visible, treat them as Outlook-style scheduling constraints rather than a separate \"room finder\" workflow.\n\n## Workflow\n\n1. Ground the scheduling problem first: date window, duration, timezone, required attendees, optional attendees, and any hard constraints such as \"this week\", \"afternoons only\", or \"avoid lunch\".\n2. If the scheduling window is ambiguous, assess the meeting stakes before choosing a default search window. For relatively high-stakes meetings, go back to the user and suggest tightening the timeline, for example to the next week. For lower-stakes or more casual group scheduling, default to a near-term search such as the next 1 to 3 weeks.\n3. Normalize the request into explicit candidate windows before ranking anything.\n4. Rank slots, do not enumerate everything. Optimize for a short list of strong options.\n5. Treat `Busy` and `Out of Office` as harder constraints than `Tentative` or `Working Elsewhere` unless the user says otherwise.\n6. Prefer slots that minimize conflict cost, fit within work hours, and avoid avoidable hybrid-work friction such as forcing an in-office room meeting onto remote-heavy attendees.\n7. When rooms, resources, or building context are available, prefer slots that keep the meeting logistically coherent instead of treating time as the only variable.\n8. If shared-calendar visibility is partial, say when a recommendation is based on free\u002Fbusy signals rather than full event detail.\n\n## Ranking Heuristics\n\n- Favor required-attendee fit over optional-attendee fit.\n- Favor slots that avoid very early or very late local times for distributed attendees.\n- Favor slots that stay inside work hours and avoid consuming the only large free block in someone's day unless the meeting is clearly important.\n- Favor a small number of high-confidence options over a long weak list.\n- When two slots are similar, prefer the one that causes less calendar fragmentation.\n- When one attendee is only `Tentative` or `Working Elsewhere`, describe that as a softer constraint instead of silently treating it as unavailable.\n- When one option aligns better with attendees' work locations or room logistics, explain that advantage explicitly.\n\n## Output Conventions\n\n- Return 2-4 candidate slots by default.\n- For each slot, say why it works and who, if anyone, would be inconvenienced.\n- If there is no clean option, say what tradeoff the best slot is making.\n",{"data":37,"body":38},{"name":4,"description":6},{"type":39,"children":40},"root",[41,49,55,62,125,131,149,155,230,236,287,293],{"type":42,"tag":43,"props":44,"children":45},"element","h1",{"id":4},[46],{"type":47,"value":48},"text","Outlook Calendar Group Scheduler",{"type":42,"tag":50,"props":51,"children":52},"p",{},[53],{"type":47,"value":54},"Use this skill when the scheduling problem is the task.",{"type":42,"tag":56,"props":57,"children":59},"h2",{"id":58},"relevant-actions",[60],{"type":47,"value":61},"Relevant Actions",{"type":42,"tag":63,"props":64,"children":65},"ul",{},[66,81,93,113],{"type":42,"tag":67,"props":68,"children":69},"li",{},[70,72,79],{"type":47,"value":71},"Use ",{"type":42,"tag":73,"props":74,"children":76},"code",{"className":75},[],[77],{"type":47,"value":78},"get_schedule",{"type":47,"value":80}," for attendee and room\u002Fresource free-busy windows once you know the concrete schedule identifiers.",{"type":42,"tag":67,"props":82,"children":83},{},[84,85,91],{"type":47,"value":71},{"type":42,"tag":73,"props":86,"children":88},{"className":87},[],[89],{"type":47,"value":90},"find_available_slots",{"type":47,"value":92}," when the problem is mostly about the user's own calendar and buffered openings.",{"type":42,"tag":67,"props":94,"children":95},{},[96,97,103,105,111],{"type":47,"value":71},{"type":42,"tag":73,"props":98,"children":100},{"className":99},[],[101],{"type":47,"value":102},"search_events",{"type":47,"value":104}," or ",{"type":42,"tag":73,"props":106,"children":108},{"className":107},[],[109],{"type":47,"value":110},"list_events",{"type":47,"value":112}," when you need conflict context before ranking options.",{"type":42,"tag":67,"props":114,"children":115},{},[116,117,123],{"type":47,"value":71},{"type":42,"tag":73,"props":118,"children":120},{"className":119},[],[121],{"type":47,"value":122},"create_event",{"type":47,"value":124}," only after the winning slot and attendee set are settled.",{"type":42,"tag":56,"props":126,"children":128},{"id":127},"outlook-product-framing",[129],{"type":47,"value":130},"Outlook Product Framing",{"type":42,"tag":63,"props":132,"children":133},{},[134,139,144],{"type":42,"tag":67,"props":135,"children":136},{},[137],{"type":47,"value":138},"Treat free\u002Fbusy visibility, work hours, and work location as first-class scheduling evidence when full event detail is unavailable.",{"type":42,"tag":67,"props":140,"children":141},{},[142],{"type":47,"value":143},"Treat attendee response state and organizer logistics as part of scheduling, not just the final event body.",{"type":42,"tag":67,"props":145,"children":146},{},[147],{"type":47,"value":148},"When rooms or resources are visible, treat them as Outlook-style scheduling constraints rather than a separate \"room finder\" workflow.",{"type":42,"tag":56,"props":150,"children":152},{"id":151},"workflow",[153],{"type":47,"value":154},"Workflow",{"type":42,"tag":156,"props":157,"children":158},"ol",{},[159,164,169,174,179,215,220,225],{"type":42,"tag":67,"props":160,"children":161},{},[162],{"type":47,"value":163},"Ground the scheduling problem first: date window, duration, timezone, required attendees, optional attendees, and any hard constraints such as \"this week\", \"afternoons only\", or \"avoid lunch\".",{"type":42,"tag":67,"props":165,"children":166},{},[167],{"type":47,"value":168},"If the scheduling window is ambiguous, assess the meeting stakes before choosing a default search window. For relatively high-stakes meetings, go back to the user and suggest tightening the timeline, for example to the next week. For lower-stakes or more casual group scheduling, default to a near-term search such as the next 1 to 3 weeks.",{"type":42,"tag":67,"props":170,"children":171},{},[172],{"type":47,"value":173},"Normalize the request into explicit candidate windows before ranking anything.",{"type":42,"tag":67,"props":175,"children":176},{},[177],{"type":47,"value":178},"Rank slots, do not enumerate everything. Optimize for a short list of strong options.",{"type":42,"tag":67,"props":180,"children":181},{},[182,184,190,192,198,200,206,207,213],{"type":47,"value":183},"Treat ",{"type":42,"tag":73,"props":185,"children":187},{"className":186},[],[188],{"type":47,"value":189},"Busy",{"type":47,"value":191}," and ",{"type":42,"tag":73,"props":193,"children":195},{"className":194},[],[196],{"type":47,"value":197},"Out of Office",{"type":47,"value":199}," as harder constraints than ",{"type":42,"tag":73,"props":201,"children":203},{"className":202},[],[204],{"type":47,"value":205},"Tentative",{"type":47,"value":104},{"type":42,"tag":73,"props":208,"children":210},{"className":209},[],[211],{"type":47,"value":212},"Working Elsewhere",{"type":47,"value":214}," unless the user says otherwise.",{"type":42,"tag":67,"props":216,"children":217},{},[218],{"type":47,"value":219},"Prefer slots that minimize conflict cost, fit within work hours, and avoid avoidable hybrid-work friction such as forcing an in-office room meeting onto remote-heavy attendees.",{"type":42,"tag":67,"props":221,"children":222},{},[223],{"type":47,"value":224},"When rooms, resources, or building context are available, prefer slots that keep the meeting logistically coherent instead of treating time as the only variable.",{"type":42,"tag":67,"props":226,"children":227},{},[228],{"type":47,"value":229},"If shared-calendar visibility is partial, say when a recommendation is based on free\u002Fbusy signals rather than full event detail.",{"type":42,"tag":56,"props":231,"children":233},{"id":232},"ranking-heuristics",[234],{"type":47,"value":235},"Ranking Heuristics",{"type":42,"tag":63,"props":237,"children":238},{},[239,244,249,254,259,264,282],{"type":42,"tag":67,"props":240,"children":241},{},[242],{"type":47,"value":243},"Favor required-attendee fit over optional-attendee fit.",{"type":42,"tag":67,"props":245,"children":246},{},[247],{"type":47,"value":248},"Favor slots that avoid very early or very late local times for distributed attendees.",{"type":42,"tag":67,"props":250,"children":251},{},[252],{"type":47,"value":253},"Favor slots that stay inside work hours and avoid consuming the only large free block in someone's day unless the meeting is clearly important.",{"type":42,"tag":67,"props":255,"children":256},{},[257],{"type":47,"value":258},"Favor a small number of high-confidence options over a long weak list.",{"type":42,"tag":67,"props":260,"children":261},{},[262],{"type":47,"value":263},"When two slots are similar, prefer the one that causes less calendar fragmentation.",{"type":42,"tag":67,"props":265,"children":266},{},[267,269,274,275,280],{"type":47,"value":268},"When one attendee is only ",{"type":42,"tag":73,"props":270,"children":272},{"className":271},[],[273],{"type":47,"value":205},{"type":47,"value":104},{"type":42,"tag":73,"props":276,"children":278},{"className":277},[],[279],{"type":47,"value":212},{"type":47,"value":281},", describe that as a softer constraint instead of silently treating it as unavailable.",{"type":42,"tag":67,"props":283,"children":284},{},[285],{"type":47,"value":286},"When one option aligns better with attendees' work locations or room logistics, explain that advantage explicitly.",{"type":42,"tag":56,"props":288,"children":290},{"id":289},"output-conventions",[291],{"type":47,"value":292},"Output Conventions",{"type":42,"tag":63,"props":294,"children":295},{},[296,301,306],{"type":42,"tag":67,"props":297,"children":298},{},[299],{"type":47,"value":300},"Return 2-4 candidate slots by default.",{"type":42,"tag":67,"props":302,"children":303},{},[304],{"type":47,"value":305},"For each slot, say why it works and who, if anyone, would be inconvenienced.",{"type":42,"tag":67,"props":307,"children":308},{},[309],{"type":47,"value":310},"If there is no clean option, say what tradeoff the best slot is making.",{"items":312,"total":434},[313,332,348,360,380,402,422],{"slug":314,"name":314,"fn":315,"description":316,"org":317,"tags":318,"stars":25,"repoUrl":26,"updatedAt":331},"accessibility-and-inclusive-visualization","make data visualizations accessible","Make data visualizations accessible and inclusive. Use when the user needs chart or diagram accessibility guidance, text alternatives for complex visuals, color and contrast review, keyboard support, reduced-motion behavior for animation or parallax, or an accessibility QA workflow for exported figures, UML-like diagrams, and dashboards.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[319,322,325,328],{"name":320,"slug":321,"type":15},"Accessibility","accessibility",{"name":323,"slug":324,"type":15},"Charts","charts",{"name":326,"slug":327,"type":15},"Data Visualization","data-visualization",{"name":329,"slug":330,"type":15},"Design","design","2026-06-30T19:00:57.102",{"slug":333,"name":333,"fn":334,"description":335,"org":336,"tags":337,"stars":25,"repoUrl":26,"updatedAt":347},"agent-browser","automate browser interactions for agents","Browser automation CLI for AI agents. Use when the user needs to interact with websites, verify dev server output, test web apps, navigate pages, fill forms, click buttons, take screenshots, extract data, or automate any browser task. Also triggers when a dev server starts so you can verify it visually.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[338,341,344],{"name":339,"slug":340,"type":15},"Agents","agents",{"name":342,"slug":343,"type":15},"Browser Automation","browser-automation",{"name":345,"slug":346,"type":15},"Testing","testing","2026-04-06T18:41:03.44016",{"slug":349,"name":349,"fn":350,"description":351,"org":352,"tags":353,"stars":25,"repoUrl":26,"updatedAt":359},"agent-browser-verify","verify dev server output with automated browser","Automated browser verification for dev servers. Triggers when a dev server starts to run a visual gut-check with agent-browser — verifies the page loads, checks for console errors, validates key UI elements, and reports pass\u002Ffail before continuing.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[354,355,358],{"name":342,"slug":343,"type":15},{"name":356,"slug":357,"type":15},"Local Development","local-development",{"name":345,"slug":346,"type":15},"2026-04-06T18:41:17.526867",{"slug":361,"name":361,"fn":362,"description":363,"org":364,"tags":365,"stars":25,"repoUrl":26,"updatedAt":379},"agents-sdk","build AI agents on Cloudflare Workers","Build AI agents on Cloudflare Workers using the Agents SDK. Load when creating stateful agents, durable workflows, real-time WebSocket apps, scheduled tasks, MCP servers, or chat applications. Covers Agent class, state management, callable RPC, Workflows integration, and React hooks. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[366,367,370,373,376],{"name":339,"slug":340,"type":15},{"name":368,"slug":369,"type":15},"Cloudflare Workers","cloudflare-workers",{"name":371,"slug":372,"type":15},"SDK","sdk",{"name":374,"slug":375,"type":15},"Serverless","serverless",{"name":377,"slug":378,"type":15},"WebSockets","websockets","2026-04-06T18:39:51.717063",{"slug":381,"name":381,"fn":382,"description":383,"org":384,"tags":385,"stars":25,"repoUrl":26,"updatedAt":401},"ai-elements","build chat UIs with AI Elements","AI Elements component library guidance — pre-built React components for AI interfaces built on shadcn\u002Fui. Use when building chat UIs, message displays, tool call rendering, streaming responses, reasoning panels, or any AI-native interface with the AI SDK.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[386,389,392,395,398],{"name":387,"slug":388,"type":15},"Frontend","frontend",{"name":390,"slug":391,"type":15},"React","react",{"name":393,"slug":394,"type":15},"shadcn\u002Fui","shadcn-ui",{"name":396,"slug":397,"type":15},"UI Components","ui-components",{"name":399,"slug":400,"type":15},"Vercel","vercel","2026-04-06T18:40:59.619419",{"slug":403,"name":403,"fn":404,"description":405,"org":406,"tags":407,"stars":25,"repoUrl":26,"updatedAt":421},"ai-gateway","configure Vercel AI Gateway","Vercel AI Gateway expert guidance. Use when configuring model routing, provider failover, cost tracking, or managing multiple AI providers through a unified API.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[408,411,414,417,420],{"name":409,"slug":410,"type":15},"AI Infrastructure","ai-infrastructure",{"name":412,"slug":413,"type":15},"Cost Optimization","cost-optimization",{"name":415,"slug":416,"type":15},"LLM","llm",{"name":418,"slug":419,"type":15},"Performance","performance",{"name":399,"slug":400,"type":15},"2026-04-06T18:40:44.377464",{"slug":423,"name":423,"fn":424,"description":425,"org":426,"tags":427,"stars":25,"repoUrl":26,"updatedAt":433},"ai-generation-persistence","implement persistence patterns for AI generations","AI generation persistence patterns — unique IDs, addressable URLs, database storage, and cost tracking for every LLM generation",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[428,429,432],{"name":412,"slug":413,"type":15},{"name":430,"slug":431,"type":15},"Database","database",{"name":415,"slug":416,"type":15},"2026-04-06T18:41:08.513425",600,{"items":436,"total":629},[437,458,481,498,514,531,546,558,572,586,598,613],{"slug":438,"name":438,"fn":439,"description":440,"org":441,"tags":442,"stars":455,"repoUrl":456,"updatedAt":457},"prior-auth-packet-builder","build healthcare prior authorization packets","Build a concise prior authorization packet from local case files and payer policy docs.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[443,446,449,452],{"name":444,"slug":445,"type":15},"Documents","documents",{"name":447,"slug":448,"type":15},"Healthcare","healthcare",{"name":450,"slug":451,"type":15},"Insurance","insurance",{"name":453,"slug":454,"type":15},"Regulatory Compliance","regulatory-compliance",28169,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fopenai-agents-python","2026-04-16T05:11:39.180399",{"slug":459,"name":459,"fn":460,"description":461,"org":462,"tags":463,"stars":478,"repoUrl":479,"updatedAt":480},"aspnet-core","build ASP.NET Core web applications","Build, review, refactor, or architect ASP.NET Core web applications using current official guidance for .NET web development. Use when working on Blazor Web Apps, Razor Pages, MVC, Minimal APIs, controller-based Web APIs, SignalR, gRPC, middleware, dependency injection, configuration, authentication, authorization, testing, performance, deployment, or ASP.NET Core upgrades.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[464,467,469,472,475],{"name":465,"slug":466,"type":15},".NET","dotnet",{"name":468,"slug":459,"type":15},"ASP.NET Core",{"name":470,"slug":471,"type":15},"Blazor","blazor",{"name":473,"slug":474,"type":15},"C#","csharp",{"name":476,"slug":477,"type":15},"Web Development","web-development",23787,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fskills","2026-04-12T05:07:02.819491",{"slug":482,"name":482,"fn":483,"description":484,"org":485,"tags":486,"stars":478,"repoUrl":479,"updatedAt":497},"chatgpt-apps","build ChatGPT Apps SDK applications","Build, scaffold, refactor, and troubleshoot ChatGPT Apps SDK applications that combine an MCP server and widget UI. Use when Codex needs to design tools, register UI resources, wire the MCP Apps bridge or ChatGPT compatibility APIs, apply Apps SDK metadata or CSP or domain settings, or produce a docs-aligned project scaffold. Prefer a docs-first workflow by invoking the openai-docs skill or OpenAI developer docs MCP tools before generating code.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[487,490,493,496],{"name":488,"slug":489,"type":15},"Apps SDK","apps-sdk",{"name":491,"slug":492,"type":15},"ChatGPT","chatgpt",{"name":494,"slug":495,"type":15},"MCP","mcp",{"name":9,"slug":8,"type":15},"2026-04-12T05:07:05.468097",{"slug":499,"name":499,"fn":500,"description":501,"org":502,"tags":503,"stars":478,"repoUrl":479,"updatedAt":513},"cli-creator","build CLIs from API docs","Build a composable CLI for Codex from API docs, an OpenAPI spec, existing curl examples, an SDK, a web app, an admin tool, or a local script. Use when the user wants Codex to create a command-line tool that can run from any repo, expose composable read\u002Fwrite commands, return stable JSON, manage auth, and pair with a companion skill.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[504,507,510],{"name":505,"slug":506,"type":15},"API Development","api-development",{"name":508,"slug":509,"type":15},"CLI","cli",{"name":511,"slug":512,"type":15},"Codex","codex","2026-04-12T05:07:04.132762",{"slug":515,"name":515,"fn":516,"description":517,"org":518,"tags":519,"stars":478,"repoUrl":479,"updatedAt":530},"cloudflare-deploy","deploy projects to Cloudflare","Deploy applications and infrastructure to Cloudflare using Workers, Pages, and related platform services. Use when the user asks to deploy, host, publish, or set up a project on Cloudflare.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[520,523,526,527],{"name":521,"slug":522,"type":15},"Cloudflare","cloudflare",{"name":524,"slug":525,"type":15},"Cloudflare Pages","cloudflare-pages",{"name":368,"slug":369,"type":15},{"name":528,"slug":529,"type":15},"Deployment","deployment","2026-04-12T05:07:14.275118",{"slug":532,"name":532,"fn":533,"description":534,"org":535,"tags":536,"stars":478,"repoUrl":479,"updatedAt":545},"define-goal","define and set measurable project goals","Help the user define a concrete, measurable goal before starting work, especially when they ask to use the goal tool, create a goal, set an objective, clarify success criteria, or turn a fuzzy intention into a quantitative outcome. Use this skill for goal creation and goal refinement only; it does not manage durable snapshots, decision logs, or long-running execution artifacts.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[537,538,541,544],{"name":13,"slug":14,"type":15},{"name":539,"slug":540,"type":15},"Project Management","project-management",{"name":542,"slug":543,"type":15},"Strategy","strategy",{"name":23,"slug":24,"type":15},"2026-05-23T06:17:16.870838",{"slug":547,"name":547,"fn":548,"description":549,"org":550,"tags":551,"stars":478,"repoUrl":479,"updatedAt":557},"figma","translate Figma designs into code","Use the Figma MCP server to fetch design context, screenshots, variables, and assets from Figma, and to translate Figma nodes into production code. Trigger when a task involves Figma URLs, node IDs, design-to-code implementation, or Figma MCP setup and troubleshooting.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[552,553,555,556],{"name":329,"slug":330,"type":15},{"name":554,"slug":547,"type":15},"Figma",{"name":387,"slug":388,"type":15},{"name":494,"slug":495,"type":15},"2026-04-12T05:06:47.939943",{"slug":559,"name":559,"fn":560,"description":561,"org":562,"tags":563,"stars":478,"repoUrl":479,"updatedAt":571},"figma-code-connect-components","connect Figma designs to code components","Connects Figma design components to code components using Code Connect mapping tools. Use when user says \"code connect\", \"connect this component to code\", \"map this component\", \"link component to code\", \"create code connect mapping\", or wants to establish mappings between Figma designs and code implementations. For canvas writes via `use_figma`, use `figma-use`.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[564,565,568,569,570],{"name":329,"slug":330,"type":15},{"name":566,"slug":567,"type":15},"Design System","design-system",{"name":554,"slug":547,"type":15},{"name":387,"slug":388,"type":15},{"name":396,"slug":397,"type":15},"2026-05-10T05:59:52.971881",{"slug":573,"name":573,"fn":574,"description":575,"org":576,"tags":577,"stars":478,"repoUrl":479,"updatedAt":585},"figma-create-design-system-rules","generate design system rules from Figma","Generates custom design system rules for the user's codebase. Use when user says \"create design system rules\", \"generate rules for my project\", \"set up design rules\", \"customize design system guidelines\", or wants to establish project-specific conventions for Figma-to-code workflows. Requires Figma MCP server connection.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[578,579,580,583,584],{"name":329,"slug":330,"type":15},{"name":566,"slug":567,"type":15},{"name":581,"slug":582,"type":15},"Documentation","documentation",{"name":554,"slug":547,"type":15},{"name":387,"slug":388,"type":15},"2026-05-16T06:07:47.821474",{"slug":587,"name":587,"fn":588,"description":589,"org":590,"tags":591,"stars":478,"repoUrl":479,"updatedAt":597},"figma-implement-design","translate Figma designs into application code","Translates Figma designs into production-ready application code with 1:1 visual fidelity. Use when implementing UI code from Figma files, when user mentions \"implement design\", \"generate code\", \"implement component\", provides Figma URLs, or asks to build components matching Figma specs. For Figma canvas writes via `use_figma`, use `figma-use`.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[592,593,594,595,596],{"name":329,"slug":330,"type":15},{"name":554,"slug":547,"type":15},{"name":387,"slug":388,"type":15},{"name":396,"slug":397,"type":15},{"name":476,"slug":477,"type":15},"2026-05-16T06:07:40.583615",{"slug":599,"name":599,"fn":600,"description":601,"org":602,"tags":603,"stars":478,"repoUrl":479,"updatedAt":612},"hatch-pet","create animated pets for Codex","Create, repair, validate, visually QA, and package Codex-compatible animated pets and pet spritesheets from character art, generated images, company or prospect brand cues, or visual references. Use when a user wants a lightweight-worker Codex pet workflow, a non-pixel custom pet style, a prospect or company mascot pet, or a full 8x9 animated pet atlas with transparent unused cells, QA contact sheets, and pet.json packaging. This skill composes the installed $imagegen system skill for visual generation and uses bundled scripts for deterministic spritesheet assembly.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[604,607,608,611],{"name":605,"slug":606,"type":15},"Animation","animation",{"name":511,"slug":512,"type":15},{"name":609,"slug":610,"type":15},"Creative","creative",{"name":329,"slug":330,"type":15},"2026-05-02T05:31:48.48485",{"slug":614,"name":614,"fn":615,"description":616,"org":617,"tags":618,"stars":478,"repoUrl":479,"updatedAt":628},"imagegen","generate and edit raster images","Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output should be a bitmap asset rather than repo-native code or vector. Do not use when the task is better handled by editing existing SVG\u002Fvector\u002Fcode-native assets, extending an established icon or logo system, or building the visual directly in HTML\u002FCSS\u002Fcanvas.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[619,620,621,624,627],{"name":609,"slug":610,"type":15},{"name":329,"slug":330,"type":15},{"name":622,"slug":623,"type":15},"Image Generation","image-generation",{"name":625,"slug":626,"type":15},"Images","images",{"name":9,"slug":8,"type":15},"2026-05-15T06:23:24.312127",675]