[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-openai-gather-business-context":3,"mdc-1lle0h-key":33,"related-repo-openai-gather-business-context":231,"related-org-openai-gather-business-context":344},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":22,"repoUrl":23,"updatedAt":24,"license":25,"forks":26,"topics":27,"repo":28,"sourceUrl":31,"mdContent":32},"gather-business-context","gather business context for analysis","Gather business context from connected or provided sources so downstream analysis starts with the right framing. Use when an analytical question depends on missing context, such as what a metric means, what changed recently, or which sources should be checked. If the same prompt asks for diagnosis, recommendation, or a deliverable, gather context first and continue to the focused skill.",{"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],{"name":13,"slug":14,"type":15},"Research","research","tag",{"name":17,"slug":18,"type":15},"Operations","operations",{"name":20,"slug":21,"type":15},"Data Analysis","data-analysis",427,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Frole-specific-plugins","2026-07-01T07:54:58.546082",null,65,[],{"repoUrl":23,"stars":22,"forks":26,"topics":29,"description":30},[],"Role-specific Codex plugin templates","https:\u002F\u002Fgithub.com\u002Fopenai\u002Frole-specific-plugins\u002Ftree\u002FHEAD\u002Fplugins\u002Fdata-analytics\u002Fskills\u002Fgather-business-context","---\nname: gather-business-context\ndescription: \"Gather business context from connected or provided sources so downstream analysis starts with the right framing. Use when an analytical question depends on missing context, such as what a metric means, what changed recently, or which sources should be checked. If the same prompt asks for diagnosis, recommendation, or a deliverable, gather context first and continue to the focused skill.\"\n---\n\n## Boundary\n\nUse this skill to gather framing context, not to complete the downstream analysis.\n\nIf the same request also asks for a diagnosis, recommendation, dashboard, report, or other analytical deliverable, return only the context needed for that next step and continue with the appropriate focused skill, such as $metric-diagnostics, $product-business-analysis, $build-dashboard, or $build-report.\n\n# Gather Business Context\n\nUse this skill to collect the business context needed to understand an analytical question before doing deeper work. Focus on what the topic is, why it matters, what changed or is being decided, who or what source is closest to the work, and which definitions or artifacts should frame the analysis. This is a retrieval and extraction skill: gather enough context to set up the next step, not a final report, root-cause analysis, or broad background scan. Skip it when the prompt already provides the needed context or the task is fully self-contained.\n\n## Workflow\n\n### 1. Identify The Retrieval Target\n\nEstablish the analytical topic that needs context and why it matters for the next step. Capture the boundary needed to search and interpret sources, such as the relevant product area, audience, time period, or decision. If the timeframe is missing, use the narrowest reasonable window implied by the task and label it as an assumption.\n\n### 2. Build Search Anchors\n\nSearch with concrete identifiers rather than broad topic guesses. Start with the names the user provided or the sources surfaced, then expand with adjacent terms that help recall, such as aliases, owners, teams, dates, source names, related entities, or entities found in earlier results.\n\nStart broad enough to avoid missing relevant context. If too much comes back and a quick scan suggests the results are mostly unrelated, combine anchors to narrow retrieval, for example a metric plus a dashboard name, a feature plus a launch window, or a customer plus the relevant workflow. If a likely source comes back thin, revise the anchors before treating the source as missing.\n\n### 3. Search From Discovery Points Toward Authoritative Artifacts\n\n1. **Explore all possible sources.** Search every enabled or provided source family that could contain useful context or task-relevant data. Within each structured-data source, run fresh catalog or metadata discovery for relevant schemas, datasets, tables, views, models, and metrics. User-named sources, known tables, dashboards, and semantic-layer anchors are starting points, not stopping points.\n2. **Compare duplicates and conflicts.** When sources overlap or disagree, compare authority, freshness, definition, scope, and directness. Prefer artifacts closest to what was decided, defined, implemented, or measured; follow linked evidence when useful. Note material conflicts and explain which source or combination should guide downstream analysis.\n\n### 4. Extract Only Decision-Shaping Context\n\nTreat business context as a fixed extraction target, not an open-ended summary. Capture the facts that will shape the downstream analysis: the topic's business meaning, why it matters now, how it is defined or measured, where to verify it, what recently changed, and what uncertainty should travel with the analysis. Examples can include a metric definition, current rollout state, dashboard link, owner note, source conflict, or stated next step.\n\nKeep the context note focused on details that help frame the next analysis. Skip broad background, adjacent history, or long source excerpts unless they add useful context.\n\n### 5. Keep Source Notes Compact And Attributable\n\nFor each useful source, record enough attribution for the downstream work to be checked later: when the source applies, what kind of source it is, what factual context it established, and any important caveat or conflict. Distinguish source facts from inference and do not imply source review, stakeholder views, metric certainty, or confidence beyond what was actually established.\n\n### 6. Reconcile Conflicts Explicitly\n\nWhen sources disagree in a way that could change the downstream framing, preserve the disagreement instead of smoothing it over. Prefer the newest explicit decision artifact over older plans, owner-written docs over third-party summaries, and implementation artifacts over aspirational plans when the question is what is live, shipped, logged, or queryable now. Treat an informal source as stronger than a canonical artifact only when it clearly records a later decision or owner confirmation.\n\nIf disagreement remains, present both views, label the conflict, and state what source or owner would resolve it. If context is stale or incomplete, say what is missing and where to look next.\n\n### 7. Stop Once The Framing Is Sound\n\nStop gathering context when the downstream task can be framed well enough to proceed and the likely enabled or provided source families have been checked, ruled out as unavailable, or identified as too thin. Before stopping, make sure the next step has a clear enough understanding of the topic, why it matters, where the important definitions came from, what recent context applies, and what gaps remain.\n\nContinue searching when a relevant enabled or provided source is likely to add useful context. If an expected source was not found, name that as a gap rather than implying it does not exist.\n\n### 8. Return A Lightweight Context Note When Useful\n\nPrefer a focused context note over a full report or raw retrieval dump. Include enough context for the next analysis to proceed without redoing the search: a short summary, the relevant context, important definitions or source links, uncertainty or caveats, and citations. Keep it readable, but do not compress away details that explain the framing or source quality.\n\nIf the user asked only for quick orientation, shorten the structure while preserving citations, conflicts, and missing canonical artifacts.\n\n## Standards\n\nJudge sources by what they can actually establish. Informal discussion can be useful for discovery and recent context, but durable artifacts are usually stronger evidence for definitions, decisions, status, and measured results once found. Prefer sources close to the work, recent enough to reflect current reality, and explicit about what they establish. Surface missing source-of-truth artifacts as context gaps.\n\nKeep important claims attributable. Treat a source as useful only when it clarifies how the downstream task should be framed or interpreted; sources that merely mention the topic are incidental. Preserve enough evidence to check the work later, and label interpretation, assumptions, conflicts, and uncertainty when support is thin, stale, indirect, or conflicting.\n\nPreserve disagreements that could change the framing. Prefer owner-authored or decision-adjacent material and evidence of what is current over secondhand summaries or speculation. Do not infer consensus from silence. Say what source or owner would resolve an important conflict.\n",{"data":34,"body":35},{"name":4,"description":6},{"type":36,"children":37},"root",[38,47,53,58,64,69,75,82,87,93,98,103,109,135,141,146,151,157,162,168,173,178,184,189,194,200,205,210,216,221,226],{"type":39,"tag":40,"props":41,"children":43},"element","h2",{"id":42},"boundary",[44],{"type":45,"value":46},"text","Boundary",{"type":39,"tag":48,"props":49,"children":50},"p",{},[51],{"type":45,"value":52},"Use this skill to gather framing context, not to complete the downstream analysis.",{"type":39,"tag":48,"props":54,"children":55},{},[56],{"type":45,"value":57},"If the same request also asks for a diagnosis, recommendation, dashboard, report, or other analytical deliverable, return only the context needed for that next step and continue with the appropriate focused skill, such as $metric-diagnostics, $product-business-analysis, $build-dashboard, or $build-report.",{"type":39,"tag":59,"props":60,"children":61},"h1",{"id":4},[62],{"type":45,"value":63},"Gather Business Context",{"type":39,"tag":48,"props":65,"children":66},{},[67],{"type":45,"value":68},"Use this skill to collect the business context needed to understand an analytical question before doing deeper work. Focus on what the topic is, why it matters, what changed or is being decided, who or what source is closest to the work, and which definitions or artifacts should frame the analysis. This is a retrieval and extraction skill: gather enough context to set up the next step, not a final report, root-cause analysis, or broad background scan. Skip it when the prompt already provides the needed context or the task is fully self-contained.",{"type":39,"tag":40,"props":70,"children":72},{"id":71},"workflow",[73],{"type":45,"value":74},"Workflow",{"type":39,"tag":76,"props":77,"children":79},"h3",{"id":78},"_1-identify-the-retrieval-target",[80],{"type":45,"value":81},"1. Identify The Retrieval Target",{"type":39,"tag":48,"props":83,"children":84},{},[85],{"type":45,"value":86},"Establish the analytical topic that needs context and why it matters for the next step. Capture the boundary needed to search and interpret sources, such as the relevant product area, audience, time period, or decision. If the timeframe is missing, use the narrowest reasonable window implied by the task and label it as an assumption.",{"type":39,"tag":76,"props":88,"children":90},{"id":89},"_2-build-search-anchors",[91],{"type":45,"value":92},"2. Build Search Anchors",{"type":39,"tag":48,"props":94,"children":95},{},[96],{"type":45,"value":97},"Search with concrete identifiers rather than broad topic guesses. Start with the names the user provided or the sources surfaced, then expand with adjacent terms that help recall, such as aliases, owners, teams, dates, source names, related entities, or entities found in earlier results.",{"type":39,"tag":48,"props":99,"children":100},{},[101],{"type":45,"value":102},"Start broad enough to avoid missing relevant context. If too much comes back and a quick scan suggests the results are mostly unrelated, combine anchors to narrow retrieval, for example a metric plus a dashboard name, a feature plus a launch window, or a customer plus the relevant workflow. If a likely source comes back thin, revise the anchors before treating the source as missing.",{"type":39,"tag":76,"props":104,"children":106},{"id":105},"_3-search-from-discovery-points-toward-authoritative-artifacts",[107],{"type":45,"value":108},"3. Search From Discovery Points Toward Authoritative Artifacts",{"type":39,"tag":110,"props":111,"children":112},"ol",{},[113,125],{"type":39,"tag":114,"props":115,"children":116},"li",{},[117,123],{"type":39,"tag":118,"props":119,"children":120},"strong",{},[121],{"type":45,"value":122},"Explore all possible sources.",{"type":45,"value":124}," Search every enabled or provided source family that could contain useful context or task-relevant data. Within each structured-data source, run fresh catalog or metadata discovery for relevant schemas, datasets, tables, views, models, and metrics. User-named sources, known tables, dashboards, and semantic-layer anchors are starting points, not stopping points.",{"type":39,"tag":114,"props":126,"children":127},{},[128,133],{"type":39,"tag":118,"props":129,"children":130},{},[131],{"type":45,"value":132},"Compare duplicates and conflicts.",{"type":45,"value":134}," When sources overlap or disagree, compare authority, freshness, definition, scope, and directness. Prefer artifacts closest to what was decided, defined, implemented, or measured; follow linked evidence when useful. Note material conflicts and explain which source or combination should guide downstream analysis.",{"type":39,"tag":76,"props":136,"children":138},{"id":137},"_4-extract-only-decision-shaping-context",[139],{"type":45,"value":140},"4. Extract Only Decision-Shaping Context",{"type":39,"tag":48,"props":142,"children":143},{},[144],{"type":45,"value":145},"Treat business context as a fixed extraction target, not an open-ended summary. Capture the facts that will shape the downstream analysis: the topic's business meaning, why it matters now, how it is defined or measured, where to verify it, what recently changed, and what uncertainty should travel with the analysis. Examples can include a metric definition, current rollout state, dashboard link, owner note, source conflict, or stated next step.",{"type":39,"tag":48,"props":147,"children":148},{},[149],{"type":45,"value":150},"Keep the context note focused on details that help frame the next analysis. Skip broad background, adjacent history, or long source excerpts unless they add useful context.",{"type":39,"tag":76,"props":152,"children":154},{"id":153},"_5-keep-source-notes-compact-and-attributable",[155],{"type":45,"value":156},"5. Keep Source Notes Compact And Attributable",{"type":39,"tag":48,"props":158,"children":159},{},[160],{"type":45,"value":161},"For each useful source, record enough attribution for the downstream work to be checked later: when the source applies, what kind of source it is, what factual context it established, and any important caveat or conflict. Distinguish source facts from inference and do not imply source review, stakeholder views, metric certainty, or confidence beyond what was actually established.",{"type":39,"tag":76,"props":163,"children":165},{"id":164},"_6-reconcile-conflicts-explicitly",[166],{"type":45,"value":167},"6. Reconcile Conflicts Explicitly",{"type":39,"tag":48,"props":169,"children":170},{},[171],{"type":45,"value":172},"When sources disagree in a way that could change the downstream framing, preserve the disagreement instead of smoothing it over. Prefer the newest explicit decision artifact over older plans, owner-written docs over third-party summaries, and implementation artifacts over aspirational plans when the question is what is live, shipped, logged, or queryable now. Treat an informal source as stronger than a canonical artifact only when it clearly records a later decision or owner confirmation.",{"type":39,"tag":48,"props":174,"children":175},{},[176],{"type":45,"value":177},"If disagreement remains, present both views, label the conflict, and state what source or owner would resolve it. If context is stale or incomplete, say what is missing and where to look next.",{"type":39,"tag":76,"props":179,"children":181},{"id":180},"_7-stop-once-the-framing-is-sound",[182],{"type":45,"value":183},"7. Stop Once The Framing Is Sound",{"type":39,"tag":48,"props":185,"children":186},{},[187],{"type":45,"value":188},"Stop gathering context when the downstream task can be framed well enough to proceed and the likely enabled or provided source families have been checked, ruled out as unavailable, or identified as too thin. Before stopping, make sure the next step has a clear enough understanding of the topic, why it matters, where the important definitions came from, what recent context applies, and what gaps remain.",{"type":39,"tag":48,"props":190,"children":191},{},[192],{"type":45,"value":193},"Continue searching when a relevant enabled or provided source is likely to add useful context. If an expected source was not found, name that as a gap rather than implying it does not exist.",{"type":39,"tag":76,"props":195,"children":197},{"id":196},"_8-return-a-lightweight-context-note-when-useful",[198],{"type":45,"value":199},"8. Return A Lightweight Context Note When Useful",{"type":39,"tag":48,"props":201,"children":202},{},[203],{"type":45,"value":204},"Prefer a focused context note over a full report or raw retrieval dump. Include enough context for the next analysis to proceed without redoing the search: a short summary, the relevant context, important definitions or source links, uncertainty or caveats, and citations. Keep it readable, but do not compress away details that explain the framing or source quality.",{"type":39,"tag":48,"props":206,"children":207},{},[208],{"type":45,"value":209},"If the user asked only for quick orientation, shorten the structure while preserving citations, conflicts, and missing canonical artifacts.",{"type":39,"tag":40,"props":211,"children":213},{"id":212},"standards",[214],{"type":45,"value":215},"Standards",{"type":39,"tag":48,"props":217,"children":218},{},[219],{"type":45,"value":220},"Judge sources by what they can actually establish. Informal discussion can be useful for discovery and recent context, but durable artifacts are usually stronger evidence for definitions, decisions, status, and measured results once found. Prefer sources close to the work, recent enough to reflect current reality, and explicit about what they establish. Surface missing source-of-truth artifacts as context gaps.",{"type":39,"tag":48,"props":222,"children":223},{},[224],{"type":45,"value":225},"Keep important claims attributable. Treat a source as useful only when it clarifies how the downstream task should be framed or interpreted; sources that merely mention the topic are incidental. Preserve enough evidence to check the work later, and label interpretation, assumptions, conflicts, and uncertainty when support is thin, stale, indirect, or conflicting.",{"type":39,"tag":48,"props":227,"children":228},{},[229],{"type":45,"value":230},"Preserve disagreements that could change the framing. Prefer owner-authored or decision-adjacent material and evidence of what is current over secondhand summaries or speculation. Do not infer consensus from silence. Say what source or owner would resolve an important conflict.",{"items":232,"total":343},[233,250,266,279,295,311,328],{"slug":234,"name":234,"fn":235,"description":236,"org":237,"tags":238,"stars":22,"repoUrl":23,"updatedAt":249},"analyze-account-signals","analyze account signals for sales intelligence","Use when the user wants to know what changed with one account, monitor an owner portfolio or watchlist, or rank accounts needing attention from recent evidence. Produce an evidence-backed account brief or bounded watchlist summary with recommended actions.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[239,242,245,246],{"name":240,"slug":241,"type":15},"Analytics","analytics",{"name":243,"slug":244,"type":15},"CRM","crm",{"name":13,"slug":14,"type":15},{"name":247,"slug":248,"type":15},"Sales","sales","2026-07-01T07:54:11.79288",{"slug":251,"name":251,"fn":252,"description":253,"org":254,"tags":255,"stars":22,"repoUrl":23,"updatedAt":265},"analyze-data-quality","assess data quality for analysis","Assess whether structured data, query results, dashboards, or analytical evidence are trustworthy enough to use. Use when the task is to check data quality, reconcile conflicting sources or metric definitions, or decide whether evidence is safe to cite.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[256,259,262],{"name":257,"slug":258,"type":15},"Audit","audit",{"name":260,"slug":261,"type":15},"Data Engineering","data-engineering",{"name":263,"slug":264,"type":15},"Data Quality","data-quality","2026-07-01T07:55:01.146961",{"slug":267,"name":267,"fn":268,"description":269,"org":270,"tags":271,"stars":22,"repoUrl":23,"updatedAt":278},"answers-ask-user-input","request missing context from users","Use when a small amount of missing context would materially improve the answer and tappable options plus a free-text answer can gather it efficiently.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[272,275],{"name":273,"slug":274,"type":15},"Communications","communications",{"name":276,"slug":277,"type":15},"Productivity","productivity","2026-07-14T05:43:36.096323",{"slug":280,"name":280,"fn":281,"description":282,"org":283,"tags":284,"stars":22,"repoUrl":23,"updatedAt":294},"apollo","prospect and enrich leads with Apollo","Use only when a focused Sales workflow has selected a present and connected Apollo connector, or the user explicitly asks for Apollo prospecting, enrichment, Company Details, records, sequences, or outbound planning. Apply Apollo v2-specific behavior only after verifying app version 2.0.0 or later.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[285,287,290,293],{"name":286,"slug":280,"type":15},"Apollo",{"name":288,"slug":289,"type":15},"Lead Enrichment","lead-enrichment",{"name":291,"slug":292,"type":15},"Prospecting","prospecting",{"name":247,"slug":248,"type":15},"2026-07-14T05:43:34.800076",{"slug":258,"name":258,"fn":296,"description":297,"org":298,"tags":299,"stars":22,"repoUrl":23,"updatedAt":310},"audit product flows and user journeys","Audit or critique a product flow, journey, workflow, funnel, onboarding path, checkout path, settings path, screen, or multi-step product experience by capturing screenshots first, then reporting UX, design, and accessibility findings inline from that evidence. Use Figma only when the user explicitly asks for a board. Use when the user asks to audit, review, critique, inspect, assess, analyze, evaluate, or give feedback on a product experience.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[300,301,304,307],{"name":257,"slug":258,"type":15},{"name":302,"slug":303,"type":15},"Design","design",{"name":305,"slug":306,"type":15},"Product Management","product-management",{"name":308,"slug":309,"type":15},"UX Design","ux-design","2026-07-01T07:54:30.613428",{"slug":312,"name":312,"fn":313,"description":314,"org":315,"tags":316,"stars":22,"repoUrl":23,"updatedAt":327},"build-business-case","build customer-led business cases and ROI","Review commercial proposals and build customer-led business cases, ROI or value models, pricing or investment rationales, executive summaries, and customer-ready value stories tied to a customer, workflow, initiative, or decision.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[317,320,323,326],{"name":318,"slug":319,"type":15},"Content Creation","content-creation",{"name":321,"slug":322,"type":15},"Finance","finance",{"name":324,"slug":325,"type":15},"Financial Modeling","financial-modeling",{"name":247,"slug":248,"type":15},"2026-07-01T07:54:02.779003",{"slug":329,"name":329,"fn":330,"description":331,"org":332,"tags":333,"stars":22,"repoUrl":23,"updatedAt":342},"build-competitive-brief","build competitive briefs and battlecards","Use when the user wants a competitor or vendor comparison, market-landscape analysis, battlecard, objection package, positioning brief, or account-specific competitive view. Produce an evidence-backed comparison, guidance, and brief, using supplied materials, connected research, and public evidence when appropriate.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[334,337,340,341],{"name":335,"slug":336,"type":15},"Competitive Intelligence","competitive-intelligence",{"name":338,"slug":339,"type":15},"Marketing","marketing",{"name":13,"slug":14,"type":15},{"name":247,"slug":248,"type":15},"2026-07-01T07:54:13.073252",43,{"items":345,"total":546},[346,367,390,407,423,442,459,473,489,503,515,530],{"slug":347,"name":347,"fn":348,"description":349,"org":350,"tags":351,"stars":364,"repoUrl":365,"updatedAt":366},"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},[352,355,358,361],{"name":353,"slug":354,"type":15},"Documents","documents",{"name":356,"slug":357,"type":15},"Healthcare","healthcare",{"name":359,"slug":360,"type":15},"Insurance","insurance",{"name":362,"slug":363,"type":15},"Regulatory Compliance","regulatory-compliance",28169,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fopenai-agents-python","2026-04-16T05:11:39.180399",{"slug":368,"name":368,"fn":369,"description":370,"org":371,"tags":372,"stars":387,"repoUrl":388,"updatedAt":389},"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},[373,376,378,381,384],{"name":374,"slug":375,"type":15},".NET","dotnet",{"name":377,"slug":368,"type":15},"ASP.NET Core",{"name":379,"slug":380,"type":15},"Blazor","blazor",{"name":382,"slug":383,"type":15},"C#","csharp",{"name":385,"slug":386,"type":15},"Web Development","web-development",23787,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fskills","2026-04-12T05:07:02.819491",{"slug":391,"name":391,"fn":392,"description":393,"org":394,"tags":395,"stars":387,"repoUrl":388,"updatedAt":406},"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},[396,399,402,405],{"name":397,"slug":398,"type":15},"Apps SDK","apps-sdk",{"name":400,"slug":401,"type":15},"ChatGPT","chatgpt",{"name":403,"slug":404,"type":15},"MCP","mcp",{"name":9,"slug":8,"type":15},"2026-04-12T05:07:05.468097",{"slug":408,"name":408,"fn":409,"description":410,"org":411,"tags":412,"stars":387,"repoUrl":388,"updatedAt":422},"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},[413,416,419],{"name":414,"slug":415,"type":15},"API Development","api-development",{"name":417,"slug":418,"type":15},"CLI","cli",{"name":420,"slug":421,"type":15},"Codex","codex","2026-04-12T05:07:04.132762",{"slug":424,"name":424,"fn":425,"description":426,"org":427,"tags":428,"stars":387,"repoUrl":388,"updatedAt":441},"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},[429,432,435,438],{"name":430,"slug":431,"type":15},"Cloudflare","cloudflare",{"name":433,"slug":434,"type":15},"Cloudflare Pages","cloudflare-pages",{"name":436,"slug":437,"type":15},"Cloudflare Workers","cloudflare-workers",{"name":439,"slug":440,"type":15},"Deployment","deployment","2026-04-12T05:07:14.275118",{"slug":443,"name":443,"fn":444,"description":445,"org":446,"tags":447,"stars":387,"repoUrl":388,"updatedAt":458},"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},[448,449,452,455],{"name":276,"slug":277,"type":15},{"name":450,"slug":451,"type":15},"Project Management","project-management",{"name":453,"slug":454,"type":15},"Strategy","strategy",{"name":456,"slug":457,"type":15},"Task Management","task-management","2026-05-23T06:17:16.870838",{"slug":460,"name":460,"fn":461,"description":462,"org":463,"tags":464,"stars":387,"repoUrl":388,"updatedAt":472},"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},[465,466,468,471],{"name":302,"slug":303,"type":15},{"name":467,"slug":460,"type":15},"Figma",{"name":469,"slug":470,"type":15},"Frontend","frontend",{"name":403,"slug":404,"type":15},"2026-04-12T05:06:47.939943",{"slug":474,"name":474,"fn":475,"description":476,"org":477,"tags":478,"stars":387,"repoUrl":388,"updatedAt":488},"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},[479,480,483,484,485],{"name":302,"slug":303,"type":15},{"name":481,"slug":482,"type":15},"Design System","design-system",{"name":467,"slug":460,"type":15},{"name":469,"slug":470,"type":15},{"name":486,"slug":487,"type":15},"UI Components","ui-components","2026-05-10T05:59:52.971881",{"slug":490,"name":490,"fn":491,"description":492,"org":493,"tags":494,"stars":387,"repoUrl":388,"updatedAt":502},"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},[495,496,497,500,501],{"name":302,"slug":303,"type":15},{"name":481,"slug":482,"type":15},{"name":498,"slug":499,"type":15},"Documentation","documentation",{"name":467,"slug":460,"type":15},{"name":469,"slug":470,"type":15},"2026-05-16T06:07:47.821474",{"slug":504,"name":504,"fn":505,"description":506,"org":507,"tags":508,"stars":387,"repoUrl":388,"updatedAt":514},"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},[509,510,511,512,513],{"name":302,"slug":303,"type":15},{"name":467,"slug":460,"type":15},{"name":469,"slug":470,"type":15},{"name":486,"slug":487,"type":15},{"name":385,"slug":386,"type":15},"2026-05-16T06:07:40.583615",{"slug":516,"name":516,"fn":517,"description":518,"org":519,"tags":520,"stars":387,"repoUrl":388,"updatedAt":529},"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},[521,524,525,528],{"name":522,"slug":523,"type":15},"Animation","animation",{"name":420,"slug":421,"type":15},{"name":526,"slug":527,"type":15},"Creative","creative",{"name":302,"slug":303,"type":15},"2026-05-02T05:31:48.48485",{"slug":531,"name":531,"fn":532,"description":533,"org":534,"tags":535,"stars":387,"repoUrl":388,"updatedAt":545},"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},[536,537,538,541,544],{"name":526,"slug":527,"type":15},{"name":302,"slug":303,"type":15},{"name":539,"slug":540,"type":15},"Image Generation","image-generation",{"name":542,"slug":543,"type":15},"Images","images",{"name":9,"slug":8,"type":15},"2026-05-15T06:23:24.312127",675]