[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-openai-product-business-analysis":3,"mdc-92wvid-key":36,"related-repo-openai-product-business-analysis":582,"related-org-openai-product-business-analysis":693},{"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},"product-business-analysis","analyze product and business data","Analyze product or business data to support a decision or recommendation. Use when a decision depends on metric-backed evidence, such as choosing a direction, prioritizing an opportunity, evaluating a change, segmenting users, sizing tradeoffs, or deciding what to do next.",{"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},"KPI","kpi","tag",{"name":17,"slug":18,"type":15},"Data Analysis","data-analysis",{"name":20,"slug":21,"type":15},"Product Management","product-management",{"name":23,"slug":24,"type":15},"Analytics","analytics",427,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Frole-specific-plugins","2026-07-01T07:54:59.851783",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\u002Fproduct-business-analysis","---\nname: product-business-analysis\ndescription: \"Analyze product or business data to support a decision or recommendation. Use when a decision depends on metric-backed evidence, such as choosing a direction, prioritizing an opportunity, evaluating a change, segmenting users, sizing tradeoffs, or deciding what to do next.\"\n---\n\n## Related Skills\n\nUse $metric-diagnostics when the recommendation depends on explaining a metric movement, anomaly, gap, or discrepancy.\n\n# Product And Business Analysis\n\nUse this skill to answer product or business questions with data-backed evidence, context, and a recommendation. Give the audience enough trustworthy evidence, interpretation, and uncertainty framing to choose a practical next action.\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 analytical frame or recommendation. Otherwise make a reasonable assumption, state it, and proceed.\n\n## Workflow\n\n### 1. Start From The Decision\n\nIdentify the decision, audience, and action the analysis should inform before choosing data sources or metrics.\n\nState plainly:\n\n- the question and decision the analysis should inform\n- who will use the answer and what they can act on\n- the scope and comparison that define a useful answer\n- the outcome or behavior that matters for the decision\n- any assumptions needed to proceed\n\nDo not let unclear scope turn into broad exploratory work by default.\n\n### 2. Gather Decision-Relevant Context\n\nRun $gather-business-context before deeper analysis. That skill owns source selection, retrieval, source authority, conflict handling, and compact context notes. Use this workflow to decide how the gathered context changes the analysis and recommendation.\n\nKeep the context pass proportional to the task. For self-contained prompts or cases where the user already provided enough context, the pass can be brief: confirm the decision frame, definitions, source assumptions, and any obvious gaps before moving on. Do not turn mandatory context gathering into a broad background scan.\n\nRelevant context should clarify:\n\n- intent: what the work was meant to accomplish and why\n- definitions: how the work, metric, or source is defined and measured\n- timing: what changed around the analysis period that could affect interpretation\n- constraints: decisions, caveats, or limitations that affect what action is realistic\n\n### 3. Frame The Analysis\n\nTurn the question into a focused analytical framework.\n\nDefine a framework for answering the question with data:\n\n- the specific data questions that would support or change the recommendation\n- the comparisons and dimensions to inspect\n- the unit of analysis that matches the decision\n- the metric definitions and caveats needed to interpret the result\n\nUse the framework to surface plausible hypotheses or interpretations, then turn them into focused data questions. Keep the framework specific enough to avoid broad exploration and support a recommendation.\n\nUse $design-kpis when the success metric, driver metrics, guardrails, or measurement plan need to be defined before the analysis can proceed.\n\nStart by defining what the answer needs to show in plain language. Then choose the data that matches that meaning as closely as possible, including who is counted and what comparison makes the number meaningful. If a field or event captures only part of what the decision cares about, say what it captures and what it leaves out.\n\n### 4. Run Focused Quantitative Analysis\n\nRun enough quantitative analysis to support or reject the framed hypotheses and inform the decision:\n\n- **Follow the framework.** Run the analyses that could change the recommendation first. Track additional data questions that emerge, answer the ones that matter for the decision, and leave lower-impact cuts as follow-up instead of expanding into broad exploration.\n\n- **Use the right comparison.** Interpret results against the relevant baseline, denominator, or comparison point before turning them into a recommendation. For example, do not conclude that one group is the best opportunity just because it has the most total usage. Check whether usage is high because the group is larger, whether the pattern still holds after normalizing by the active base, whether the group is growing or declining, whether the usage reflects the behavior or outcome that matters, and whether business context changes the interpretation.\n\n- **Size the opportunities.** Estimate the magnitude of impact each important opportunity could have. State what is being compared, which metric represents impact, what denominator or population it uses, and whether the data is complete enough to trust. Keep material unknown or unclassified groups visible when they could change the interpretation.\n\n- **Keep quantitative work inspectable.** Use $jupyter-notebooks to record queries and analysis. Use $analyze-data-quality when source freshness, grain, joins, missingness, schema drift, or unexpected distributions could affect trust.\n\n- **Validate before concluding.** Use $validate-data before sharing stakeholder-facing recommendations, high-impact claims, or surprising results. When dashboards and direct queries both exist, reconcile them or explain why they differ.\n\n### 5. Translate Evidence Into Decision Implications\n\nFrame the findings within the broader business context. Do not present quantitative evidence and business context as two unrelated streams.\n\nInterpret the evidence through the decision lenses that best fit the question. Choose lenses that would actually change the recommendation, and skip ones that would add noise or false precision. Common lenses include:\n\n- **Current scale:** Is the opportunity or problem large enough today to matter for the decision?\n- **Momentum:** Is the signal growing, shrinking, accelerating, or newly emerging?\n- **Breadth:** Is the pattern broad-based, or does it only appear in a narrow corner of the business?\n- **Concentration:** Does the conclusion depend on a few large entities, events, or outliers?\n- **Intensity:** Is the behavior deep enough per unit to suggest real need, value, or risk?\n- **Efficiency:** Does the option create better output, margin, conversion, productivity, or quality for the input required?\n- **Addressability:** Can the team realistically act on this option with available product, GTM, operational, policy, or technical levers?\n- **Differentiation:** Does this group or use case require a distinct motion, product experience, support model, or message?\n- **Substitution:** Is there evidence that behavior, spend, time, or workload could shift from another path?\n- **Risk or dependency:** Are there quality, trust, compliance, technical, operational, or data constraints that change the recommendation?\n- **Coverage:** Are unknown, missing, or sparsely tagged records large enough to change the answer?\n\nUse these as thinking tools, not a checklist. Explain why the chosen lenses matter for this decision, and mention omitted cuts only when they would plausibly change the interpretation or help explain the result.\n\nUse the measured opportunities to explain which differences matter for the decision and which ones call for different actions. If the business context shows that the initial sizing misses the actionable part of the opportunity, add the focused sizing cut needed to make the recommendation useful.\n\nIf evidence conflicts, say so directly and explain which interpretation is better supported. Do not smooth over disagreement between sources.\n\n### 6. Hand Off The Recommendation\n\nEnd by handing the decision-ready recommendation to $build-report 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. This handoff is mandatory when no explicit human waiver was given; do not infer a waiver because the user asked a direct question or did not use the word \"report\". This workflow owns the analytical conclusion; $build-report owns the reader-facing structure, visuals, evidence placement, and delivery surface.\n\nBefore handoff, make the recommendation explicit:\n\n- what they should believe or do next\n- why the evidence supports that recommendation\n- which caveats or dependencies matter\n- what follow-up analysis would most improve confidence\n\nIf evidence is incomplete, label the recommendation as provisional and state what would change confidence. Do not overstate the conclusion just to make the answer feel decisive.\n\nUse $validate-data when methodology, calculations, caveats, or the evidentiary support for the conclusion need review before sharing.\n\nPass narrative ingredients to the report surface, not only result tables:\n\n- direct answer and recommendation\n- key evidence and how to interpret it\n- implication for the decision\n- unresolved uncertainty and caveats\n- recommended follow-up\n",{"data":37,"body":38},{"name":4,"description":6},{"type":39,"children":40},"root",[41,50,56,63,68,74,81,86,112,118,123,128,133,138,144,150,155,160,189,194,200,205,210,215,238,244,249,254,277,282,287,292,298,303,356,362,367,372,485,490,495,500,506,511,516,539,544,549,554],{"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 $metric-diagnostics when the recommendation depends on explaining a metric movement, anomaly, gap, or discrepancy.",{"type":42,"tag":57,"props":58,"children":60},"h1",{"id":59},"product-and-business-analysis",[61],{"type":48,"value":62},"Product And Business Analysis",{"type":42,"tag":51,"props":64,"children":65},{},[66],{"type":48,"value":67},"Use this skill to answer product or business questions with data-backed evidence, context, and a recommendation. Give the audience enough trustworthy evidence, interpretation, and uncertainty framing to choose a practical next action.",{"type":42,"tag":43,"props":69,"children":71},{"id":70},"skill-configuration",[72],{"type":48,"value":73},"Skill Configuration",{"type":42,"tag":75,"props":76,"children":78},"h3",{"id":77},"source-discovery-and-verification",[79],{"type":48,"value":80},"Source Discovery And Verification",{"type":42,"tag":51,"props":82,"children":83},{},[84],{"type":48,"value":85},"Use the relevant semantic layer as a starting map, not a boundary.",{"type":42,"tag":87,"props":88,"children":89},"ol",{},[90,102],{"type":42,"tag":91,"props":92,"children":93},"li",{},[94,100],{"type":42,"tag":95,"props":96,"children":97},"strong",{},[98],{"type":48,"value":99},"Explore all possible sources.",{"type":48,"value":101}," 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":91,"props":103,"children":104},{},[105,110],{"type":42,"tag":95,"props":106,"children":107},{},[108],{"type":48,"value":109},"Compare duplicates and conflicts.",{"type":48,"value":111}," 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":75,"props":113,"children":115},{"id":114},"source-access-guardrail",[116],{"type":48,"value":117},"Source Access Guardrail",{"type":42,"tag":51,"props":119,"children":120},{},[121],{"type":48,"value":122},"Before querying sources, building artifacts, or drawing conclusions, determine whether the answer requires a specific source of truth.",{"type":42,"tag":51,"props":124,"children":125},{},[126],{"type":48,"value":127},"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":129,"children":130},{},[131],{"type":48,"value":132},"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":134,"children":135},{},[136],{"type":48,"value":137},"Clarify with the user when a missing input would materially change the analytical frame or recommendation. Otherwise make a reasonable assumption, state it, and proceed.",{"type":42,"tag":43,"props":139,"children":141},{"id":140},"workflow",[142],{"type":48,"value":143},"Workflow",{"type":42,"tag":75,"props":145,"children":147},{"id":146},"_1-start-from-the-decision",[148],{"type":48,"value":149},"1. Start From The Decision",{"type":42,"tag":51,"props":151,"children":152},{},[153],{"type":48,"value":154},"Identify the decision, audience, and action the analysis should inform before choosing data sources or metrics.",{"type":42,"tag":51,"props":156,"children":157},{},[158],{"type":48,"value":159},"State plainly:",{"type":42,"tag":161,"props":162,"children":163},"ul",{},[164,169,174,179,184],{"type":42,"tag":91,"props":165,"children":166},{},[167],{"type":48,"value":168},"the question and decision the analysis should inform",{"type":42,"tag":91,"props":170,"children":171},{},[172],{"type":48,"value":173},"who will use the answer and what they can act on",{"type":42,"tag":91,"props":175,"children":176},{},[177],{"type":48,"value":178},"the scope and comparison that define a useful answer",{"type":42,"tag":91,"props":180,"children":181},{},[182],{"type":48,"value":183},"the outcome or behavior that matters for the decision",{"type":42,"tag":91,"props":185,"children":186},{},[187],{"type":48,"value":188},"any assumptions needed to proceed",{"type":42,"tag":51,"props":190,"children":191},{},[192],{"type":48,"value":193},"Do not let unclear scope turn into broad exploratory work by default.",{"type":42,"tag":75,"props":195,"children":197},{"id":196},"_2-gather-decision-relevant-context",[198],{"type":48,"value":199},"2. Gather Decision-Relevant Context",{"type":42,"tag":51,"props":201,"children":202},{},[203],{"type":48,"value":204},"Run $gather-business-context before deeper analysis. That skill owns source selection, retrieval, source authority, conflict handling, and compact context notes. Use this workflow to decide how the gathered context changes the analysis and recommendation.",{"type":42,"tag":51,"props":206,"children":207},{},[208],{"type":48,"value":209},"Keep the context pass proportional to the task. For self-contained prompts or cases where the user already provided enough context, the pass can be brief: confirm the decision frame, definitions, source assumptions, and any obvious gaps before moving on. Do not turn mandatory context gathering into a broad background scan.",{"type":42,"tag":51,"props":211,"children":212},{},[213],{"type":48,"value":214},"Relevant context should clarify:",{"type":42,"tag":161,"props":216,"children":217},{},[218,223,228,233],{"type":42,"tag":91,"props":219,"children":220},{},[221],{"type":48,"value":222},"intent: what the work was meant to accomplish and why",{"type":42,"tag":91,"props":224,"children":225},{},[226],{"type":48,"value":227},"definitions: how the work, metric, or source is defined and measured",{"type":42,"tag":91,"props":229,"children":230},{},[231],{"type":48,"value":232},"timing: what changed around the analysis period that could affect interpretation",{"type":42,"tag":91,"props":234,"children":235},{},[236],{"type":48,"value":237},"constraints: decisions, caveats, or limitations that affect what action is realistic",{"type":42,"tag":75,"props":239,"children":241},{"id":240},"_3-frame-the-analysis",[242],{"type":48,"value":243},"3. Frame The Analysis",{"type":42,"tag":51,"props":245,"children":246},{},[247],{"type":48,"value":248},"Turn the question into a focused analytical framework.",{"type":42,"tag":51,"props":250,"children":251},{},[252],{"type":48,"value":253},"Define a framework for answering the question with data:",{"type":42,"tag":161,"props":255,"children":256},{},[257,262,267,272],{"type":42,"tag":91,"props":258,"children":259},{},[260],{"type":48,"value":261},"the specific data questions that would support or change the recommendation",{"type":42,"tag":91,"props":263,"children":264},{},[265],{"type":48,"value":266},"the comparisons and dimensions to inspect",{"type":42,"tag":91,"props":268,"children":269},{},[270],{"type":48,"value":271},"the unit of analysis that matches the decision",{"type":42,"tag":91,"props":273,"children":274},{},[275],{"type":48,"value":276},"the metric definitions and caveats needed to interpret the result",{"type":42,"tag":51,"props":278,"children":279},{},[280],{"type":48,"value":281},"Use the framework to surface plausible hypotheses or interpretations, then turn them into focused data questions. Keep the framework specific enough to avoid broad exploration and support a recommendation.",{"type":42,"tag":51,"props":283,"children":284},{},[285],{"type":48,"value":286},"Use $design-kpis when the success metric, driver metrics, guardrails, or measurement plan need to be defined before the analysis can proceed.",{"type":42,"tag":51,"props":288,"children":289},{},[290],{"type":48,"value":291},"Start by defining what the answer needs to show in plain language. Then choose the data that matches that meaning as closely as possible, including who is counted and what comparison makes the number meaningful. If a field or event captures only part of what the decision cares about, say what it captures and what it leaves out.",{"type":42,"tag":75,"props":293,"children":295},{"id":294},"_4-run-focused-quantitative-analysis",[296],{"type":48,"value":297},"4. Run Focused Quantitative Analysis",{"type":42,"tag":51,"props":299,"children":300},{},[301],{"type":48,"value":302},"Run enough quantitative analysis to support or reject the framed hypotheses and inform the decision:",{"type":42,"tag":161,"props":304,"children":305},{},[306,316,326,336,346],{"type":42,"tag":91,"props":307,"children":308},{},[309,314],{"type":42,"tag":95,"props":310,"children":311},{},[312],{"type":48,"value":313},"Follow the framework.",{"type":48,"value":315}," Run the analyses that could change the recommendation first. Track additional data questions that emerge, answer the ones that matter for the decision, and leave lower-impact cuts as follow-up instead of expanding into broad exploration.",{"type":42,"tag":91,"props":317,"children":318},{},[319,324],{"type":42,"tag":95,"props":320,"children":321},{},[322],{"type":48,"value":323},"Use the right comparison.",{"type":48,"value":325}," Interpret results against the relevant baseline, denominator, or comparison point before turning them into a recommendation. For example, do not conclude that one group is the best opportunity just because it has the most total usage. Check whether usage is high because the group is larger, whether the pattern still holds after normalizing by the active base, whether the group is growing or declining, whether the usage reflects the behavior or outcome that matters, and whether business context changes the interpretation.",{"type":42,"tag":91,"props":327,"children":328},{},[329,334],{"type":42,"tag":95,"props":330,"children":331},{},[332],{"type":48,"value":333},"Size the opportunities.",{"type":48,"value":335}," Estimate the magnitude of impact each important opportunity could have. State what is being compared, which metric represents impact, what denominator or population it uses, and whether the data is complete enough to trust. Keep material unknown or unclassified groups visible when they could change the interpretation.",{"type":42,"tag":91,"props":337,"children":338},{},[339,344],{"type":42,"tag":95,"props":340,"children":341},{},[342],{"type":48,"value":343},"Keep quantitative work inspectable.",{"type":48,"value":345}," Use $jupyter-notebooks to record queries and analysis. Use $analyze-data-quality when source freshness, grain, joins, missingness, schema drift, or unexpected distributions could affect trust.",{"type":42,"tag":91,"props":347,"children":348},{},[349,354],{"type":42,"tag":95,"props":350,"children":351},{},[352],{"type":48,"value":353},"Validate before concluding.",{"type":48,"value":355}," Use $validate-data before sharing stakeholder-facing recommendations, high-impact claims, or surprising results. When dashboards and direct queries both exist, reconcile them or explain why they differ.",{"type":42,"tag":75,"props":357,"children":359},{"id":358},"_5-translate-evidence-into-decision-implications",[360],{"type":48,"value":361},"5. Translate Evidence Into Decision Implications",{"type":42,"tag":51,"props":363,"children":364},{},[365],{"type":48,"value":366},"Frame the findings within the broader business context. Do not present quantitative evidence and business context as two unrelated streams.",{"type":42,"tag":51,"props":368,"children":369},{},[370],{"type":48,"value":371},"Interpret the evidence through the decision lenses that best fit the question. Choose lenses that would actually change the recommendation, and skip ones that would add noise or false precision. Common lenses include:",{"type":42,"tag":161,"props":373,"children":374},{},[375,385,395,405,415,425,435,445,455,465,475],{"type":42,"tag":91,"props":376,"children":377},{},[378,383],{"type":42,"tag":95,"props":379,"children":380},{},[381],{"type":48,"value":382},"Current scale:",{"type":48,"value":384}," Is the opportunity or problem large enough today to matter for the decision?",{"type":42,"tag":91,"props":386,"children":387},{},[388,393],{"type":42,"tag":95,"props":389,"children":390},{},[391],{"type":48,"value":392},"Momentum:",{"type":48,"value":394}," Is the signal growing, shrinking, accelerating, or newly emerging?",{"type":42,"tag":91,"props":396,"children":397},{},[398,403],{"type":42,"tag":95,"props":399,"children":400},{},[401],{"type":48,"value":402},"Breadth:",{"type":48,"value":404}," Is the pattern broad-based, or does it only appear in a narrow corner of the business?",{"type":42,"tag":91,"props":406,"children":407},{},[408,413],{"type":42,"tag":95,"props":409,"children":410},{},[411],{"type":48,"value":412},"Concentration:",{"type":48,"value":414}," Does the conclusion depend on a few large entities, events, or outliers?",{"type":42,"tag":91,"props":416,"children":417},{},[418,423],{"type":42,"tag":95,"props":419,"children":420},{},[421],{"type":48,"value":422},"Intensity:",{"type":48,"value":424}," Is the behavior deep enough per unit to suggest real need, value, or risk?",{"type":42,"tag":91,"props":426,"children":427},{},[428,433],{"type":42,"tag":95,"props":429,"children":430},{},[431],{"type":48,"value":432},"Efficiency:",{"type":48,"value":434}," Does the option create better output, margin, conversion, productivity, or quality for the input required?",{"type":42,"tag":91,"props":436,"children":437},{},[438,443],{"type":42,"tag":95,"props":439,"children":440},{},[441],{"type":48,"value":442},"Addressability:",{"type":48,"value":444}," Can the team realistically act on this option with available product, GTM, operational, policy, or technical levers?",{"type":42,"tag":91,"props":446,"children":447},{},[448,453],{"type":42,"tag":95,"props":449,"children":450},{},[451],{"type":48,"value":452},"Differentiation:",{"type":48,"value":454}," Does this group or use case require a distinct motion, product experience, support model, or message?",{"type":42,"tag":91,"props":456,"children":457},{},[458,463],{"type":42,"tag":95,"props":459,"children":460},{},[461],{"type":48,"value":462},"Substitution:",{"type":48,"value":464}," Is there evidence that behavior, spend, time, or workload could shift from another path?",{"type":42,"tag":91,"props":466,"children":467},{},[468,473],{"type":42,"tag":95,"props":469,"children":470},{},[471],{"type":48,"value":472},"Risk or dependency:",{"type":48,"value":474}," Are there quality, trust, compliance, technical, operational, or data constraints that change the recommendation?",{"type":42,"tag":91,"props":476,"children":477},{},[478,483],{"type":42,"tag":95,"props":479,"children":480},{},[481],{"type":48,"value":482},"Coverage:",{"type":48,"value":484}," Are unknown, missing, or sparsely tagged records large enough to change the answer?",{"type":42,"tag":51,"props":486,"children":487},{},[488],{"type":48,"value":489},"Use these as thinking tools, not a checklist. Explain why the chosen lenses matter for this decision, and mention omitted cuts only when they would plausibly change the interpretation or help explain the result.",{"type":42,"tag":51,"props":491,"children":492},{},[493],{"type":48,"value":494},"Use the measured opportunities to explain which differences matter for the decision and which ones call for different actions. If the business context shows that the initial sizing misses the actionable part of the opportunity, add the focused sizing cut needed to make the recommendation useful.",{"type":42,"tag":51,"props":496,"children":497},{},[498],{"type":48,"value":499},"If evidence conflicts, say so directly and explain which interpretation is better supported. Do not smooth over disagreement between sources.",{"type":42,"tag":75,"props":501,"children":503},{"id":502},"_6-hand-off-the-recommendation",[504],{"type":48,"value":505},"6. Hand Off The Recommendation",{"type":42,"tag":51,"props":507,"children":508},{},[509],{"type":48,"value":510},"End by handing the decision-ready recommendation to $build-report 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. This handoff is mandatory when no explicit human waiver was given; do not infer a waiver because the user asked a direct question or did not use the word \"report\". This workflow owns the analytical conclusion; $build-report owns the reader-facing structure, visuals, evidence placement, and delivery surface.",{"type":42,"tag":51,"props":512,"children":513},{},[514],{"type":48,"value":515},"Before handoff, make the recommendation explicit:",{"type":42,"tag":161,"props":517,"children":518},{},[519,524,529,534],{"type":42,"tag":91,"props":520,"children":521},{},[522],{"type":48,"value":523},"what they should believe or do next",{"type":42,"tag":91,"props":525,"children":526},{},[527],{"type":48,"value":528},"why the evidence supports that recommendation",{"type":42,"tag":91,"props":530,"children":531},{},[532],{"type":48,"value":533},"which caveats or dependencies matter",{"type":42,"tag":91,"props":535,"children":536},{},[537],{"type":48,"value":538},"what follow-up analysis would most improve confidence",{"type":42,"tag":51,"props":540,"children":541},{},[542],{"type":48,"value":543},"If evidence is incomplete, label the recommendation as provisional and state what would change confidence. Do not overstate the conclusion just to make the answer feel decisive.",{"type":42,"tag":51,"props":545,"children":546},{},[547],{"type":48,"value":548},"Use $validate-data when methodology, calculations, caveats, or the evidentiary support for the conclusion need review before sharing.",{"type":42,"tag":51,"props":550,"children":551},{},[552],{"type":48,"value":553},"Pass narrative ingredients to the report surface, not only result tables:",{"type":42,"tag":161,"props":555,"children":556},{},[557,562,567,572,577],{"type":42,"tag":91,"props":558,"children":559},{},[560],{"type":48,"value":561},"direct answer and recommendation",{"type":42,"tag":91,"props":563,"children":564},{},[565],{"type":48,"value":566},"key evidence and how to interpret it",{"type":42,"tag":91,"props":568,"children":569},{},[570],{"type":48,"value":571},"implication for the decision",{"type":42,"tag":91,"props":573,"children":574},{},[575],{"type":48,"value":576},"unresolved uncertainty and caveats",{"type":42,"tag":91,"props":578,"children":579},{},[580],{"type":48,"value":581},"recommended follow-up",{"items":583,"total":692},[584,601,617,630,646,660,677],{"slug":585,"name":585,"fn":586,"description":587,"org":588,"tags":589,"stars":25,"repoUrl":26,"updatedAt":600},"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},[590,591,594,597],{"name":23,"slug":24,"type":15},{"name":592,"slug":593,"type":15},"CRM","crm",{"name":595,"slug":596,"type":15},"Research","research",{"name":598,"slug":599,"type":15},"Sales","sales","2026-07-01T07:54:11.79288",{"slug":602,"name":602,"fn":603,"description":604,"org":605,"tags":606,"stars":25,"repoUrl":26,"updatedAt":616},"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},[607,610,613],{"name":608,"slug":609,"type":15},"Audit","audit",{"name":611,"slug":612,"type":15},"Data Engineering","data-engineering",{"name":614,"slug":615,"type":15},"Data Quality","data-quality","2026-07-01T07:55:01.146961",{"slug":618,"name":618,"fn":619,"description":620,"org":621,"tags":622,"stars":25,"repoUrl":26,"updatedAt":629},"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},[623,626],{"name":624,"slug":625,"type":15},"Communications","communications",{"name":627,"slug":628,"type":15},"Productivity","productivity","2026-07-14T05:43:36.096323",{"slug":631,"name":631,"fn":632,"description":633,"org":634,"tags":635,"stars":25,"repoUrl":26,"updatedAt":645},"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},[636,638,641,644],{"name":637,"slug":631,"type":15},"Apollo",{"name":639,"slug":640,"type":15},"Lead Enrichment","lead-enrichment",{"name":642,"slug":643,"type":15},"Prospecting","prospecting",{"name":598,"slug":599,"type":15},"2026-07-14T05:43:34.800076",{"slug":609,"name":609,"fn":647,"description":648,"org":649,"tags":650,"stars":25,"repoUrl":26,"updatedAt":659},"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},[651,652,655,656],{"name":608,"slug":609,"type":15},{"name":653,"slug":654,"type":15},"Design","design",{"name":20,"slug":21,"type":15},{"name":657,"slug":658,"type":15},"UX Design","ux-design","2026-07-01T07:54:30.613428",{"slug":661,"name":661,"fn":662,"description":663,"org":664,"tags":665,"stars":25,"repoUrl":26,"updatedAt":676},"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},[666,669,672,675],{"name":667,"slug":668,"type":15},"Content Creation","content-creation",{"name":670,"slug":671,"type":15},"Finance","finance",{"name":673,"slug":674,"type":15},"Financial Modeling","financial-modeling",{"name":598,"slug":599,"type":15},"2026-07-01T07:54:02.779003",{"slug":678,"name":678,"fn":679,"description":680,"org":681,"tags":682,"stars":25,"repoUrl":26,"updatedAt":691},"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},[683,686,689,690],{"name":684,"slug":685,"type":15},"Competitive Intelligence","competitive-intelligence",{"name":687,"slug":688,"type":15},"Marketing","marketing",{"name":595,"slug":596,"type":15},{"name":598,"slug":599,"type":15},"2026-07-01T07:54:13.073252",43,{"items":694,"total":895},[695,716,739,756,772,791,808,822,838,852,864,879],{"slug":696,"name":696,"fn":697,"description":698,"org":699,"tags":700,"stars":713,"repoUrl":714,"updatedAt":715},"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},[701,704,707,710],{"name":702,"slug":703,"type":15},"Documents","documents",{"name":705,"slug":706,"type":15},"Healthcare","healthcare",{"name":708,"slug":709,"type":15},"Insurance","insurance",{"name":711,"slug":712,"type":15},"Regulatory Compliance","regulatory-compliance",28169,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fopenai-agents-python","2026-04-16T05:11:39.180399",{"slug":717,"name":717,"fn":718,"description":719,"org":720,"tags":721,"stars":736,"repoUrl":737,"updatedAt":738},"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},[722,725,727,730,733],{"name":723,"slug":724,"type":15},".NET","dotnet",{"name":726,"slug":717,"type":15},"ASP.NET Core",{"name":728,"slug":729,"type":15},"Blazor","blazor",{"name":731,"slug":732,"type":15},"C#","csharp",{"name":734,"slug":735,"type":15},"Web Development","web-development",23787,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fskills","2026-04-12T05:07:02.819491",{"slug":740,"name":740,"fn":741,"description":742,"org":743,"tags":744,"stars":736,"repoUrl":737,"updatedAt":755},"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},[745,748,751,754],{"name":746,"slug":747,"type":15},"Apps SDK","apps-sdk",{"name":749,"slug":750,"type":15},"ChatGPT","chatgpt",{"name":752,"slug":753,"type":15},"MCP","mcp",{"name":9,"slug":8,"type":15},"2026-04-12T05:07:05.468097",{"slug":757,"name":757,"fn":758,"description":759,"org":760,"tags":761,"stars":736,"repoUrl":737,"updatedAt":771},"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},[762,765,768],{"name":763,"slug":764,"type":15},"API Development","api-development",{"name":766,"slug":767,"type":15},"CLI","cli",{"name":769,"slug":770,"type":15},"Codex","codex","2026-04-12T05:07:04.132762",{"slug":773,"name":773,"fn":774,"description":775,"org":776,"tags":777,"stars":736,"repoUrl":737,"updatedAt":790},"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},[778,781,784,787],{"name":779,"slug":780,"type":15},"Cloudflare","cloudflare",{"name":782,"slug":783,"type":15},"Cloudflare Pages","cloudflare-pages",{"name":785,"slug":786,"type":15},"Cloudflare Workers","cloudflare-workers",{"name":788,"slug":789,"type":15},"Deployment","deployment","2026-04-12T05:07:14.275118",{"slug":792,"name":792,"fn":793,"description":794,"org":795,"tags":796,"stars":736,"repoUrl":737,"updatedAt":807},"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},[797,798,801,804],{"name":627,"slug":628,"type":15},{"name":799,"slug":800,"type":15},"Project Management","project-management",{"name":802,"slug":803,"type":15},"Strategy","strategy",{"name":805,"slug":806,"type":15},"Task Management","task-management","2026-05-23T06:17:16.870838",{"slug":809,"name":809,"fn":810,"description":811,"org":812,"tags":813,"stars":736,"repoUrl":737,"updatedAt":821},"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},[814,815,817,820],{"name":653,"slug":654,"type":15},{"name":816,"slug":809,"type":15},"Figma",{"name":818,"slug":819,"type":15},"Frontend","frontend",{"name":752,"slug":753,"type":15},"2026-04-12T05:06:47.939943",{"slug":823,"name":823,"fn":824,"description":825,"org":826,"tags":827,"stars":736,"repoUrl":737,"updatedAt":837},"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},[828,829,832,833,834],{"name":653,"slug":654,"type":15},{"name":830,"slug":831,"type":15},"Design System","design-system",{"name":816,"slug":809,"type":15},{"name":818,"slug":819,"type":15},{"name":835,"slug":836,"type":15},"UI Components","ui-components","2026-05-10T05:59:52.971881",{"slug":839,"name":839,"fn":840,"description":841,"org":842,"tags":843,"stars":736,"repoUrl":737,"updatedAt":851},"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},[844,845,846,849,850],{"name":653,"slug":654,"type":15},{"name":830,"slug":831,"type":15},{"name":847,"slug":848,"type":15},"Documentation","documentation",{"name":816,"slug":809,"type":15},{"name":818,"slug":819,"type":15},"2026-05-16T06:07:47.821474",{"slug":853,"name":853,"fn":854,"description":855,"org":856,"tags":857,"stars":736,"repoUrl":737,"updatedAt":863},"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},[858,859,860,861,862],{"name":653,"slug":654,"type":15},{"name":816,"slug":809,"type":15},{"name":818,"slug":819,"type":15},{"name":835,"slug":836,"type":15},{"name":734,"slug":735,"type":15},"2026-05-16T06:07:40.583615",{"slug":865,"name":865,"fn":866,"description":867,"org":868,"tags":869,"stars":736,"repoUrl":737,"updatedAt":878},"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},[870,873,874,877],{"name":871,"slug":872,"type":15},"Animation","animation",{"name":769,"slug":770,"type":15},{"name":875,"slug":876,"type":15},"Creative","creative",{"name":653,"slug":654,"type":15},"2026-05-02T05:31:48.48485",{"slug":880,"name":880,"fn":881,"description":882,"org":883,"tags":884,"stars":736,"repoUrl":737,"updatedAt":894},"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},[885,886,887,890,893],{"name":875,"slug":876,"type":15},{"name":653,"slug":654,"type":15},{"name":888,"slug":889,"type":15},"Image Generation","image-generation",{"name":891,"slug":892,"type":15},"Images","images",{"name":9,"slug":8,"type":15},"2026-05-15T06:23:24.312127",675]