[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-openai-chronograph-gp-meeting-prep":3,"mdc--i6cno1-key":36,"related-repo-openai-chronograph-gp-meeting-prep":349,"related-org-openai-chronograph-gp-meeting-prep":473},{"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},"chronograph-gp-meeting-prep","prepare fund manager meeting materials","Prepare an LP to meet with their fund manager (GP): review the fund's latest reporting, surface what changed since last period, and draft the questions worth raising. Use when someone is getting ready for a manager call, quarterly check-in, annual meeting, LPAC meeting, or a re-up decision — for example \"I have my quarterly call with this manager next week, help me prep,\" \"what changed in this fund this quarter,\" \"what should I ask them about these marks,\" or \"what are the red flags in this reporting package.\" Draws on Chronograph fund and portfolio data when connected — captured reporting such as fund performance, schedules of investments, and portfolio company KPI profiles — and asks the LP to provide anything else it needs, such as a capital account statement, investor letter, or AGM or board deck.\n",{"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},"Reporting","reporting","tag",{"name":17,"slug":18,"type":15},"Finance","finance",{"name":20,"slug":21,"type":15},"Meetings","meetings",{"name":23,"slug":24,"type":15},"Private Equity","private-equity",3992,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins","2026-07-01T07:55:45.962594",null,465,[],{"repoUrl":26,"stars":25,"forks":29,"topics":32,"description":33},[],"OpenAI Plugins","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins\u002Ftree\u002FHEAD\u002Fplugins\u002Fchronograph-lp\u002Fskills\u002Fchronograph-gp-meeting-prep","---\nname: chronograph-gp-meeting-prep\ndescription: >\n  Prepare an LP to meet with their fund manager (GP): review the fund's latest\n  reporting, surface what changed since last period, and draft the questions\n  worth raising. Use when someone is getting ready for a manager call, quarterly\n  check-in, annual meeting, LPAC meeting, or a re-up decision — for example \"I\n  have my quarterly call with this manager next week, help me prep,\" \"what\n  changed in this fund this quarter,\" \"what should I ask them about these marks,\"\n  or \"what are the red flags in this reporting package.\" Draws on Chronograph\n  fund and portfolio data when connected — captured reporting such as fund\n  performance, schedules of investments, and portfolio company KPI profiles —\n  and asks the LP to provide anything else it needs, such as a capital account\n  statement, investor letter, or AGM or board deck.\n---\n\n# Chronograph GP Meeting Prep\n\n**Requirements:** A connected Chronograph MCP server. These workflows are designed for permissioned Chronograph users to connect to their private investment data.\n\n## Overview\n\nPrepare an LP for a meeting with a GP by reviewing fund reporting, surfacing what changed, identifying diligence questions, and producing a concise meeting brief. The brief exists to sharpen a forward decision — a re-up, a secondary sale, or an LPAC vote — so prioritize what bears on those. Use Chronograph as the source of truth where connected and permissioned; otherwise work from user-provided reporting materials.\n\nDefault to a chat brief. Create a document, workbook, or deck only when the user asks for an artifact.\n\n## Workflow\n\n1. Clarify scope only when needed: GP, fund, reporting period, meeting type, as-of date, currency, units, output format, and whether the user wants a quick brief or a formal prep document.\n2. Resolve the relevant fund, manager, commitment, reporting period, and LP perspective from Chronograph where available. If Chronograph is unavailable, ask for the GP reporting package or a pasted\u002Fuploaded summary.\n3. Gather the fund baseline, anchoring first on the figures the GP reported this period and citing the source document where available: gross performance, cost, realized and unrealized value, current valuation, portfolio holdings, prior-period values, and fund attributes. Carry net performance — NAV, calls, distributions, TVPI\u002FDPI\u002FRVPI, and net IRR — as the LP's headline return, clearly labeled gross versus net and dated.\n4. Review document-backed reporting content. When Chronograph document semantic search is available, use it as a primary step to find the story behind the numbers: what drove calls and distributions, how the GP describes its marks, and the commentary on portfolio company KPIs.\n5. If a document the meeting needs isn't in the connected context, ask the LP to provide it. Do not infer narrative, management explanations, or meeting context from structured data alone.\n6. Compare current period to prior period: performance movement, cashflow activity, NAV and unfunded movement, valuation changes, portfolio company adds\u002Fexits, concentration changes, and KPI movements.\n7. Separate facts from interpretation. Use reporting data for facts, cite document support when available, and label inferred questions as analyst prompts rather than confirmed issues.\n8. Produce a prioritized meeting brief with key changes, watch items, suggested GP questions, and follow-up requests.\n\n## Chronograph Data Use\n\nWhen the Chronograph MCP is available, use it to retrieve the relevant portfolio, fund, commitment, performance, exposure, and report-derived document context where permissioned. Keep public-facing explanations at the workflow level; do not expose internal schemas, private tool names, field mappings, or retrieval recipes.\n\nSource discipline:\n\n- Cite Chronograph, document, page, period, or user-provided source for quantitative claims whenever available.\n- State currency, units, as-of date, and whether values are GP-reported, Chronograph-derived, user-provided, or estimated.\n- Do not fabricate NAVs, KPIs, performance metrics, holdings, explanations, or manager commentary.\n- If sources disagree, present the discrepancy and ask the GP-facing question that follows from it.\n\n## Review Priorities\n\nUse `references\u002Freport-review-checklist.md` for a fuller checklist when reviewing a package. Anchor the review on the figures the GP reported this period, citing the source document where available, and present net performance as the LP's headline return clearly labeled gross versus net. Prioritize:\n\n- Performance: lead with the GP-reported figures — gross IRR and MOIC, cost, and realized and unrealized value — and their movement versus prior period, citing sources where available. Carry net performance (TVPI, DPI, RVPI, net IRR) as the LP's bottom-line return, labeled gross versus net, and watch the trend from unrealized value toward realized distributions.\n- Cashflows: calls, distributions, recallable amounts, unfunded exposure, and unusual activity. Distinguish realized-cash distributions from those financed by NAV or subscription-line facilities.\n- Valuation: write-ups, write-downs, stale marks, methodology changes (including any shift toward a cost basis), the GP's written valuation policy, and valuation concentration.\n- Portfolio: new investments, exits, major company KPI changes, top holdings, sector\u002Fgeography exposure, and single-name concentration.\n- Reporting quality: missing explanations, inconsistent values, stale dates, changed definitions, or unexplained metric movement.\n- Meeting readiness: three to eight prioritized questions, required follow-up materials, and open items to track.\n\n## Output\n\nFor a quick answer, use this shape:\n\n- Executive snapshot\n- What changed this period\n- Items to ask the GP\n- Follow-up requests\n- Source notes and assumptions\n\nFor a formal memo or document, use `references\u002Fmeeting-brief-template.md`.\n\nUse `references\u002Fquestion-bank.md` when the user wants more complete question coverage by topic or when the review surfaces a broad set of issues.\n\n## Fallback Behavior\n\nIf Chronograph is unavailable, or the meeting needs a document outside the connected context:\n\n- Ask the LP for the relevant GP reporting package or materials — for example the quarterly report, schedule of investments, capital account statement, or prior meeting notes.\n- If only partial data is available, produce a partial brief and list the missing inputs needed for a complete meeting prep.\n- If the user provides PDFs, workbooks, or pasted text, extract only what is supported by the material and cite the source artifact.\n\n## Guardrails\n\n- Treat the output as draft analyst work product for LP meeting preparation.\n- Do not provide investment, legal, tax, audit, or valuation advice.\n- Do not imply that a missing GP explanation is misconduct; frame gaps as questions or follow-up requests.\n- Do not infer manager intent or portfolio company facts from metric movement alone.\n- Avoid overprecision. Round appropriately and disclose incomplete source coverage.\n",{"data":37,"body":38},{"name":4,"description":6},{"type":39,"children":40},"root",[41,49,61,68,73,78,84,129,135,140,145,169,175,189,222,228,233,261,274,286,292,297,315,321],{"type":42,"tag":43,"props":44,"children":45},"element","h1",{"id":4},[46],{"type":47,"value":48},"text","Chronograph GP Meeting Prep",{"type":42,"tag":50,"props":51,"children":52},"p",{},[53,59],{"type":42,"tag":54,"props":55,"children":56},"strong",{},[57],{"type":47,"value":58},"Requirements:",{"type":47,"value":60}," A connected Chronograph MCP server. These workflows are designed for permissioned Chronograph users to connect to their private investment data.",{"type":42,"tag":62,"props":63,"children":65},"h2",{"id":64},"overview",[66],{"type":47,"value":67},"Overview",{"type":42,"tag":50,"props":69,"children":70},{},[71],{"type":47,"value":72},"Prepare an LP for a meeting with a GP by reviewing fund reporting, surfacing what changed, identifying diligence questions, and producing a concise meeting brief. The brief exists to sharpen a forward decision — a re-up, a secondary sale, or an LPAC vote — so prioritize what bears on those. Use Chronograph as the source of truth where connected and permissioned; otherwise work from user-provided reporting materials.",{"type":42,"tag":50,"props":74,"children":75},{},[76],{"type":47,"value":77},"Default to a chat brief. Create a document, workbook, or deck only when the user asks for an artifact.",{"type":42,"tag":62,"props":79,"children":81},{"id":80},"workflow",[82],{"type":47,"value":83},"Workflow",{"type":42,"tag":85,"props":86,"children":87},"ol",{},[88,94,99,104,109,114,119,124],{"type":42,"tag":89,"props":90,"children":91},"li",{},[92],{"type":47,"value":93},"Clarify scope only when needed: GP, fund, reporting period, meeting type, as-of date, currency, units, output format, and whether the user wants a quick brief or a formal prep document.",{"type":42,"tag":89,"props":95,"children":96},{},[97],{"type":47,"value":98},"Resolve the relevant fund, manager, commitment, reporting period, and LP perspective from Chronograph where available. If Chronograph is unavailable, ask for the GP reporting package or a pasted\u002Fuploaded summary.",{"type":42,"tag":89,"props":100,"children":101},{},[102],{"type":47,"value":103},"Gather the fund baseline, anchoring first on the figures the GP reported this period and citing the source document where available: gross performance, cost, realized and unrealized value, current valuation, portfolio holdings, prior-period values, and fund attributes. Carry net performance — NAV, calls, distributions, TVPI\u002FDPI\u002FRVPI, and net IRR — as the LP's headline return, clearly labeled gross versus net and dated.",{"type":42,"tag":89,"props":105,"children":106},{},[107],{"type":47,"value":108},"Review document-backed reporting content. When Chronograph document semantic search is available, use it as a primary step to find the story behind the numbers: what drove calls and distributions, how the GP describes its marks, and the commentary on portfolio company KPIs.",{"type":42,"tag":89,"props":110,"children":111},{},[112],{"type":47,"value":113},"If a document the meeting needs isn't in the connected context, ask the LP to provide it. Do not infer narrative, management explanations, or meeting context from structured data alone.",{"type":42,"tag":89,"props":115,"children":116},{},[117],{"type":47,"value":118},"Compare current period to prior period: performance movement, cashflow activity, NAV and unfunded movement, valuation changes, portfolio company adds\u002Fexits, concentration changes, and KPI movements.",{"type":42,"tag":89,"props":120,"children":121},{},[122],{"type":47,"value":123},"Separate facts from interpretation. Use reporting data for facts, cite document support when available, and label inferred questions as analyst prompts rather than confirmed issues.",{"type":42,"tag":89,"props":125,"children":126},{},[127],{"type":47,"value":128},"Produce a prioritized meeting brief with key changes, watch items, suggested GP questions, and follow-up requests.",{"type":42,"tag":62,"props":130,"children":132},{"id":131},"chronograph-data-use",[133],{"type":47,"value":134},"Chronograph Data Use",{"type":42,"tag":50,"props":136,"children":137},{},[138],{"type":47,"value":139},"When the Chronograph MCP is available, use it to retrieve the relevant portfolio, fund, commitment, performance, exposure, and report-derived document context where permissioned. Keep public-facing explanations at the workflow level; do not expose internal schemas, private tool names, field mappings, or retrieval recipes.",{"type":42,"tag":50,"props":141,"children":142},{},[143],{"type":47,"value":144},"Source discipline:",{"type":42,"tag":146,"props":147,"children":148},"ul",{},[149,154,159,164],{"type":42,"tag":89,"props":150,"children":151},{},[152],{"type":47,"value":153},"Cite Chronograph, document, page, period, or user-provided source for quantitative claims whenever available.",{"type":42,"tag":89,"props":155,"children":156},{},[157],{"type":47,"value":158},"State currency, units, as-of date, and whether values are GP-reported, Chronograph-derived, user-provided, or estimated.",{"type":42,"tag":89,"props":160,"children":161},{},[162],{"type":47,"value":163},"Do not fabricate NAVs, KPIs, performance metrics, holdings, explanations, or manager commentary.",{"type":42,"tag":89,"props":165,"children":166},{},[167],{"type":47,"value":168},"If sources disagree, present the discrepancy and ask the GP-facing question that follows from it.",{"type":42,"tag":62,"props":170,"children":172},{"id":171},"review-priorities",[173],{"type":47,"value":174},"Review Priorities",{"type":42,"tag":50,"props":176,"children":177},{},[178,180,187],{"type":47,"value":179},"Use ",{"type":42,"tag":181,"props":182,"children":184},"code",{"className":183},[],[185],{"type":47,"value":186},"references\u002Freport-review-checklist.md",{"type":47,"value":188}," for a fuller checklist when reviewing a package. Anchor the review on the figures the GP reported this period, citing the source document where available, and present net performance as the LP's headline return clearly labeled gross versus net. Prioritize:",{"type":42,"tag":146,"props":190,"children":191},{},[192,197,202,207,212,217],{"type":42,"tag":89,"props":193,"children":194},{},[195],{"type":47,"value":196},"Performance: lead with the GP-reported figures — gross IRR and MOIC, cost, and realized and unrealized value — and their movement versus prior period, citing sources where available. Carry net performance (TVPI, DPI, RVPI, net IRR) as the LP's bottom-line return, labeled gross versus net, and watch the trend from unrealized value toward realized distributions.",{"type":42,"tag":89,"props":198,"children":199},{},[200],{"type":47,"value":201},"Cashflows: calls, distributions, recallable amounts, unfunded exposure, and unusual activity. Distinguish realized-cash distributions from those financed by NAV or subscription-line facilities.",{"type":42,"tag":89,"props":203,"children":204},{},[205],{"type":47,"value":206},"Valuation: write-ups, write-downs, stale marks, methodology changes (including any shift toward a cost basis), the GP's written valuation policy, and valuation concentration.",{"type":42,"tag":89,"props":208,"children":209},{},[210],{"type":47,"value":211},"Portfolio: new investments, exits, major company KPI changes, top holdings, sector\u002Fgeography exposure, and single-name concentration.",{"type":42,"tag":89,"props":213,"children":214},{},[215],{"type":47,"value":216},"Reporting quality: missing explanations, inconsistent values, stale dates, changed definitions, or unexplained metric movement.",{"type":42,"tag":89,"props":218,"children":219},{},[220],{"type":47,"value":221},"Meeting readiness: three to eight prioritized questions, required follow-up materials, and open items to track.",{"type":42,"tag":62,"props":223,"children":225},{"id":224},"output",[226],{"type":47,"value":227},"Output",{"type":42,"tag":50,"props":229,"children":230},{},[231],{"type":47,"value":232},"For a quick answer, use this shape:",{"type":42,"tag":146,"props":234,"children":235},{},[236,241,246,251,256],{"type":42,"tag":89,"props":237,"children":238},{},[239],{"type":47,"value":240},"Executive snapshot",{"type":42,"tag":89,"props":242,"children":243},{},[244],{"type":47,"value":245},"What changed this period",{"type":42,"tag":89,"props":247,"children":248},{},[249],{"type":47,"value":250},"Items to ask the GP",{"type":42,"tag":89,"props":252,"children":253},{},[254],{"type":47,"value":255},"Follow-up requests",{"type":42,"tag":89,"props":257,"children":258},{},[259],{"type":47,"value":260},"Source notes and assumptions",{"type":42,"tag":50,"props":262,"children":263},{},[264,266,272],{"type":47,"value":265},"For a formal memo or document, use ",{"type":42,"tag":181,"props":267,"children":269},{"className":268},[],[270],{"type":47,"value":271},"references\u002Fmeeting-brief-template.md",{"type":47,"value":273},".",{"type":42,"tag":50,"props":275,"children":276},{},[277,278,284],{"type":47,"value":179},{"type":42,"tag":181,"props":279,"children":281},{"className":280},[],[282],{"type":47,"value":283},"references\u002Fquestion-bank.md",{"type":47,"value":285}," when the user wants more complete question coverage by topic or when the review surfaces a broad set of issues.",{"type":42,"tag":62,"props":287,"children":289},{"id":288},"fallback-behavior",[290],{"type":47,"value":291},"Fallback Behavior",{"type":42,"tag":50,"props":293,"children":294},{},[295],{"type":47,"value":296},"If Chronograph is unavailable, or the meeting needs a document outside the connected context:",{"type":42,"tag":146,"props":298,"children":299},{},[300,305,310],{"type":42,"tag":89,"props":301,"children":302},{},[303],{"type":47,"value":304},"Ask the LP for the relevant GP reporting package or materials — for example the quarterly report, schedule of investments, capital account statement, or prior meeting notes.",{"type":42,"tag":89,"props":306,"children":307},{},[308],{"type":47,"value":309},"If only partial data is available, produce a partial brief and list the missing inputs needed for a complete meeting prep.",{"type":42,"tag":89,"props":311,"children":312},{},[313],{"type":47,"value":314},"If the user provides PDFs, workbooks, or pasted text, extract only what is supported by the material and cite the source artifact.",{"type":42,"tag":62,"props":316,"children":318},{"id":317},"guardrails",[319],{"type":47,"value":320},"Guardrails",{"type":42,"tag":146,"props":322,"children":323},{},[324,329,334,339,344],{"type":42,"tag":89,"props":325,"children":326},{},[327],{"type":47,"value":328},"Treat the output as draft analyst work product for LP meeting preparation.",{"type":42,"tag":89,"props":330,"children":331},{},[332],{"type":47,"value":333},"Do not provide investment, legal, tax, audit, or valuation advice.",{"type":42,"tag":89,"props":335,"children":336},{},[337],{"type":47,"value":338},"Do not imply that a missing GP explanation is misconduct; frame gaps as questions or follow-up requests.",{"type":42,"tag":89,"props":340,"children":341},{},[342],{"type":47,"value":343},"Do not infer manager intent or portfolio company facts from metric movement alone.",{"type":42,"tag":89,"props":345,"children":346},{},[347],{"type":47,"value":348},"Avoid overprecision. Round appropriately and disclose incomplete source coverage.",{"items":350,"total":472},[351,370,386,398,418,440,460],{"slug":352,"name":352,"fn":353,"description":354,"org":355,"tags":356,"stars":25,"repoUrl":26,"updatedAt":369},"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},[357,360,363,366],{"name":358,"slug":359,"type":15},"Accessibility","accessibility",{"name":361,"slug":362,"type":15},"Charts","charts",{"name":364,"slug":365,"type":15},"Data Visualization","data-visualization",{"name":367,"slug":368,"type":15},"Design","design","2026-06-30T19:00:57.102",{"slug":371,"name":371,"fn":372,"description":373,"org":374,"tags":375,"stars":25,"repoUrl":26,"updatedAt":385},"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},[376,379,382],{"name":377,"slug":378,"type":15},"Agents","agents",{"name":380,"slug":381,"type":15},"Browser Automation","browser-automation",{"name":383,"slug":384,"type":15},"Testing","testing","2026-04-06T18:41:03.44016",{"slug":387,"name":387,"fn":388,"description":389,"org":390,"tags":391,"stars":25,"repoUrl":26,"updatedAt":397},"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},[392,393,396],{"name":380,"slug":381,"type":15},{"name":394,"slug":395,"type":15},"Local Development","local-development",{"name":383,"slug":384,"type":15},"2026-04-06T18:41:17.526867",{"slug":399,"name":399,"fn":400,"description":401,"org":402,"tags":403,"stars":25,"repoUrl":26,"updatedAt":417},"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},[404,405,408,411,414],{"name":377,"slug":378,"type":15},{"name":406,"slug":407,"type":15},"Cloudflare Workers","cloudflare-workers",{"name":409,"slug":410,"type":15},"SDK","sdk",{"name":412,"slug":413,"type":15},"Serverless","serverless",{"name":415,"slug":416,"type":15},"WebSockets","websockets","2026-04-06T18:39:51.717063",{"slug":419,"name":419,"fn":420,"description":421,"org":422,"tags":423,"stars":25,"repoUrl":26,"updatedAt":439},"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},[424,427,430,433,436],{"name":425,"slug":426,"type":15},"Frontend","frontend",{"name":428,"slug":429,"type":15},"React","react",{"name":431,"slug":432,"type":15},"shadcn\u002Fui","shadcn-ui",{"name":434,"slug":435,"type":15},"UI Components","ui-components",{"name":437,"slug":438,"type":15},"Vercel","vercel","2026-04-06T18:40:59.619419",{"slug":441,"name":441,"fn":442,"description":443,"org":444,"tags":445,"stars":25,"repoUrl":26,"updatedAt":459},"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},[446,449,452,455,458],{"name":447,"slug":448,"type":15},"AI Infrastructure","ai-infrastructure",{"name":450,"slug":451,"type":15},"Cost Optimization","cost-optimization",{"name":453,"slug":454,"type":15},"LLM","llm",{"name":456,"slug":457,"type":15},"Performance","performance",{"name":437,"slug":438,"type":15},"2026-04-06T18:40:44.377464",{"slug":461,"name":461,"fn":462,"description":463,"org":464,"tags":465,"stars":25,"repoUrl":26,"updatedAt":471},"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},[466,467,470],{"name":450,"slug":451,"type":15},{"name":468,"slug":469,"type":15},"Database","database",{"name":453,"slug":454,"type":15},"2026-04-06T18:41:08.513425",600,{"items":474,"total":671},[475,496,519,536,552,569,588,600,614,628,640,655],{"slug":476,"name":476,"fn":477,"description":478,"org":479,"tags":480,"stars":493,"repoUrl":494,"updatedAt":495},"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},[481,484,487,490],{"name":482,"slug":483,"type":15},"Documents","documents",{"name":485,"slug":486,"type":15},"Healthcare","healthcare",{"name":488,"slug":489,"type":15},"Insurance","insurance",{"name":491,"slug":492,"type":15},"Regulatory Compliance","regulatory-compliance",28169,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fopenai-agents-python","2026-04-16T05:11:39.180399",{"slug":497,"name":497,"fn":498,"description":499,"org":500,"tags":501,"stars":516,"repoUrl":517,"updatedAt":518},"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},[502,505,507,510,513],{"name":503,"slug":504,"type":15},".NET","dotnet",{"name":506,"slug":497,"type":15},"ASP.NET Core",{"name":508,"slug":509,"type":15},"Blazor","blazor",{"name":511,"slug":512,"type":15},"C#","csharp",{"name":514,"slug":515,"type":15},"Web Development","web-development",23787,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fskills","2026-04-12T05:07:02.819491",{"slug":520,"name":520,"fn":521,"description":522,"org":523,"tags":524,"stars":516,"repoUrl":517,"updatedAt":535},"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},[525,528,531,534],{"name":526,"slug":527,"type":15},"Apps SDK","apps-sdk",{"name":529,"slug":530,"type":15},"ChatGPT","chatgpt",{"name":532,"slug":533,"type":15},"MCP","mcp",{"name":9,"slug":8,"type":15},"2026-04-12T05:07:05.468097",{"slug":537,"name":537,"fn":538,"description":539,"org":540,"tags":541,"stars":516,"repoUrl":517,"updatedAt":551},"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},[542,545,548],{"name":543,"slug":544,"type":15},"API Development","api-development",{"name":546,"slug":547,"type":15},"CLI","cli",{"name":549,"slug":550,"type":15},"Codex","codex","2026-04-12T05:07:04.132762",{"slug":553,"name":553,"fn":554,"description":555,"org":556,"tags":557,"stars":516,"repoUrl":517,"updatedAt":568},"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},[558,561,564,565],{"name":559,"slug":560,"type":15},"Cloudflare","cloudflare",{"name":562,"slug":563,"type":15},"Cloudflare Pages","cloudflare-pages",{"name":406,"slug":407,"type":15},{"name":566,"slug":567,"type":15},"Deployment","deployment","2026-04-12T05:07:14.275118",{"slug":570,"name":570,"fn":571,"description":572,"org":573,"tags":574,"stars":516,"repoUrl":517,"updatedAt":587},"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},[575,578,581,584],{"name":576,"slug":577,"type":15},"Productivity","productivity",{"name":579,"slug":580,"type":15},"Project Management","project-management",{"name":582,"slug":583,"type":15},"Strategy","strategy",{"name":585,"slug":586,"type":15},"Task Management","task-management","2026-05-23T06:17:16.870838",{"slug":589,"name":589,"fn":590,"description":591,"org":592,"tags":593,"stars":516,"repoUrl":517,"updatedAt":599},"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},[594,595,597,598],{"name":367,"slug":368,"type":15},{"name":596,"slug":589,"type":15},"Figma",{"name":425,"slug":426,"type":15},{"name":532,"slug":533,"type":15},"2026-04-12T05:06:47.939943",{"slug":601,"name":601,"fn":602,"description":603,"org":604,"tags":605,"stars":516,"repoUrl":517,"updatedAt":613},"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},[606,607,610,611,612],{"name":367,"slug":368,"type":15},{"name":608,"slug":609,"type":15},"Design System","design-system",{"name":596,"slug":589,"type":15},{"name":425,"slug":426,"type":15},{"name":434,"slug":435,"type":15},"2026-05-10T05:59:52.971881",{"slug":615,"name":615,"fn":616,"description":617,"org":618,"tags":619,"stars":516,"repoUrl":517,"updatedAt":627},"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},[620,621,622,625,626],{"name":367,"slug":368,"type":15},{"name":608,"slug":609,"type":15},{"name":623,"slug":624,"type":15},"Documentation","documentation",{"name":596,"slug":589,"type":15},{"name":425,"slug":426,"type":15},"2026-05-16T06:07:47.821474",{"slug":629,"name":629,"fn":630,"description":631,"org":632,"tags":633,"stars":516,"repoUrl":517,"updatedAt":639},"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},[634,635,636,637,638],{"name":367,"slug":368,"type":15},{"name":596,"slug":589,"type":15},{"name":425,"slug":426,"type":15},{"name":434,"slug":435,"type":15},{"name":514,"slug":515,"type":15},"2026-05-16T06:07:40.583615",{"slug":641,"name":641,"fn":642,"description":643,"org":644,"tags":645,"stars":516,"repoUrl":517,"updatedAt":654},"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},[646,649,650,653],{"name":647,"slug":648,"type":15},"Animation","animation",{"name":549,"slug":550,"type":15},{"name":651,"slug":652,"type":15},"Creative","creative",{"name":367,"slug":368,"type":15},"2026-05-02T05:31:48.48485",{"slug":656,"name":656,"fn":657,"description":658,"org":659,"tags":660,"stars":516,"repoUrl":517,"updatedAt":670},"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},[661,662,663,666,669],{"name":651,"slug":652,"type":15},{"name":367,"slug":368,"type":15},{"name":664,"slug":665,"type":15},"Image Generation","image-generation",{"name":667,"slug":668,"type":15},"Images","images",{"name":9,"slug":8,"type":15},"2026-05-15T06:23:24.312127",675]