[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-openai-google-calendar":3,"mdc--eylq8c-key":35,"related-org-openai-google-calendar":441,"related-repo-openai-google-calendar":644},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":24,"repoUrl":25,"updatedAt":26,"license":27,"forks":28,"topics":29,"repo":30,"sourceUrl":33,"mdContent":34},"google-calendar","manage scheduling in Google Calendar","Manage scheduling and conflicts in connected Google Calendar data. Use when the user wants to inspect calendars, compare availability, review conflicts, find a meeting room, review event notes or attachments, add or adjust reminders, place temporary holds, or draft exact create, update, reschedule, or cancel changes with timezone-aware details.",{"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,18,21],{"name":13,"slug":14,"type":15},"Productivity","productivity","tag",{"name":17,"slug":4,"type":15},"Google Calendar",{"name":19,"slug":20,"type":15},"Meetings","meetings",{"name":22,"slug":23,"type":15},"Task Management","task-management",3992,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins","2026-04-06T18:42:49.822876",null,465,[],{"repoUrl":25,"stars":24,"forks":28,"topics":31,"description":32},[],"OpenAI Plugins","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins\u002Ftree\u002FHEAD\u002Fplugins\u002Fgoogle-calendar\u002Fskills\u002Fgoogle-calendar","---\nname: google-calendar\ndescription: Manage scheduling and conflicts in connected Google Calendar data. Use when the user wants to inspect calendars, compare availability, review conflicts, find a meeting room, review event notes or attachments, add or adjust reminders, place temporary holds, or draft exact create, update, reschedule, or cancel changes with timezone-aware details.\n---\n\n# Google Calendar\n\n## Overview\n\nUse this skill to turn raw calendar data into clear scheduling decisions, reminder plans, and safe event updates. Keep answers grounded in exact dates, times, and calendar evidence.\n\n## Preferred Deliverables\n\n- Availability summaries with exact candidate slots, timezone, and conflicts.\n- Room or resource recommendations grounded in actual calendar availability or prior meeting patterns.\n- Event change proposals that show the current event and the intended update.\n- Reminder change proposals with exact lead time, scope, and the meetings that qualify.\n- Temporary hold proposals or final hold details with the exact slot and whether the hold is transparent.\n- Final event details that are ready to create or confirm.\n\n## Workflow\n\n1. Read the relevant calendar state first so the request is grounded in actual events, calendars, and time windows.\n2. Normalize relative time language into explicit dates, times, and timezone-aware ranges before reasoning about availability.\n3. Keep reads bounded. Use explicit `time_min` and `time_max` whenever possible, avoid unbounded broad searches, and choose a small default window when the user does not state one.\n4. When a bounded search returns too much, page within that same window before widening the date range. For longer historical, precedent, or preference discovery, chunk the search into smaller windows instead of one giant pull.\n5. When the user leaves something ambiguous, inspect previous calendar data for a clear precedent before choosing a default. Follow established patterns when they are obvious, such as using the user's usual meeting duration if similar events are consistently 30 minutes.\n6. When a participant, attendee list, manager, room, or contact detail is referenced indirectly, search a bounded relevant window and read the likely source event before asking the user for details. Use `read_event` or `search_events_all_fields` when attendee emails or full event metadata matter; the standard `search_events` summary is not enough for contact details.\n7. If a found event belongs to a recurring series and the user wants a series-level change, read the master series or recurrence details before editing. Do not infer the cadence or scope from a single occurrence when `recurring_event_id` or equivalent series evidence is available.\n8. Use the connector's `update_event` action for recurring edits and set `update_scope` to `this_instance`, `entire_series`, or `this_and_following` as needed. If the series is COUNT-based and the tool requires an explicit recurrence for a future-only split, preserve and restate the recurrence rule or explain that the connector cannot safely infer the split from one occurrence.\n9. For room-finding requests, do not assume there is a reliable global room search. In this V1 flow, mine a reasonable window of past meetings, locations, and resource attendees to build a candidate room list, then compare availability on that concrete set.\n10. For bulk reminder or classification-based edit requests, inspect a reasonable upcoming window first instead of asking for extra scoping immediately. If the prompt does not bound the horizon, use a narrow default such as the next 30 days and say so.\n11. When notes, prep context, or missing details matter, inspect the event payload before proposing a change.\n12. For free-slot and temporary-hold requests, if the prompt already gives the window and duration, search within that range and move directly to proposing or placing the hold. Prefer a transparent hold for temporary placeholders unless the user clearly wants a blocking focus block.\n13. Surface conflicts, transparent holds, and missing meeting details before suggesting a write.\n14. If the request is still ambiguous after checking for precedent or scanning a reasonable bounded window, summarize the candidate slots or exact diff before writing anything.\n\n## Write Safety\n\n- Preserve source event details unless the user asked to change them.\n- When changing reminders, preserve title, attendees, location, meeting link, and notes unless the user asked to change them.\n- For Google Calendar reminder writes, prefer the structured `reminders` object rather than free-form reminder text. Use `use_default` plus explicit `overrides` with `method` and `minutes` when the user wants custom reminder timing.\n- Treat deletes and broad availability changes as high-impact actions.\n- For bulk reminder or hold writes, restate the qualifying event set and time window before applying them.\n- If multiple calendars or similarly named events are in play, identify the intended one explicitly before editing.\n- Treat missing title, attendees, location, meeting link, or timezone as confirmation points rather than assumptions only after checking whether the missing detail is recoverable from a bounded calendar search or the relevant source event.\n\n## Output Conventions\n\n- Present scheduling summaries with exact weekday, date, time, and timezone.\n- When sharing availability, say why a slot works or conflicts instead of listing raw times without context.\n- When suggesting a room or resource, name the likely room and why it is a fit, such as prior usage, matching location, or open busy windows.\n- When reporting reminder changes, name which meetings qualify, the exact lead time, and whether the scope is one event, future events, or a bounded meeting set.\n- When proposing or placing a temporary hold, say whether it is transparent or busy and why that choice fits the user's request.\n- When comparing options, keep the list short and explain the tradeoff for each slot.\n- When the user asks for meeting notes or prep context, mention whether the answer came from the event description, an attachment, or both.\n\n## Example Requests\n\n- \"Check my availability with Priya this Thursday afternoon and suggest the best two meeting slots.\"\n- \"Find a 1-hour slot next week where I'm free and place a temporary hold on it.\"\n- \"Find a room for the weekly team sync next Tuesday by checking rooms we've used before and which ones are free.\"\n- \"Move the design review to next week and keep the same attendees and Zoom link.\"\n- \"Add 1-hour reminders to my external-facing meetings next month and leave internal meetings unchanged.\"\n- \"Summarize my calendar for tomorrow and flag anything that overlaps or leaves no travel time.\"\n- \"Draft the final event details for a 30 minute customer sync at 2 PM Pacific on Friday.\"\n",{"data":36,"body":37},{"name":4,"description":6},{"type":38,"children":39},"root",[40,47,54,60,66,101,107,270,276,353,359,397,403],{"type":41,"tag":42,"props":43,"children":44},"element","h1",{"id":4},[45],{"type":46,"value":17},"text",{"type":41,"tag":48,"props":49,"children":51},"h2",{"id":50},"overview",[52],{"type":46,"value":53},"Overview",{"type":41,"tag":55,"props":56,"children":57},"p",{},[58],{"type":46,"value":59},"Use this skill to turn raw calendar data into clear scheduling decisions, reminder plans, and safe event updates. Keep answers grounded in exact dates, times, and calendar evidence.",{"type":41,"tag":48,"props":61,"children":63},{"id":62},"preferred-deliverables",[64],{"type":46,"value":65},"Preferred Deliverables",{"type":41,"tag":67,"props":68,"children":69},"ul",{},[70,76,81,86,91,96],{"type":41,"tag":71,"props":72,"children":73},"li",{},[74],{"type":46,"value":75},"Availability summaries with exact candidate slots, timezone, and conflicts.",{"type":41,"tag":71,"props":77,"children":78},{},[79],{"type":46,"value":80},"Room or resource recommendations grounded in actual calendar availability or prior meeting patterns.",{"type":41,"tag":71,"props":82,"children":83},{},[84],{"type":46,"value":85},"Event change proposals that show the current event and the intended update.",{"type":41,"tag":71,"props":87,"children":88},{},[89],{"type":46,"value":90},"Reminder change proposals with exact lead time, scope, and the meetings that qualify.",{"type":41,"tag":71,"props":92,"children":93},{},[94],{"type":46,"value":95},"Temporary hold proposals or final hold details with the exact slot and whether the hold is transparent.",{"type":41,"tag":71,"props":97,"children":98},{},[99],{"type":46,"value":100},"Final event details that are ready to create or confirm.",{"type":41,"tag":48,"props":102,"children":104},{"id":103},"workflow",[105],{"type":46,"value":106},"Workflow",{"type":41,"tag":108,"props":109,"children":110},"ol",{},[111,116,121,143,148,153,182,195,240,245,250,255,260,265],{"type":41,"tag":71,"props":112,"children":113},{},[114],{"type":46,"value":115},"Read the relevant calendar state first so the request is grounded in actual events, calendars, and time windows.",{"type":41,"tag":71,"props":117,"children":118},{},[119],{"type":46,"value":120},"Normalize relative time language into explicit dates, times, and timezone-aware ranges before reasoning about availability.",{"type":41,"tag":71,"props":122,"children":123},{},[124,126,133,135,141],{"type":46,"value":125},"Keep reads bounded. Use explicit ",{"type":41,"tag":127,"props":128,"children":130},"code",{"className":129},[],[131],{"type":46,"value":132},"time_min",{"type":46,"value":134}," and ",{"type":41,"tag":127,"props":136,"children":138},{"className":137},[],[139],{"type":46,"value":140},"time_max",{"type":46,"value":142}," whenever possible, avoid unbounded broad searches, and choose a small default window when the user does not state one.",{"type":41,"tag":71,"props":144,"children":145},{},[146],{"type":46,"value":147},"When a bounded search returns too much, page within that same window before widening the date range. For longer historical, precedent, or preference discovery, chunk the search into smaller windows instead of one giant pull.",{"type":41,"tag":71,"props":149,"children":150},{},[151],{"type":46,"value":152},"When the user leaves something ambiguous, inspect previous calendar data for a clear precedent before choosing a default. Follow established patterns when they are obvious, such as using the user's usual meeting duration if similar events are consistently 30 minutes.",{"type":41,"tag":71,"props":154,"children":155},{},[156,158,164,166,172,174,180],{"type":46,"value":157},"When a participant, attendee list, manager, room, or contact detail is referenced indirectly, search a bounded relevant window and read the likely source event before asking the user for details. Use ",{"type":41,"tag":127,"props":159,"children":161},{"className":160},[],[162],{"type":46,"value":163},"read_event",{"type":46,"value":165}," or ",{"type":41,"tag":127,"props":167,"children":169},{"className":168},[],[170],{"type":46,"value":171},"search_events_all_fields",{"type":46,"value":173}," when attendee emails or full event metadata matter; the standard ",{"type":41,"tag":127,"props":175,"children":177},{"className":176},[],[178],{"type":46,"value":179},"search_events",{"type":46,"value":181}," summary is not enough for contact details.",{"type":41,"tag":71,"props":183,"children":184},{},[185,187,193],{"type":46,"value":186},"If a found event belongs to a recurring series and the user wants a series-level change, read the master series or recurrence details before editing. Do not infer the cadence or scope from a single occurrence when ",{"type":41,"tag":127,"props":188,"children":190},{"className":189},[],[191],{"type":46,"value":192},"recurring_event_id",{"type":46,"value":194}," or equivalent series evidence is available.",{"type":41,"tag":71,"props":196,"children":197},{},[198,200,206,208,214,216,222,224,230,232,238],{"type":46,"value":199},"Use the connector's ",{"type":41,"tag":127,"props":201,"children":203},{"className":202},[],[204],{"type":46,"value":205},"update_event",{"type":46,"value":207}," action for recurring edits and set ",{"type":41,"tag":127,"props":209,"children":211},{"className":210},[],[212],{"type":46,"value":213},"update_scope",{"type":46,"value":215}," to ",{"type":41,"tag":127,"props":217,"children":219},{"className":218},[],[220],{"type":46,"value":221},"this_instance",{"type":46,"value":223},", ",{"type":41,"tag":127,"props":225,"children":227},{"className":226},[],[228],{"type":46,"value":229},"entire_series",{"type":46,"value":231},", or ",{"type":41,"tag":127,"props":233,"children":235},{"className":234},[],[236],{"type":46,"value":237},"this_and_following",{"type":46,"value":239}," as needed. If the series is COUNT-based and the tool requires an explicit recurrence for a future-only split, preserve and restate the recurrence rule or explain that the connector cannot safely infer the split from one occurrence.",{"type":41,"tag":71,"props":241,"children":242},{},[243],{"type":46,"value":244},"For room-finding requests, do not assume there is a reliable global room search. In this V1 flow, mine a reasonable window of past meetings, locations, and resource attendees to build a candidate room list, then compare availability on that concrete set.",{"type":41,"tag":71,"props":246,"children":247},{},[248],{"type":46,"value":249},"For bulk reminder or classification-based edit requests, inspect a reasonable upcoming window first instead of asking for extra scoping immediately. If the prompt does not bound the horizon, use a narrow default such as the next 30 days and say so.",{"type":41,"tag":71,"props":251,"children":252},{},[253],{"type":46,"value":254},"When notes, prep context, or missing details matter, inspect the event payload before proposing a change.",{"type":41,"tag":71,"props":256,"children":257},{},[258],{"type":46,"value":259},"For free-slot and temporary-hold requests, if the prompt already gives the window and duration, search within that range and move directly to proposing or placing the hold. Prefer a transparent hold for temporary placeholders unless the user clearly wants a blocking focus block.",{"type":41,"tag":71,"props":261,"children":262},{},[263],{"type":46,"value":264},"Surface conflicts, transparent holds, and missing meeting details before suggesting a write.",{"type":41,"tag":71,"props":266,"children":267},{},[268],{"type":46,"value":269},"If the request is still ambiguous after checking for precedent or scanning a reasonable bounded window, summarize the candidate slots or exact diff before writing anything.",{"type":41,"tag":48,"props":271,"children":273},{"id":272},"write-safety",[274],{"type":46,"value":275},"Write Safety",{"type":41,"tag":67,"props":277,"children":278},{},[279,284,289,333,338,343,348],{"type":41,"tag":71,"props":280,"children":281},{},[282],{"type":46,"value":283},"Preserve source event details unless the user asked to change them.",{"type":41,"tag":71,"props":285,"children":286},{},[287],{"type":46,"value":288},"When changing reminders, preserve title, attendees, location, meeting link, and notes unless the user asked to change them.",{"type":41,"tag":71,"props":290,"children":291},{},[292,294,300,302,308,310,316,318,324,325,331],{"type":46,"value":293},"For Google Calendar reminder writes, prefer the structured ",{"type":41,"tag":127,"props":295,"children":297},{"className":296},[],[298],{"type":46,"value":299},"reminders",{"type":46,"value":301}," object rather than free-form reminder text. Use ",{"type":41,"tag":127,"props":303,"children":305},{"className":304},[],[306],{"type":46,"value":307},"use_default",{"type":46,"value":309}," plus explicit ",{"type":41,"tag":127,"props":311,"children":313},{"className":312},[],[314],{"type":46,"value":315},"overrides",{"type":46,"value":317}," with ",{"type":41,"tag":127,"props":319,"children":321},{"className":320},[],[322],{"type":46,"value":323},"method",{"type":46,"value":134},{"type":41,"tag":127,"props":326,"children":328},{"className":327},[],[329],{"type":46,"value":330},"minutes",{"type":46,"value":332}," when the user wants custom reminder timing.",{"type":41,"tag":71,"props":334,"children":335},{},[336],{"type":46,"value":337},"Treat deletes and broad availability changes as high-impact actions.",{"type":41,"tag":71,"props":339,"children":340},{},[341],{"type":46,"value":342},"For bulk reminder or hold writes, restate the qualifying event set and time window before applying them.",{"type":41,"tag":71,"props":344,"children":345},{},[346],{"type":46,"value":347},"If multiple calendars or similarly named events are in play, identify the intended one explicitly before editing.",{"type":41,"tag":71,"props":349,"children":350},{},[351],{"type":46,"value":352},"Treat missing title, attendees, location, meeting link, or timezone as confirmation points rather than assumptions only after checking whether the missing detail is recoverable from a bounded calendar search or the relevant source event.",{"type":41,"tag":48,"props":354,"children":356},{"id":355},"output-conventions",[357],{"type":46,"value":358},"Output Conventions",{"type":41,"tag":67,"props":360,"children":361},{},[362,367,372,377,382,387,392],{"type":41,"tag":71,"props":363,"children":364},{},[365],{"type":46,"value":366},"Present scheduling summaries with exact weekday, date, time, and timezone.",{"type":41,"tag":71,"props":368,"children":369},{},[370],{"type":46,"value":371},"When sharing availability, say why a slot works or conflicts instead of listing raw times without context.",{"type":41,"tag":71,"props":373,"children":374},{},[375],{"type":46,"value":376},"When suggesting a room or resource, name the likely room and why it is a fit, such as prior usage, matching location, or open busy windows.",{"type":41,"tag":71,"props":378,"children":379},{},[380],{"type":46,"value":381},"When reporting reminder changes, name which meetings qualify, the exact lead time, and whether the scope is one event, future events, or a bounded meeting set.",{"type":41,"tag":71,"props":383,"children":384},{},[385],{"type":46,"value":386},"When proposing or placing a temporary hold, say whether it is transparent or busy and why that choice fits the user's request.",{"type":41,"tag":71,"props":388,"children":389},{},[390],{"type":46,"value":391},"When comparing options, keep the list short and explain the tradeoff for each slot.",{"type":41,"tag":71,"props":393,"children":394},{},[395],{"type":46,"value":396},"When the user asks for meeting notes or prep context, mention whether the answer came from the event description, an attachment, or both.",{"type":41,"tag":48,"props":398,"children":400},{"id":399},"example-requests",[401],{"type":46,"value":402},"Example Requests",{"type":41,"tag":67,"props":404,"children":405},{},[406,411,416,421,426,431,436],{"type":41,"tag":71,"props":407,"children":408},{},[409],{"type":46,"value":410},"\"Check my availability with Priya this Thursday afternoon and suggest the best two meeting slots.\"",{"type":41,"tag":71,"props":412,"children":413},{},[414],{"type":46,"value":415},"\"Find a 1-hour slot next week where I'm free and place a temporary hold on it.\"",{"type":41,"tag":71,"props":417,"children":418},{},[419],{"type":46,"value":420},"\"Find a room for the weekly team sync next Tuesday by checking rooms we've used before and which ones are free.\"",{"type":41,"tag":71,"props":422,"children":423},{},[424],{"type":46,"value":425},"\"Move the design review to next week and keep the same attendees and Zoom link.\"",{"type":41,"tag":71,"props":427,"children":428},{},[429],{"type":46,"value":430},"\"Add 1-hour reminders to my external-facing meetings next month and leave internal meetings unchanged.\"",{"type":41,"tag":71,"props":432,"children":433},{},[434],{"type":46,"value":435},"\"Summarize my calendar for tomorrow and flag anything that overlaps or leaves no travel time.\"",{"type":41,"tag":71,"props":437,"children":438},{},[439],{"type":46,"value":440},"\"Draft the final event details for a 30 minute customer sync at 2 PM Pacific on Friday.\"",{"items":442,"total":643},[443,464,487,504,520,539,554,570,586,600,612,627],{"slug":444,"name":444,"fn":445,"description":446,"org":447,"tags":448,"stars":461,"repoUrl":462,"updatedAt":463},"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},[449,452,455,458],{"name":450,"slug":451,"type":15},"Documents","documents",{"name":453,"slug":454,"type":15},"Healthcare","healthcare",{"name":456,"slug":457,"type":15},"Insurance","insurance",{"name":459,"slug":460,"type":15},"Regulatory Compliance","regulatory-compliance",28169,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fopenai-agents-python","2026-04-16T05:11:39.180399",{"slug":465,"name":465,"fn":466,"description":467,"org":468,"tags":469,"stars":484,"repoUrl":485,"updatedAt":486},"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},[470,473,475,478,481],{"name":471,"slug":472,"type":15},".NET","dotnet",{"name":474,"slug":465,"type":15},"ASP.NET Core",{"name":476,"slug":477,"type":15},"Blazor","blazor",{"name":479,"slug":480,"type":15},"C#","csharp",{"name":482,"slug":483,"type":15},"Web Development","web-development",23787,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fskills","2026-04-12T05:07:02.819491",{"slug":488,"name":488,"fn":489,"description":490,"org":491,"tags":492,"stars":484,"repoUrl":485,"updatedAt":503},"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},[493,496,499,502],{"name":494,"slug":495,"type":15},"Apps SDK","apps-sdk",{"name":497,"slug":498,"type":15},"ChatGPT","chatgpt",{"name":500,"slug":501,"type":15},"MCP","mcp",{"name":9,"slug":8,"type":15},"2026-04-12T05:07:05.468097",{"slug":505,"name":505,"fn":506,"description":507,"org":508,"tags":509,"stars":484,"repoUrl":485,"updatedAt":519},"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},[510,513,516],{"name":511,"slug":512,"type":15},"API Development","api-development",{"name":514,"slug":515,"type":15},"CLI","cli",{"name":517,"slug":518,"type":15},"Codex","codex","2026-04-12T05:07:04.132762",{"slug":521,"name":521,"fn":522,"description":523,"org":524,"tags":525,"stars":484,"repoUrl":485,"updatedAt":538},"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},[526,529,532,535],{"name":527,"slug":528,"type":15},"Cloudflare","cloudflare",{"name":530,"slug":531,"type":15},"Cloudflare Pages","cloudflare-pages",{"name":533,"slug":534,"type":15},"Cloudflare Workers","cloudflare-workers",{"name":536,"slug":537,"type":15},"Deployment","deployment","2026-04-12T05:07:14.275118",{"slug":540,"name":540,"fn":541,"description":542,"org":543,"tags":544,"stars":484,"repoUrl":485,"updatedAt":553},"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},[545,546,549,552],{"name":13,"slug":14,"type":15},{"name":547,"slug":548,"type":15},"Project Management","project-management",{"name":550,"slug":551,"type":15},"Strategy","strategy",{"name":22,"slug":23,"type":15},"2026-05-23T06:17:16.870838",{"slug":555,"name":555,"fn":556,"description":557,"org":558,"tags":559,"stars":484,"repoUrl":485,"updatedAt":569},"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},[560,563,565,568],{"name":561,"slug":562,"type":15},"Design","design",{"name":564,"slug":555,"type":15},"Figma",{"name":566,"slug":567,"type":15},"Frontend","frontend",{"name":500,"slug":501,"type":15},"2026-04-12T05:06:47.939943",{"slug":571,"name":571,"fn":572,"description":573,"org":574,"tags":575,"stars":484,"repoUrl":485,"updatedAt":585},"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},[576,577,580,581,582],{"name":561,"slug":562,"type":15},{"name":578,"slug":579,"type":15},"Design System","design-system",{"name":564,"slug":555,"type":15},{"name":566,"slug":567,"type":15},{"name":583,"slug":584,"type":15},"UI Components","ui-components","2026-05-10T05:59:52.971881",{"slug":587,"name":587,"fn":588,"description":589,"org":590,"tags":591,"stars":484,"repoUrl":485,"updatedAt":599},"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},[592,593,594,597,598],{"name":561,"slug":562,"type":15},{"name":578,"slug":579,"type":15},{"name":595,"slug":596,"type":15},"Documentation","documentation",{"name":564,"slug":555,"type":15},{"name":566,"slug":567,"type":15},"2026-05-16T06:07:47.821474",{"slug":601,"name":601,"fn":602,"description":603,"org":604,"tags":605,"stars":484,"repoUrl":485,"updatedAt":611},"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},[606,607,608,609,610],{"name":561,"slug":562,"type":15},{"name":564,"slug":555,"type":15},{"name":566,"slug":567,"type":15},{"name":583,"slug":584,"type":15},{"name":482,"slug":483,"type":15},"2026-05-16T06:07:40.583615",{"slug":613,"name":613,"fn":614,"description":615,"org":616,"tags":617,"stars":484,"repoUrl":485,"updatedAt":626},"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},[618,621,622,625],{"name":619,"slug":620,"type":15},"Animation","animation",{"name":517,"slug":518,"type":15},{"name":623,"slug":624,"type":15},"Creative","creative",{"name":561,"slug":562,"type":15},"2026-05-02T05:31:48.48485",{"slug":628,"name":628,"fn":629,"description":630,"org":631,"tags":632,"stars":484,"repoUrl":485,"updatedAt":642},"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},[633,634,635,638,641],{"name":623,"slug":624,"type":15},{"name":561,"slug":562,"type":15},{"name":636,"slug":637,"type":15},"Image Generation","image-generation",{"name":639,"slug":640,"type":15},"Images","images",{"name":9,"slug":8,"type":15},"2026-05-15T06:23:24.312127",675,{"items":645,"total":759},[646,663,679,691,709,727,747],{"slug":647,"name":647,"fn":648,"description":649,"org":650,"tags":651,"stars":24,"repoUrl":25,"updatedAt":662},"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},[652,655,658,661],{"name":653,"slug":654,"type":15},"Accessibility","accessibility",{"name":656,"slug":657,"type":15},"Charts","charts",{"name":659,"slug":660,"type":15},"Data Visualization","data-visualization",{"name":561,"slug":562,"type":15},"2026-06-30T19:00:57.102",{"slug":664,"name":664,"fn":665,"description":666,"org":667,"tags":668,"stars":24,"repoUrl":25,"updatedAt":678},"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},[669,672,675],{"name":670,"slug":671,"type":15},"Agents","agents",{"name":673,"slug":674,"type":15},"Browser Automation","browser-automation",{"name":676,"slug":677,"type":15},"Testing","testing","2026-04-06T18:41:03.44016",{"slug":680,"name":680,"fn":681,"description":682,"org":683,"tags":684,"stars":24,"repoUrl":25,"updatedAt":690},"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},[685,686,689],{"name":673,"slug":674,"type":15},{"name":687,"slug":688,"type":15},"Local Development","local-development",{"name":676,"slug":677,"type":15},"2026-04-06T18:41:17.526867",{"slug":692,"name":692,"fn":693,"description":694,"org":695,"tags":696,"stars":24,"repoUrl":25,"updatedAt":708},"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},[697,698,699,702,705],{"name":670,"slug":671,"type":15},{"name":533,"slug":534,"type":15},{"name":700,"slug":701,"type":15},"SDK","sdk",{"name":703,"slug":704,"type":15},"Serverless","serverless",{"name":706,"slug":707,"type":15},"WebSockets","websockets","2026-04-06T18:39:51.717063",{"slug":710,"name":710,"fn":711,"description":712,"org":713,"tags":714,"stars":24,"repoUrl":25,"updatedAt":726},"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},[715,716,719,722,723],{"name":566,"slug":567,"type":15},{"name":717,"slug":718,"type":15},"React","react",{"name":720,"slug":721,"type":15},"shadcn\u002Fui","shadcn-ui",{"name":583,"slug":584,"type":15},{"name":724,"slug":725,"type":15},"Vercel","vercel","2026-04-06T18:40:59.619419",{"slug":728,"name":728,"fn":729,"description":730,"org":731,"tags":732,"stars":24,"repoUrl":25,"updatedAt":746},"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},[733,736,739,742,745],{"name":734,"slug":735,"type":15},"AI Infrastructure","ai-infrastructure",{"name":737,"slug":738,"type":15},"Cost Optimization","cost-optimization",{"name":740,"slug":741,"type":15},"LLM","llm",{"name":743,"slug":744,"type":15},"Performance","performance",{"name":724,"slug":725,"type":15},"2026-04-06T18:40:44.377464",{"slug":748,"name":748,"fn":749,"description":750,"org":751,"tags":752,"stars":24,"repoUrl":25,"updatedAt":758},"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},[753,754,757],{"name":737,"slug":738,"type":15},{"name":755,"slug":756,"type":15},"Database","database",{"name":740,"slug":741,"type":15},"2026-04-06T18:41:08.513425",600]