[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-openai-posthog":3,"mdc-wkklpq-key":41,"related-repo-openai-posthog":536,"related-org-openai-posthog":659},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":30,"repoUrl":31,"updatedAt":32,"license":33,"forks":34,"topics":35,"repo":36,"sourceUrl":39,"mdContent":40},"posthog","analyze product data and manage PostHog tools","Analyze product data and manage product tooling in PostHog. Use when the user wants product analytics or insights, HogQL\u002FSQL queries, feature flags, experiments and A\u002FB tests, error tracking, session replay, surveys, LLM analytics, dashboards, data warehouse, or PostHog documentation.",{"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,24,27],{"name":13,"slug":14,"type":15},"Observability","observability","tag",{"name":17,"slug":4,"type":15},"PostHog",{"name":19,"slug":20,"type":15},"Feature Flags","feature-flags",{"name":22,"slug":23,"type":15},"Analytics","analytics",{"name":25,"slug":26,"type":15},"A\u002FB Testing","a-b-testing",{"name":28,"slug":29,"type":15},"Debugging","debugging",3992,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins","2026-06-30T19:00:57.102",null,465,[],{"repoUrl":31,"stars":30,"forks":34,"topics":37,"description":38},[],"OpenAI Plugins","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins\u002Ftree\u002FHEAD\u002Fplugins\u002Fposthog\u002Fskills\u002Fposthog","---\nname: posthog\ndescription: Analyze product data and manage product tooling in PostHog. Use when the user wants product analytics or insights, HogQL\u002FSQL queries, feature flags, experiments and A\u002FB tests, error tracking, session replay, surveys, LLM analytics, dashboards, data warehouse, or PostHog documentation.\n---\n\n# PostHog\n\n## Overview\n\nThis skill provides a structured workflow for working with PostHog from ChatGPT and Codex. It assumes the bundled PostHog app is connected so the PostHog tools are available for analytics, feature flags, experiments, error tracking, and more.\n\nPostHog is an all-in-one product platform. The same project's data backs every surface below, so most questions can be answered by querying analytics or running HogQL, and most product changes (flags, experiments, surveys) can be made directly.\n\n**Prefer live tools over pre-trained knowledge.** Your baked-in knowledge of PostHog's API, HogQL functions, and tool shapes may be outdated. The connected PostHog app advertises its own skills and tools at runtime and asks clients to *prioritize its skills over raw tools* — discover and follow those rather than guessing. When in doubt about syntax, limits, or product behavior, use the documentation-search tool.\n\n## Prerequisites\n- The PostHog app must be connected and accessible via OAuth.\n- Confirm which PostHog organization and project the request targets before reading or writing.\n- Self-hosted users connect against their own instance during the app's OAuth flow.\n\n## Required Workflow\n\n**Follow these steps in order. Do not skip steps.**\n\n### Step 0: Connect the PostHog app (if not already configured)\n\nIf PostHog tools are unavailable, pause and ask the user to connect the PostHog app:\n\n1. Enable the bundled PostHog app for this plugin or session.\n2. Complete the PostHog OAuth flow if prompted, and select the correct organization\u002Fproject.\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### Step 1\nClarify the user's goal and scope (e.g., a metric over a time range, a funnel, a new feature flag, an experiment readout, an error investigation). Confirm the target project, date range, event\u002Fproperty names, and any filters or cohorts.\n\n### Step 2\nDiscover the available PostHog skills\u002Ftools the connected app exposes and pick the right one for the task. Resolve identifiers (project ID, flag key, experiment ID, insight\u002Fdashboard ID, error issue ID) before calling tools. For anything involving syntax, function names, or product behavior, search the docs first.\n\n### Step 3\nExecute PostHog tool calls in logical batches:\n- **Read first** — list\u002Fget\u002Fquery (insights, events, HogQL\u002FSQL, error issues) to build context.\n- **Write next** — create or update flags, experiments, surveys, dashboards, or insights with all required fields.\n- For destructive or broad changes (e.g., toggling a flag in production, ending an experiment), state the impact and confirm before applying.\n\n### Step 4\nSummarize results with concrete numbers and links to the PostHog UI where available, call out caveats (sampling, person-on-events timing, date ranges), and propose next actions.\n\n## Capability Map\n\nUse this to route a request to the right PostHog surface, then discover the exact tool the app exposes for it.\n\n| If the user wants to… | PostHog surface |\n| --- | --- |\n| Answer a metric\u002Ftrend\u002Ffunnel\u002Fretention\u002Fpath question | Insights & queries (trends, funnels, retention, paths, lifecycle, stickiness) |\n| Run arbitrary SQL over events\u002Fpersons | HogQL \u002F SQL execution |\n| Create, toggle, or audit a feature flag | Feature flags |\n| Launch or read out an A\u002FB test | Experiments |\n| Investigate a bug or exception | Error tracking (issues + events) |\n| Watch how users actually behave | Session replay |\n| Gather qualitative feedback (NPS, surveys) | Surveys |\n| Track LLM cost\u002Flatency\u002Fusage | LLM analytics |\n| Build or update a dashboard | Dashboards & insights |\n| Connect or query external data | Data warehouse |\n| Look up how something works in PostHog | Documentation search |\n\n## HogQL & Querying Tips\n- HogQL is PostHog's SQL dialect over the events\u002Fpersons schema. Read the data schema before writing queries, and confirm event and property names exist.\n- With person-on-events enabled, `person.properties.*` on the events table reflect the value at ingestion time, not the person's current value — the same person can show different values across events. Don't build workarounds for \"query-time\" person properties.\n- Respect the project timezone when bucketing by day.\n- Start narrow (small date range, limited rows), validate, then widen.\n\n## Tips for Maximum Productivity\n- Batch related reads before writes; confirm identifiers up front.\n- Use natural-language asks where the app supports them (\"signups by week this quarter\").\n- Reference prior insights\u002Fdashboards instead of rebuilding from scratch.\n- For experiments and flags, double-check rollout conditions and targeting before enabling.\n\n## Troubleshooting\n- **Tools missing**: re-run the app connection\u002FOAuth flow (Step 0); verify org\u002Fproject access.\n- **Empty or surprising results**: re-check event\u002Fproperty names, date range, filters, and timezone; confirm the events exist via a small query.\n- **Permission errors**: confirm the connected account has access to the target project and the action (some changes require elevated roles).\n- **Unsure about syntax or limits**: search the PostHog docs rather than guessing.\n",{"data":42,"body":43},{"name":4,"description":6},{"type":44,"children":45},"root",[46,53,60,66,71,90,96,116,122,130,137,142,161,166,172,177,183,188,194,199,227,233,238,244,249,420,426,458,464,487,493],{"type":47,"tag":48,"props":49,"children":50},"element","h1",{"id":4},[51],{"type":52,"value":17},"text",{"type":47,"tag":54,"props":55,"children":57},"h2",{"id":56},"overview",[58],{"type":52,"value":59},"Overview",{"type":47,"tag":61,"props":62,"children":63},"p",{},[64],{"type":52,"value":65},"This skill provides a structured workflow for working with PostHog from ChatGPT and Codex. It assumes the bundled PostHog app is connected so the PostHog tools are available for analytics, feature flags, experiments, error tracking, and more.",{"type":47,"tag":61,"props":67,"children":68},{},[69],{"type":52,"value":70},"PostHog is an all-in-one product platform. The same project's data backs every surface below, so most questions can be answered by querying analytics or running HogQL, and most product changes (flags, experiments, surveys) can be made directly.",{"type":47,"tag":61,"props":72,"children":73},{},[74,80,82,88],{"type":47,"tag":75,"props":76,"children":77},"strong",{},[78],{"type":52,"value":79},"Prefer live tools over pre-trained knowledge.",{"type":52,"value":81}," Your baked-in knowledge of PostHog's API, HogQL functions, and tool shapes may be outdated. The connected PostHog app advertises its own skills and tools at runtime and asks clients to ",{"type":47,"tag":83,"props":84,"children":85},"em",{},[86],{"type":52,"value":87},"prioritize its skills over raw tools",{"type":52,"value":89}," — discover and follow those rather than guessing. When in doubt about syntax, limits, or product behavior, use the documentation-search tool.",{"type":47,"tag":54,"props":91,"children":93},{"id":92},"prerequisites",[94],{"type":52,"value":95},"Prerequisites",{"type":47,"tag":97,"props":98,"children":99},"ul",{},[100,106,111],{"type":47,"tag":101,"props":102,"children":103},"li",{},[104],{"type":52,"value":105},"The PostHog app must be connected and accessible via OAuth.",{"type":47,"tag":101,"props":107,"children":108},{},[109],{"type":52,"value":110},"Confirm which PostHog organization and project the request targets before reading or writing.",{"type":47,"tag":101,"props":112,"children":113},{},[114],{"type":52,"value":115},"Self-hosted users connect against their own instance during the app's OAuth flow.",{"type":47,"tag":54,"props":117,"children":119},{"id":118},"required-workflow",[120],{"type":52,"value":121},"Required Workflow",{"type":47,"tag":61,"props":123,"children":124},{},[125],{"type":47,"tag":75,"props":126,"children":127},{},[128],{"type":52,"value":129},"Follow these steps in order. Do not skip steps.",{"type":47,"tag":131,"props":132,"children":134},"h3",{"id":133},"step-0-connect-the-posthog-app-if-not-already-configured",[135],{"type":52,"value":136},"Step 0: Connect the PostHog app (if not already configured)",{"type":47,"tag":61,"props":138,"children":139},{},[140],{"type":52,"value":141},"If PostHog tools are unavailable, pause and ask the user to connect the PostHog app:",{"type":47,"tag":143,"props":144,"children":145},"ol",{},[146,151,156],{"type":47,"tag":101,"props":147,"children":148},{},[149],{"type":52,"value":150},"Enable the bundled PostHog app for this plugin or session.",{"type":47,"tag":101,"props":152,"children":153},{},[154],{"type":52,"value":155},"Complete the PostHog OAuth flow if prompted, and select the correct organization\u002Fproject.",{"type":47,"tag":101,"props":157,"children":158},{},[159],{"type":52,"value":160},"Restart Codex or the current session if the tools still do not appear.",{"type":47,"tag":61,"props":162,"children":163},{},[164],{"type":52,"value":165},"After the app is connected, finish your answer and tell the user to retry so they can continue with Step 1.",{"type":47,"tag":131,"props":167,"children":169},{"id":168},"step-1",[170],{"type":52,"value":171},"Step 1",{"type":47,"tag":61,"props":173,"children":174},{},[175],{"type":52,"value":176},"Clarify the user's goal and scope (e.g., a metric over a time range, a funnel, a new feature flag, an experiment readout, an error investigation). Confirm the target project, date range, event\u002Fproperty names, and any filters or cohorts.",{"type":47,"tag":131,"props":178,"children":180},{"id":179},"step-2",[181],{"type":52,"value":182},"Step 2",{"type":47,"tag":61,"props":184,"children":185},{},[186],{"type":52,"value":187},"Discover the available PostHog skills\u002Ftools the connected app exposes and pick the right one for the task. Resolve identifiers (project ID, flag key, experiment ID, insight\u002Fdashboard ID, error issue ID) before calling tools. For anything involving syntax, function names, or product behavior, search the docs first.",{"type":47,"tag":131,"props":189,"children":191},{"id":190},"step-3",[192],{"type":52,"value":193},"Step 3",{"type":47,"tag":61,"props":195,"children":196},{},[197],{"type":52,"value":198},"Execute PostHog tool calls in logical batches:",{"type":47,"tag":97,"props":200,"children":201},{},[202,212,222],{"type":47,"tag":101,"props":203,"children":204},{},[205,210],{"type":47,"tag":75,"props":206,"children":207},{},[208],{"type":52,"value":209},"Read first",{"type":52,"value":211}," — list\u002Fget\u002Fquery (insights, events, HogQL\u002FSQL, error issues) to build context.",{"type":47,"tag":101,"props":213,"children":214},{},[215,220],{"type":47,"tag":75,"props":216,"children":217},{},[218],{"type":52,"value":219},"Write next",{"type":52,"value":221}," — create or update flags, experiments, surveys, dashboards, or insights with all required fields.",{"type":47,"tag":101,"props":223,"children":224},{},[225],{"type":52,"value":226},"For destructive or broad changes (e.g., toggling a flag in production, ending an experiment), state the impact and confirm before applying.",{"type":47,"tag":131,"props":228,"children":230},{"id":229},"step-4",[231],{"type":52,"value":232},"Step 4",{"type":47,"tag":61,"props":234,"children":235},{},[236],{"type":52,"value":237},"Summarize results with concrete numbers and links to the PostHog UI where available, call out caveats (sampling, person-on-events timing, date ranges), and propose next actions.",{"type":47,"tag":54,"props":239,"children":241},{"id":240},"capability-map",[242],{"type":52,"value":243},"Capability Map",{"type":47,"tag":61,"props":245,"children":246},{},[247],{"type":52,"value":248},"Use this to route a request to the right PostHog surface, then discover the exact tool the app exposes for it.",{"type":47,"tag":250,"props":251,"children":252},"table",{},[253,272],{"type":47,"tag":254,"props":255,"children":256},"thead",{},[257],{"type":47,"tag":258,"props":259,"children":260},"tr",{},[261,267],{"type":47,"tag":262,"props":263,"children":264},"th",{},[265],{"type":52,"value":266},"If the user wants to…",{"type":47,"tag":262,"props":268,"children":269},{},[270],{"type":52,"value":271},"PostHog surface",{"type":47,"tag":273,"props":274,"children":275},"tbody",{},[276,290,303,316,329,342,355,368,381,394,407],{"type":47,"tag":258,"props":277,"children":278},{},[279,285],{"type":47,"tag":280,"props":281,"children":282},"td",{},[283],{"type":52,"value":284},"Answer a metric\u002Ftrend\u002Ffunnel\u002Fretention\u002Fpath question",{"type":47,"tag":280,"props":286,"children":287},{},[288],{"type":52,"value":289},"Insights & queries (trends, funnels, retention, paths, lifecycle, stickiness)",{"type":47,"tag":258,"props":291,"children":292},{},[293,298],{"type":47,"tag":280,"props":294,"children":295},{},[296],{"type":52,"value":297},"Run arbitrary SQL over events\u002Fpersons",{"type":47,"tag":280,"props":299,"children":300},{},[301],{"type":52,"value":302},"HogQL \u002F SQL execution",{"type":47,"tag":258,"props":304,"children":305},{},[306,311],{"type":47,"tag":280,"props":307,"children":308},{},[309],{"type":52,"value":310},"Create, toggle, or audit a feature flag",{"type":47,"tag":280,"props":312,"children":313},{},[314],{"type":52,"value":315},"Feature flags",{"type":47,"tag":258,"props":317,"children":318},{},[319,324],{"type":47,"tag":280,"props":320,"children":321},{},[322],{"type":52,"value":323},"Launch or read out an A\u002FB test",{"type":47,"tag":280,"props":325,"children":326},{},[327],{"type":52,"value":328},"Experiments",{"type":47,"tag":258,"props":330,"children":331},{},[332,337],{"type":47,"tag":280,"props":333,"children":334},{},[335],{"type":52,"value":336},"Investigate a bug or exception",{"type":47,"tag":280,"props":338,"children":339},{},[340],{"type":52,"value":341},"Error tracking (issues + events)",{"type":47,"tag":258,"props":343,"children":344},{},[345,350],{"type":47,"tag":280,"props":346,"children":347},{},[348],{"type":52,"value":349},"Watch how users actually behave",{"type":47,"tag":280,"props":351,"children":352},{},[353],{"type":52,"value":354},"Session replay",{"type":47,"tag":258,"props":356,"children":357},{},[358,363],{"type":47,"tag":280,"props":359,"children":360},{},[361],{"type":52,"value":362},"Gather qualitative feedback (NPS, surveys)",{"type":47,"tag":280,"props":364,"children":365},{},[366],{"type":52,"value":367},"Surveys",{"type":47,"tag":258,"props":369,"children":370},{},[371,376],{"type":47,"tag":280,"props":372,"children":373},{},[374],{"type":52,"value":375},"Track LLM cost\u002Flatency\u002Fusage",{"type":47,"tag":280,"props":377,"children":378},{},[379],{"type":52,"value":380},"LLM analytics",{"type":47,"tag":258,"props":382,"children":383},{},[384,389],{"type":47,"tag":280,"props":385,"children":386},{},[387],{"type":52,"value":388},"Build or update a dashboard",{"type":47,"tag":280,"props":390,"children":391},{},[392],{"type":52,"value":393},"Dashboards & insights",{"type":47,"tag":258,"props":395,"children":396},{},[397,402],{"type":47,"tag":280,"props":398,"children":399},{},[400],{"type":52,"value":401},"Connect or query external data",{"type":47,"tag":280,"props":403,"children":404},{},[405],{"type":52,"value":406},"Data warehouse",{"type":47,"tag":258,"props":408,"children":409},{},[410,415],{"type":47,"tag":280,"props":411,"children":412},{},[413],{"type":52,"value":414},"Look up how something works in PostHog",{"type":47,"tag":280,"props":416,"children":417},{},[418],{"type":52,"value":419},"Documentation search",{"type":47,"tag":54,"props":421,"children":423},{"id":422},"hogql-querying-tips",[424],{"type":52,"value":425},"HogQL & Querying Tips",{"type":47,"tag":97,"props":427,"children":428},{},[429,434,448,453],{"type":47,"tag":101,"props":430,"children":431},{},[432],{"type":52,"value":433},"HogQL is PostHog's SQL dialect over the events\u002Fpersons schema. Read the data schema before writing queries, and confirm event and property names exist.",{"type":47,"tag":101,"props":435,"children":436},{},[437,439,446],{"type":52,"value":438},"With person-on-events enabled, ",{"type":47,"tag":440,"props":441,"children":443},"code",{"className":442},[],[444],{"type":52,"value":445},"person.properties.*",{"type":52,"value":447}," on the events table reflect the value at ingestion time, not the person's current value — the same person can show different values across events. Don't build workarounds for \"query-time\" person properties.",{"type":47,"tag":101,"props":449,"children":450},{},[451],{"type":52,"value":452},"Respect the project timezone when bucketing by day.",{"type":47,"tag":101,"props":454,"children":455},{},[456],{"type":52,"value":457},"Start narrow (small date range, limited rows), validate, then widen.",{"type":47,"tag":54,"props":459,"children":461},{"id":460},"tips-for-maximum-productivity",[462],{"type":52,"value":463},"Tips for Maximum Productivity",{"type":47,"tag":97,"props":465,"children":466},{},[467,472,477,482],{"type":47,"tag":101,"props":468,"children":469},{},[470],{"type":52,"value":471},"Batch related reads before writes; confirm identifiers up front.",{"type":47,"tag":101,"props":473,"children":474},{},[475],{"type":52,"value":476},"Use natural-language asks where the app supports them (\"signups by week this quarter\").",{"type":47,"tag":101,"props":478,"children":479},{},[480],{"type":52,"value":481},"Reference prior insights\u002Fdashboards instead of rebuilding from scratch.",{"type":47,"tag":101,"props":483,"children":484},{},[485],{"type":52,"value":486},"For experiments and flags, double-check rollout conditions and targeting before enabling.",{"type":47,"tag":54,"props":488,"children":490},{"id":489},"troubleshooting",[491],{"type":52,"value":492},"Troubleshooting",{"type":47,"tag":97,"props":494,"children":495},{},[496,506,516,526],{"type":47,"tag":101,"props":497,"children":498},{},[499,504],{"type":47,"tag":75,"props":500,"children":501},{},[502],{"type":52,"value":503},"Tools missing",{"type":52,"value":505},": re-run the app connection\u002FOAuth flow (Step 0); verify org\u002Fproject access.",{"type":47,"tag":101,"props":507,"children":508},{},[509,514],{"type":47,"tag":75,"props":510,"children":511},{},[512],{"type":52,"value":513},"Empty or surprising results",{"type":52,"value":515},": re-check event\u002Fproperty names, date range, filters, and timezone; confirm the events exist via a small query.",{"type":47,"tag":101,"props":517,"children":518},{},[519,524],{"type":47,"tag":75,"props":520,"children":521},{},[522],{"type":52,"value":523},"Permission errors",{"type":52,"value":525},": confirm the connected account has access to the target project and the action (some changes require elevated roles).",{"type":47,"tag":101,"props":527,"children":528},{},[529,534],{"type":47,"tag":75,"props":530,"children":531},{},[532],{"type":52,"value":533},"Unsure about syntax or limits",{"type":52,"value":535},": search the PostHog docs rather than guessing.",{"items":537,"total":658},[538,556,572,584,604,626,646],{"slug":539,"name":539,"fn":540,"description":541,"org":542,"tags":543,"stars":30,"repoUrl":31,"updatedAt":32},"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},[544,547,550,553],{"name":545,"slug":546,"type":15},"Accessibility","accessibility",{"name":548,"slug":549,"type":15},"Charts","charts",{"name":551,"slug":552,"type":15},"Data Visualization","data-visualization",{"name":554,"slug":555,"type":15},"Design","design",{"slug":557,"name":557,"fn":558,"description":559,"org":560,"tags":561,"stars":30,"repoUrl":31,"updatedAt":571},"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},[562,565,568],{"name":563,"slug":564,"type":15},"Agents","agents",{"name":566,"slug":567,"type":15},"Browser Automation","browser-automation",{"name":569,"slug":570,"type":15},"Testing","testing","2026-04-06T18:41:03.44016",{"slug":573,"name":573,"fn":574,"description":575,"org":576,"tags":577,"stars":30,"repoUrl":31,"updatedAt":583},"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},[578,579,582],{"name":566,"slug":567,"type":15},{"name":580,"slug":581,"type":15},"Local Development","local-development",{"name":569,"slug":570,"type":15},"2026-04-06T18:41:17.526867",{"slug":585,"name":585,"fn":586,"description":587,"org":588,"tags":589,"stars":30,"repoUrl":31,"updatedAt":603},"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},[590,591,594,597,600],{"name":563,"slug":564,"type":15},{"name":592,"slug":593,"type":15},"Cloudflare Workers","cloudflare-workers",{"name":595,"slug":596,"type":15},"SDK","sdk",{"name":598,"slug":599,"type":15},"Serverless","serverless",{"name":601,"slug":602,"type":15},"WebSockets","websockets","2026-04-06T18:39:51.717063",{"slug":605,"name":605,"fn":606,"description":607,"org":608,"tags":609,"stars":30,"repoUrl":31,"updatedAt":625},"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},[610,613,616,619,622],{"name":611,"slug":612,"type":15},"Frontend","frontend",{"name":614,"slug":615,"type":15},"React","react",{"name":617,"slug":618,"type":15},"shadcn\u002Fui","shadcn-ui",{"name":620,"slug":621,"type":15},"UI Components","ui-components",{"name":623,"slug":624,"type":15},"Vercel","vercel","2026-04-06T18:40:59.619419",{"slug":627,"name":627,"fn":628,"description":629,"org":630,"tags":631,"stars":30,"repoUrl":31,"updatedAt":645},"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},[632,635,638,641,644],{"name":633,"slug":634,"type":15},"AI Infrastructure","ai-infrastructure",{"name":636,"slug":637,"type":15},"Cost Optimization","cost-optimization",{"name":639,"slug":640,"type":15},"LLM","llm",{"name":642,"slug":643,"type":15},"Performance","performance",{"name":623,"slug":624,"type":15},"2026-04-06T18:40:44.377464",{"slug":647,"name":647,"fn":648,"description":649,"org":650,"tags":651,"stars":30,"repoUrl":31,"updatedAt":657},"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},[652,653,656],{"name":636,"slug":637,"type":15},{"name":654,"slug":655,"type":15},"Database","database",{"name":639,"slug":640,"type":15},"2026-04-06T18:41:08.513425",600,{"items":660,"total":857},[661,682,705,722,738,755,774,786,800,814,826,841],{"slug":662,"name":662,"fn":663,"description":664,"org":665,"tags":666,"stars":679,"repoUrl":680,"updatedAt":681},"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},[667,670,673,676],{"name":668,"slug":669,"type":15},"Documents","documents",{"name":671,"slug":672,"type":15},"Healthcare","healthcare",{"name":674,"slug":675,"type":15},"Insurance","insurance",{"name":677,"slug":678,"type":15},"Regulatory Compliance","regulatory-compliance",28169,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fopenai-agents-python","2026-04-16T05:11:39.180399",{"slug":683,"name":683,"fn":684,"description":685,"org":686,"tags":687,"stars":702,"repoUrl":703,"updatedAt":704},"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},[688,691,693,696,699],{"name":689,"slug":690,"type":15},".NET","dotnet",{"name":692,"slug":683,"type":15},"ASP.NET Core",{"name":694,"slug":695,"type":15},"Blazor","blazor",{"name":697,"slug":698,"type":15},"C#","csharp",{"name":700,"slug":701,"type":15},"Web Development","web-development",23787,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fskills","2026-04-12T05:07:02.819491",{"slug":706,"name":706,"fn":707,"description":708,"org":709,"tags":710,"stars":702,"repoUrl":703,"updatedAt":721},"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},[711,714,717,720],{"name":712,"slug":713,"type":15},"Apps SDK","apps-sdk",{"name":715,"slug":716,"type":15},"ChatGPT","chatgpt",{"name":718,"slug":719,"type":15},"MCP","mcp",{"name":9,"slug":8,"type":15},"2026-04-12T05:07:05.468097",{"slug":723,"name":723,"fn":724,"description":725,"org":726,"tags":727,"stars":702,"repoUrl":703,"updatedAt":737},"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},[728,731,734],{"name":729,"slug":730,"type":15},"API Development","api-development",{"name":732,"slug":733,"type":15},"CLI","cli",{"name":735,"slug":736,"type":15},"Codex","codex","2026-04-12T05:07:04.132762",{"slug":739,"name":739,"fn":740,"description":741,"org":742,"tags":743,"stars":702,"repoUrl":703,"updatedAt":754},"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},[744,747,750,751],{"name":745,"slug":746,"type":15},"Cloudflare","cloudflare",{"name":748,"slug":749,"type":15},"Cloudflare Pages","cloudflare-pages",{"name":592,"slug":593,"type":15},{"name":752,"slug":753,"type":15},"Deployment","deployment","2026-04-12T05:07:14.275118",{"slug":756,"name":756,"fn":757,"description":758,"org":759,"tags":760,"stars":702,"repoUrl":703,"updatedAt":773},"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},[761,764,767,770],{"name":762,"slug":763,"type":15},"Productivity","productivity",{"name":765,"slug":766,"type":15},"Project Management","project-management",{"name":768,"slug":769,"type":15},"Strategy","strategy",{"name":771,"slug":772,"type":15},"Task Management","task-management","2026-05-23T06:17:16.870838",{"slug":775,"name":775,"fn":776,"description":777,"org":778,"tags":779,"stars":702,"repoUrl":703,"updatedAt":785},"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},[780,781,783,784],{"name":554,"slug":555,"type":15},{"name":782,"slug":775,"type":15},"Figma",{"name":611,"slug":612,"type":15},{"name":718,"slug":719,"type":15},"2026-04-12T05:06:47.939943",{"slug":787,"name":787,"fn":788,"description":789,"org":790,"tags":791,"stars":702,"repoUrl":703,"updatedAt":799},"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},[792,793,796,797,798],{"name":554,"slug":555,"type":15},{"name":794,"slug":795,"type":15},"Design System","design-system",{"name":782,"slug":775,"type":15},{"name":611,"slug":612,"type":15},{"name":620,"slug":621,"type":15},"2026-05-10T05:59:52.971881",{"slug":801,"name":801,"fn":802,"description":803,"org":804,"tags":805,"stars":702,"repoUrl":703,"updatedAt":813},"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},[806,807,808,811,812],{"name":554,"slug":555,"type":15},{"name":794,"slug":795,"type":15},{"name":809,"slug":810,"type":15},"Documentation","documentation",{"name":782,"slug":775,"type":15},{"name":611,"slug":612,"type":15},"2026-05-16T06:07:47.821474",{"slug":815,"name":815,"fn":816,"description":817,"org":818,"tags":819,"stars":702,"repoUrl":703,"updatedAt":825},"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},[820,821,822,823,824],{"name":554,"slug":555,"type":15},{"name":782,"slug":775,"type":15},{"name":611,"slug":612,"type":15},{"name":620,"slug":621,"type":15},{"name":700,"slug":701,"type":15},"2026-05-16T06:07:40.583615",{"slug":827,"name":827,"fn":828,"description":829,"org":830,"tags":831,"stars":702,"repoUrl":703,"updatedAt":840},"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},[832,835,836,839],{"name":833,"slug":834,"type":15},"Animation","animation",{"name":735,"slug":736,"type":15},{"name":837,"slug":838,"type":15},"Creative","creative",{"name":554,"slug":555,"type":15},"2026-05-02T05:31:48.48485",{"slug":842,"name":842,"fn":843,"description":844,"org":845,"tags":846,"stars":702,"repoUrl":703,"updatedAt":856},"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},[847,848,849,852,855],{"name":837,"slug":838,"type":15},{"name":554,"slug":555,"type":15},{"name":850,"slug":851,"type":15},"Image Generation","image-generation",{"name":853,"slug":854,"type":15},"Images","images",{"name":9,"slug":8,"type":15},"2026-05-15T06:23:24.312127",675]