[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-openai-market-sizing":3,"mdc-y8yno4-key":36,"related-repo-openai-market-sizing":435,"related-org-openai-market-sizing":544},{"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},"market-sizing","estimate market and opportunity size","Estimate market, segment, or opportunity size with transparent assumptions and uncertainty. Use for TAM\u002FSAM\u002FSOM, sizing scenarios, or comparing the scale of possible opportunities.",{"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},"Research","research","tag",{"name":17,"slug":18,"type":15},"Finance","finance",{"name":20,"slug":21,"type":15},"Strategy","strategy",{"name":23,"slug":24,"type":15},"Analytics","analytics",427,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Frole-specific-plugins","2026-07-01T07:54:51.968523",null,65,[],{"repoUrl":26,"stars":25,"forks":29,"topics":32,"description":33},[],"Role-specific Codex plugin templates","https:\u002F\u002Fgithub.com\u002Fopenai\u002Frole-specific-plugins\u002Ftree\u002FHEAD\u002Fplugins\u002Fdata-analytics\u002Fskills\u002Fmarket-sizing","---\nname: market-sizing\ndescription: \"Estimate market, segment, or opportunity size with transparent assumptions and uncertainty. Use for TAM\u002FSAM\u002FSOM, sizing scenarios, or comparing the scale of possible opportunities.\"\n---\n\n## Related Skills\n\nUse $visualize-data when the sizing result needs a chart or figure.\n\nUse $build-report to package the final estimate, assumptions, sensitivity, caveats, and source context whenever this skill is selected, unless the user explicitly requests an inline, chat-only, brief\u002Fno-artifact answer, asks not to create a report\u002Ffile\u002Fartifact, or selects another primary artifact.\n\n# Market Sizing\n\nUse this skill to produce a defensible estimate of a market or opportunity from connected context, public sources, transparent assumptions, and auditable calculations. The job is to define the market, choose a sound sizing method, distinguish evidence from assumptions, test sensitivity, and state what would most improve confidence.\n\n## Skill Configuration\n\n### Source Discovery And Verification\n\nUse the relevant semantic layer as a starting map, not a boundary.\n\n1. **Explore all possible sources.** Search every connected or provided source that could contain task-relevant data or change the interpretation. Within each structured-data source, run fresh catalog or metadata discovery for relevant schemas, datasets, tables, views, models, and metrics. Known sources, tables, dashboards, and semantic mappings are starting points, not stopping points.\n2. **Compare duplicates and conflicts.** When sources overlap or disagree, compare ownership, freshness, definition, grain, coverage, and directness. Use the best authoritative source, or combine complementary sources when needed. Note material conflicts, explain why the selected source or sources control the answer, and verify selected data through live reads before concluding.\n\n### Source Access Guardrail\n\nBefore querying sources, building artifacts, or drawing conclusions, determine whether the answer requires a specific source of truth.\n\nIf a required source is unavailable, stop that path. Tell the user what source is needed, ask them to make it available or provide a reviewed fallback, and do not treat weaker substitutes as equivalent.\n\nIf the missing source is only optional enrichment, continue with the strongest available evidence and label the gap when it materially affects the answer.\n\nClarify with the user when a missing input would materially change the estimate or recommendation. Otherwise make a reasonable assumption, state it, and proceed.\n\n## Workflow\n\n### 1. Frame The Market Or Opportunity\n\nDefine the market or opportunity boundary before estimating:\n\n- What is being sized, for example a product category, workflow, problem, use case, or category of activity.\n- Where and when it applies, for example geography, segment scope, time horizon, or market maturity.\n- Who or what counts as part of the market, for example the relevant population, unit of demand, transaction type, or included activity.\n- How the opportunity is measured, for example spend, revenue, volume, value created, or another unit that fits the question.\n- What kind of sizing answer the user needs, for example TAM\u002FSAM\u002FSOM, market entry, expansion upside, spend pool, revenue pool, population count, or unit volume.\n\n### 2. Choose A Starting Sizing Approach And Inputs\n\nPick the simplest sound sizing approach for the question, then sketch the calculation chain and the major inputs the estimate will depend on.\n\nA top-down model works when reliable aggregate market data exists; a bottom-up model works when the market can be built from observable units and assumptions; a value-based model works when the estimate should start from the value created rather than a published market total. Use a mixed approach only when cross-checking would materially improve confidence. If more than one approach fits, briefly explain which one you trust most and why.\n\nExpect the first approach to change if source checks show that another model would be more defensible.\n\n### 3. Gather Sources For The Inputs\n\nChoose sources based on the inputs the estimate depends on most.\n\nStart with user-named sources when provided. Then use the strongest available evidence for each major input from the starting approach. Use `~~structured_data` when an input should come from the user's data warehouse or another structured data source. Use context lanes such as `~~company_docs`, `~~team_communication`, or `~~dashboards_or_bi` when an input needs business meaning, source-of-truth guidance, or assumptions that are not captured in structured data alone. When an input depends on the outside market, use public sources for benchmarks, population estimates, comparable markets, or proxy assumptions.\n\nUse $gather-business-context to resolve context lanes when the right source of truth, business meaning, or assumption set is unclear.\n\nIf the strongest source is unavailable or thin, continue with a transparent proxy assumption only when the estimate is still useful. Label the gap and explain how it affects confidence.\n\n### 4. Separate Facts From Assumptions\n\nKeep sourced facts, inferred estimates, and judgment calls distinct in the model. When exact data is unavailable, use a defensible proxy, explain why it is reasonable, and note the confidence level. Ground assumptions in evidence about how the market actually behaves, what can realistically change, and what determines the size of the opportunity.\n\n### 5. Build The Model\n\nMake the model easy to inspect and adjust.\n\nThe model should make these elements easy to audit or revise:\n\n- market definition and measurement unit\n- assumptions and source context\n- calculation chain and derived values\n- base case, material ranges, and sensitivity logic\n- validation priorities\n\nFor each major input, make the source path visible: structured data, context lane, public source, user-provided input, or proxy assumption.\n\nKeep derived values traceable to formulas or code rather than hardcoded outputs.\n\nUse $jupyter-notebooks when code is needed for source harmonization, calculations, sensitivity analysis, or reusable modeling logic. Keep formulas, inputs, intermediate calculations, and sensitivity logic inspectable.\n\nUse the `$Spreadsheets` skill when the user requests a spreadsheet, workbook, or Google Sheets deliverable, or when a market-sizing model would materially benefit from editable assumptions, sensitivity tables, charts, or polished workbook formatting.\n\n### 6. Test Sensitivity\n\nIdentify the assumptions that move the estimate most.\n\nShow how the estimate changes when those assumptions move up or down. Prefer simple, decision-useful sensitivity analysis over exhaustive scenario sprawl.\n\nUse ranges when uncertainty is material. Do not hide uncertainty behind a single point estimate when the inputs are thin.\n\n### 7. State The Estimate And Validation Priorities\n\nEnd by handing the estimate, method, key assumptions, uncertainty, and next validation priorities to $build-report unless the user explicitly waives report creation or selects another primary artifact. This handoff is mandatory when no explicit human waiver was given; do not infer a waiver because the user asked for an estimate or did not use the word \"report\". This workflow owns the sizing model and conclusion; $build-report owns the reader-facing structure, visuals, evidence placement, and delivery surface.\n\nBefore handoff, make the market-sizing conclusion explicit:\n\n- market definition and measurement unit\n- estimate or range\n- method and calculation chain\n- key assumptions and source support\n- main uncertainty drivers and sensitivity takeaways\n- validation priorities and practical interpretation for the user's decision\n\nIf source coverage is thin, say which major inputs rely on proxy assumptions and what source would most improve them.\n\nUse $validate-data when methodology, calculations, assumptions, caveats, or source support need review before sharing.\n\nDo not render charts directly from this skill. If a sensitivity, scenario, funnel, or market-breakdown visual would clarify the estimate, pass that visual intent and supporting evidence to $build-report so $visualize-data owns chart selection and QA.\n",{"data":37,"body":38},{"name":4,"description":6},{"type":39,"children":40},"root",[41,50,56,61,67,72,78,85,90,116,122,127,132,137,142,148,154,159,188,194,199,204,209,215,220,258,263,268,274,279,285,290,295,323,328,333,338,351,357,362,367,372,378,383,388,420,425,430],{"type":42,"tag":43,"props":44,"children":46},"element","h2",{"id":45},"related-skills",[47],{"type":48,"value":49},"text","Related Skills",{"type":42,"tag":51,"props":52,"children":53},"p",{},[54],{"type":48,"value":55},"Use $visualize-data when the sizing result needs a chart or figure.",{"type":42,"tag":51,"props":57,"children":58},{},[59],{"type":48,"value":60},"Use $build-report to package the final estimate, assumptions, sensitivity, caveats, and source context whenever this skill is selected, unless the user explicitly requests an inline, chat-only, brief\u002Fno-artifact answer, asks not to create a report\u002Ffile\u002Fartifact, or selects another primary artifact.",{"type":42,"tag":62,"props":63,"children":64},"h1",{"id":4},[65],{"type":48,"value":66},"Market Sizing",{"type":42,"tag":51,"props":68,"children":69},{},[70],{"type":48,"value":71},"Use this skill to produce a defensible estimate of a market or opportunity from connected context, public sources, transparent assumptions, and auditable calculations. The job is to define the market, choose a sound sizing method, distinguish evidence from assumptions, test sensitivity, and state what would most improve confidence.",{"type":42,"tag":43,"props":73,"children":75},{"id":74},"skill-configuration",[76],{"type":48,"value":77},"Skill Configuration",{"type":42,"tag":79,"props":80,"children":82},"h3",{"id":81},"source-discovery-and-verification",[83],{"type":48,"value":84},"Source Discovery And Verification",{"type":42,"tag":51,"props":86,"children":87},{},[88],{"type":48,"value":89},"Use the relevant semantic layer as a starting map, not a boundary.",{"type":42,"tag":91,"props":92,"children":93},"ol",{},[94,106],{"type":42,"tag":95,"props":96,"children":97},"li",{},[98,104],{"type":42,"tag":99,"props":100,"children":101},"strong",{},[102],{"type":48,"value":103},"Explore all possible sources.",{"type":48,"value":105}," Search every connected or provided source that could contain task-relevant data or change the interpretation. Within each structured-data source, run fresh catalog or metadata discovery for relevant schemas, datasets, tables, views, models, and metrics. Known sources, tables, dashboards, and semantic mappings are starting points, not stopping points.",{"type":42,"tag":95,"props":107,"children":108},{},[109,114],{"type":42,"tag":99,"props":110,"children":111},{},[112],{"type":48,"value":113},"Compare duplicates and conflicts.",{"type":48,"value":115}," When sources overlap or disagree, compare ownership, freshness, definition, grain, coverage, and directness. Use the best authoritative source, or combine complementary sources when needed. Note material conflicts, explain why the selected source or sources control the answer, and verify selected data through live reads before concluding.",{"type":42,"tag":79,"props":117,"children":119},{"id":118},"source-access-guardrail",[120],{"type":48,"value":121},"Source Access Guardrail",{"type":42,"tag":51,"props":123,"children":124},{},[125],{"type":48,"value":126},"Before querying sources, building artifacts, or drawing conclusions, determine whether the answer requires a specific source of truth.",{"type":42,"tag":51,"props":128,"children":129},{},[130],{"type":48,"value":131},"If a required source is unavailable, stop that path. Tell the user what source is needed, ask them to make it available or provide a reviewed fallback, and do not treat weaker substitutes as equivalent.",{"type":42,"tag":51,"props":133,"children":134},{},[135],{"type":48,"value":136},"If the missing source is only optional enrichment, continue with the strongest available evidence and label the gap when it materially affects the answer.",{"type":42,"tag":51,"props":138,"children":139},{},[140],{"type":48,"value":141},"Clarify with the user when a missing input would materially change the estimate or recommendation. Otherwise make a reasonable assumption, state it, and proceed.",{"type":42,"tag":43,"props":143,"children":145},{"id":144},"workflow",[146],{"type":48,"value":147},"Workflow",{"type":42,"tag":79,"props":149,"children":151},{"id":150},"_1-frame-the-market-or-opportunity",[152],{"type":48,"value":153},"1. Frame The Market Or Opportunity",{"type":42,"tag":51,"props":155,"children":156},{},[157],{"type":48,"value":158},"Define the market or opportunity boundary before estimating:",{"type":42,"tag":160,"props":161,"children":162},"ul",{},[163,168,173,178,183],{"type":42,"tag":95,"props":164,"children":165},{},[166],{"type":48,"value":167},"What is being sized, for example a product category, workflow, problem, use case, or category of activity.",{"type":42,"tag":95,"props":169,"children":170},{},[171],{"type":48,"value":172},"Where and when it applies, for example geography, segment scope, time horizon, or market maturity.",{"type":42,"tag":95,"props":174,"children":175},{},[176],{"type":48,"value":177},"Who or what counts as part of the market, for example the relevant population, unit of demand, transaction type, or included activity.",{"type":42,"tag":95,"props":179,"children":180},{},[181],{"type":48,"value":182},"How the opportunity is measured, for example spend, revenue, volume, value created, or another unit that fits the question.",{"type":42,"tag":95,"props":184,"children":185},{},[186],{"type":48,"value":187},"What kind of sizing answer the user needs, for example TAM\u002FSAM\u002FSOM, market entry, expansion upside, spend pool, revenue pool, population count, or unit volume.",{"type":42,"tag":79,"props":189,"children":191},{"id":190},"_2-choose-a-starting-sizing-approach-and-inputs",[192],{"type":48,"value":193},"2. Choose A Starting Sizing Approach And Inputs",{"type":42,"tag":51,"props":195,"children":196},{},[197],{"type":48,"value":198},"Pick the simplest sound sizing approach for the question, then sketch the calculation chain and the major inputs the estimate will depend on.",{"type":42,"tag":51,"props":200,"children":201},{},[202],{"type":48,"value":203},"A top-down model works when reliable aggregate market data exists; a bottom-up model works when the market can be built from observable units and assumptions; a value-based model works when the estimate should start from the value created rather than a published market total. Use a mixed approach only when cross-checking would materially improve confidence. If more than one approach fits, briefly explain which one you trust most and why.",{"type":42,"tag":51,"props":205,"children":206},{},[207],{"type":48,"value":208},"Expect the first approach to change if source checks show that another model would be more defensible.",{"type":42,"tag":79,"props":210,"children":212},{"id":211},"_3-gather-sources-for-the-inputs",[213],{"type":48,"value":214},"3. Gather Sources For The Inputs",{"type":42,"tag":51,"props":216,"children":217},{},[218],{"type":48,"value":219},"Choose sources based on the inputs the estimate depends on most.",{"type":42,"tag":51,"props":221,"children":222},{},[223,225,232,234,240,242,248,250,256],{"type":48,"value":224},"Start with user-named sources when provided. Then use the strongest available evidence for each major input from the starting approach. Use ",{"type":42,"tag":226,"props":227,"children":229},"code",{"className":228},[],[230],{"type":48,"value":231},"~~structured_data",{"type":48,"value":233}," when an input should come from the user's data warehouse or another structured data source. Use context lanes such as ",{"type":42,"tag":226,"props":235,"children":237},{"className":236},[],[238],{"type":48,"value":239},"~~company_docs",{"type":48,"value":241},", ",{"type":42,"tag":226,"props":243,"children":245},{"className":244},[],[246],{"type":48,"value":247},"~~team_communication",{"type":48,"value":249},", or ",{"type":42,"tag":226,"props":251,"children":253},{"className":252},[],[254],{"type":48,"value":255},"~~dashboards_or_bi",{"type":48,"value":257}," when an input needs business meaning, source-of-truth guidance, or assumptions that are not captured in structured data alone. When an input depends on the outside market, use public sources for benchmarks, population estimates, comparable markets, or proxy assumptions.",{"type":42,"tag":51,"props":259,"children":260},{},[261],{"type":48,"value":262},"Use $gather-business-context to resolve context lanes when the right source of truth, business meaning, or assumption set is unclear.",{"type":42,"tag":51,"props":264,"children":265},{},[266],{"type":48,"value":267},"If the strongest source is unavailable or thin, continue with a transparent proxy assumption only when the estimate is still useful. Label the gap and explain how it affects confidence.",{"type":42,"tag":79,"props":269,"children":271},{"id":270},"_4-separate-facts-from-assumptions",[272],{"type":48,"value":273},"4. Separate Facts From Assumptions",{"type":42,"tag":51,"props":275,"children":276},{},[277],{"type":48,"value":278},"Keep sourced facts, inferred estimates, and judgment calls distinct in the model. When exact data is unavailable, use a defensible proxy, explain why it is reasonable, and note the confidence level. Ground assumptions in evidence about how the market actually behaves, what can realistically change, and what determines the size of the opportunity.",{"type":42,"tag":79,"props":280,"children":282},{"id":281},"_5-build-the-model",[283],{"type":48,"value":284},"5. Build The Model",{"type":42,"tag":51,"props":286,"children":287},{},[288],{"type":48,"value":289},"Make the model easy to inspect and adjust.",{"type":42,"tag":51,"props":291,"children":292},{},[293],{"type":48,"value":294},"The model should make these elements easy to audit or revise:",{"type":42,"tag":160,"props":296,"children":297},{},[298,303,308,313,318],{"type":42,"tag":95,"props":299,"children":300},{},[301],{"type":48,"value":302},"market definition and measurement unit",{"type":42,"tag":95,"props":304,"children":305},{},[306],{"type":48,"value":307},"assumptions and source context",{"type":42,"tag":95,"props":309,"children":310},{},[311],{"type":48,"value":312},"calculation chain and derived values",{"type":42,"tag":95,"props":314,"children":315},{},[316],{"type":48,"value":317},"base case, material ranges, and sensitivity logic",{"type":42,"tag":95,"props":319,"children":320},{},[321],{"type":48,"value":322},"validation priorities",{"type":42,"tag":51,"props":324,"children":325},{},[326],{"type":48,"value":327},"For each major input, make the source path visible: structured data, context lane, public source, user-provided input, or proxy assumption.",{"type":42,"tag":51,"props":329,"children":330},{},[331],{"type":48,"value":332},"Keep derived values traceable to formulas or code rather than hardcoded outputs.",{"type":42,"tag":51,"props":334,"children":335},{},[336],{"type":48,"value":337},"Use $jupyter-notebooks when code is needed for source harmonization, calculations, sensitivity analysis, or reusable modeling logic. Keep formulas, inputs, intermediate calculations, and sensitivity logic inspectable.",{"type":42,"tag":51,"props":339,"children":340},{},[341,343,349],{"type":48,"value":342},"Use the ",{"type":42,"tag":226,"props":344,"children":346},{"className":345},[],[347],{"type":48,"value":348},"$Spreadsheets",{"type":48,"value":350}," skill when the user requests a spreadsheet, workbook, or Google Sheets deliverable, or when a market-sizing model would materially benefit from editable assumptions, sensitivity tables, charts, or polished workbook formatting.",{"type":42,"tag":79,"props":352,"children":354},{"id":353},"_6-test-sensitivity",[355],{"type":48,"value":356},"6. Test Sensitivity",{"type":42,"tag":51,"props":358,"children":359},{},[360],{"type":48,"value":361},"Identify the assumptions that move the estimate most.",{"type":42,"tag":51,"props":363,"children":364},{},[365],{"type":48,"value":366},"Show how the estimate changes when those assumptions move up or down. Prefer simple, decision-useful sensitivity analysis over exhaustive scenario sprawl.",{"type":42,"tag":51,"props":368,"children":369},{},[370],{"type":48,"value":371},"Use ranges when uncertainty is material. Do not hide uncertainty behind a single point estimate when the inputs are thin.",{"type":42,"tag":79,"props":373,"children":375},{"id":374},"_7-state-the-estimate-and-validation-priorities",[376],{"type":48,"value":377},"7. State The Estimate And Validation Priorities",{"type":42,"tag":51,"props":379,"children":380},{},[381],{"type":48,"value":382},"End by handing the estimate, method, key assumptions, uncertainty, and next validation priorities to $build-report unless the user explicitly waives report creation or selects another primary artifact. This handoff is mandatory when no explicit human waiver was given; do not infer a waiver because the user asked for an estimate or did not use the word \"report\". This workflow owns the sizing model and conclusion; $build-report owns the reader-facing structure, visuals, evidence placement, and delivery surface.",{"type":42,"tag":51,"props":384,"children":385},{},[386],{"type":48,"value":387},"Before handoff, make the market-sizing conclusion explicit:",{"type":42,"tag":160,"props":389,"children":390},{},[391,395,400,405,410,415],{"type":42,"tag":95,"props":392,"children":393},{},[394],{"type":48,"value":302},{"type":42,"tag":95,"props":396,"children":397},{},[398],{"type":48,"value":399},"estimate or range",{"type":42,"tag":95,"props":401,"children":402},{},[403],{"type":48,"value":404},"method and calculation chain",{"type":42,"tag":95,"props":406,"children":407},{},[408],{"type":48,"value":409},"key assumptions and source support",{"type":42,"tag":95,"props":411,"children":412},{},[413],{"type":48,"value":414},"main uncertainty drivers and sensitivity takeaways",{"type":42,"tag":95,"props":416,"children":417},{},[418],{"type":48,"value":419},"validation priorities and practical interpretation for the user's decision",{"type":42,"tag":51,"props":421,"children":422},{},[423],{"type":48,"value":424},"If source coverage is thin, say which major inputs rely on proxy assumptions and what source would most improve them.",{"type":42,"tag":51,"props":426,"children":427},{},[428],{"type":48,"value":429},"Use $validate-data when methodology, calculations, assumptions, caveats, or source support need review before sharing.",{"type":42,"tag":51,"props":431,"children":432},{},[433],{"type":48,"value":434},"Do not render charts directly from this skill. If a sensitivity, scenario, funnel, or market-breakdown visual would clarify the estimate, pass that visual intent and supporting evidence to $build-report so $visualize-data owns chart selection and QA.",{"items":436,"total":543},[437,452,468,481,497,513,528],{"slug":438,"name":438,"fn":439,"description":440,"org":441,"tags":442,"stars":25,"repoUrl":26,"updatedAt":451},"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},[443,444,447,448],{"name":23,"slug":24,"type":15},{"name":445,"slug":446,"type":15},"CRM","crm",{"name":13,"slug":14,"type":15},{"name":449,"slug":450,"type":15},"Sales","sales","2026-07-01T07:54:11.79288",{"slug":453,"name":453,"fn":454,"description":455,"org":456,"tags":457,"stars":25,"repoUrl":26,"updatedAt":467},"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},[458,461,464],{"name":459,"slug":460,"type":15},"Audit","audit",{"name":462,"slug":463,"type":15},"Data Engineering","data-engineering",{"name":465,"slug":466,"type":15},"Data Quality","data-quality","2026-07-01T07:55:01.146961",{"slug":469,"name":469,"fn":470,"description":471,"org":472,"tags":473,"stars":25,"repoUrl":26,"updatedAt":480},"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},[474,477],{"name":475,"slug":476,"type":15},"Communications","communications",{"name":478,"slug":479,"type":15},"Productivity","productivity","2026-07-14T05:43:36.096323",{"slug":482,"name":482,"fn":483,"description":484,"org":485,"tags":486,"stars":25,"repoUrl":26,"updatedAt":496},"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},[487,489,492,495],{"name":488,"slug":482,"type":15},"Apollo",{"name":490,"slug":491,"type":15},"Lead Enrichment","lead-enrichment",{"name":493,"slug":494,"type":15},"Prospecting","prospecting",{"name":449,"slug":450,"type":15},"2026-07-14T05:43:34.800076",{"slug":460,"name":460,"fn":498,"description":499,"org":500,"tags":501,"stars":25,"repoUrl":26,"updatedAt":512},"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},[502,503,506,509],{"name":459,"slug":460,"type":15},{"name":504,"slug":505,"type":15},"Design","design",{"name":507,"slug":508,"type":15},"Product Management","product-management",{"name":510,"slug":511,"type":15},"UX Design","ux-design","2026-07-01T07:54:30.613428",{"slug":514,"name":514,"fn":515,"description":516,"org":517,"tags":518,"stars":25,"repoUrl":26,"updatedAt":527},"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},[519,522,523,526],{"name":520,"slug":521,"type":15},"Content Creation","content-creation",{"name":17,"slug":18,"type":15},{"name":524,"slug":525,"type":15},"Financial Modeling","financial-modeling",{"name":449,"slug":450,"type":15},"2026-07-01T07:54:02.779003",{"slug":529,"name":529,"fn":530,"description":531,"org":532,"tags":533,"stars":25,"repoUrl":26,"updatedAt":542},"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},[534,537,540,541],{"name":535,"slug":536,"type":15},"Competitive Intelligence","competitive-intelligence",{"name":538,"slug":539,"type":15},"Marketing","marketing",{"name":13,"slug":14,"type":15},{"name":449,"slug":450,"type":15},"2026-07-01T07:54:13.073252",43,{"items":545,"total":744},[546,567,590,607,623,642,657,671,687,701,713,728],{"slug":547,"name":547,"fn":548,"description":549,"org":550,"tags":551,"stars":564,"repoUrl":565,"updatedAt":566},"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},[552,555,558,561],{"name":553,"slug":554,"type":15},"Documents","documents",{"name":556,"slug":557,"type":15},"Healthcare","healthcare",{"name":559,"slug":560,"type":15},"Insurance","insurance",{"name":562,"slug":563,"type":15},"Regulatory Compliance","regulatory-compliance",28169,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fopenai-agents-python","2026-04-16T05:11:39.180399",{"slug":568,"name":568,"fn":569,"description":570,"org":571,"tags":572,"stars":587,"repoUrl":588,"updatedAt":589},"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},[573,576,578,581,584],{"name":574,"slug":575,"type":15},".NET","dotnet",{"name":577,"slug":568,"type":15},"ASP.NET Core",{"name":579,"slug":580,"type":15},"Blazor","blazor",{"name":582,"slug":583,"type":15},"C#","csharp",{"name":585,"slug":586,"type":15},"Web Development","web-development",23787,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fskills","2026-04-12T05:07:02.819491",{"slug":591,"name":591,"fn":592,"description":593,"org":594,"tags":595,"stars":587,"repoUrl":588,"updatedAt":606},"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},[596,599,602,605],{"name":597,"slug":598,"type":15},"Apps SDK","apps-sdk",{"name":600,"slug":601,"type":15},"ChatGPT","chatgpt",{"name":603,"slug":604,"type":15},"MCP","mcp",{"name":9,"slug":8,"type":15},"2026-04-12T05:07:05.468097",{"slug":608,"name":608,"fn":609,"description":610,"org":611,"tags":612,"stars":587,"repoUrl":588,"updatedAt":622},"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},[613,616,619],{"name":614,"slug":615,"type":15},"API Development","api-development",{"name":617,"slug":618,"type":15},"CLI","cli",{"name":620,"slug":621,"type":15},"Codex","codex","2026-04-12T05:07:04.132762",{"slug":624,"name":624,"fn":625,"description":626,"org":627,"tags":628,"stars":587,"repoUrl":588,"updatedAt":641},"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},[629,632,635,638],{"name":630,"slug":631,"type":15},"Cloudflare","cloudflare",{"name":633,"slug":634,"type":15},"Cloudflare Pages","cloudflare-pages",{"name":636,"slug":637,"type":15},"Cloudflare Workers","cloudflare-workers",{"name":639,"slug":640,"type":15},"Deployment","deployment","2026-04-12T05:07:14.275118",{"slug":643,"name":643,"fn":644,"description":645,"org":646,"tags":647,"stars":587,"repoUrl":588,"updatedAt":656},"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},[648,649,652,653],{"name":478,"slug":479,"type":15},{"name":650,"slug":651,"type":15},"Project Management","project-management",{"name":20,"slug":21,"type":15},{"name":654,"slug":655,"type":15},"Task Management","task-management","2026-05-23T06:17:16.870838",{"slug":658,"name":658,"fn":659,"description":660,"org":661,"tags":662,"stars":587,"repoUrl":588,"updatedAt":670},"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},[663,664,666,669],{"name":504,"slug":505,"type":15},{"name":665,"slug":658,"type":15},"Figma",{"name":667,"slug":668,"type":15},"Frontend","frontend",{"name":603,"slug":604,"type":15},"2026-04-12T05:06:47.939943",{"slug":672,"name":672,"fn":673,"description":674,"org":675,"tags":676,"stars":587,"repoUrl":588,"updatedAt":686},"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},[677,678,681,682,683],{"name":504,"slug":505,"type":15},{"name":679,"slug":680,"type":15},"Design System","design-system",{"name":665,"slug":658,"type":15},{"name":667,"slug":668,"type":15},{"name":684,"slug":685,"type":15},"UI Components","ui-components","2026-05-10T05:59:52.971881",{"slug":688,"name":688,"fn":689,"description":690,"org":691,"tags":692,"stars":587,"repoUrl":588,"updatedAt":700},"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},[693,694,695,698,699],{"name":504,"slug":505,"type":15},{"name":679,"slug":680,"type":15},{"name":696,"slug":697,"type":15},"Documentation","documentation",{"name":665,"slug":658,"type":15},{"name":667,"slug":668,"type":15},"2026-05-16T06:07:47.821474",{"slug":702,"name":702,"fn":703,"description":704,"org":705,"tags":706,"stars":587,"repoUrl":588,"updatedAt":712},"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},[707,708,709,710,711],{"name":504,"slug":505,"type":15},{"name":665,"slug":658,"type":15},{"name":667,"slug":668,"type":15},{"name":684,"slug":685,"type":15},{"name":585,"slug":586,"type":15},"2026-05-16T06:07:40.583615",{"slug":714,"name":714,"fn":715,"description":716,"org":717,"tags":718,"stars":587,"repoUrl":588,"updatedAt":727},"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},[719,722,723,726],{"name":720,"slug":721,"type":15},"Animation","animation",{"name":620,"slug":621,"type":15},{"name":724,"slug":725,"type":15},"Creative","creative",{"name":504,"slug":505,"type":15},"2026-05-02T05:31:48.48485",{"slug":729,"name":729,"fn":730,"description":731,"org":732,"tags":733,"stars":587,"repoUrl":588,"updatedAt":743},"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},[734,735,736,739,742],{"name":724,"slug":725,"type":15},{"name":504,"slug":505,"type":15},{"name":737,"slug":738,"type":15},"Image Generation","image-generation",{"name":740,"slug":741,"type":15},"Images","images",{"name":9,"slug":8,"type":15},"2026-05-15T06:23:24.312127",675]