[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-openai-shopify-app-store-review":3,"mdc-h5jkng-key":36,"related-repo-openai-shopify-app-store-review":570,"related-org-openai-shopify-app-store-review":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},"shopify-app-store-review","audit Shopify apps for compliance","Run a pre-submission compliance check against your Shopify app's codebase. Reviews App Store requirements and surfaces likely issues before you submit for official review.",{"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},"Compliance","compliance","tag",{"name":17,"slug":18,"type":15},"QA","qa",{"name":20,"slug":21,"type":15},"Shopify","shopify",{"name":23,"slug":24,"type":15},"Code Analysis","code-analysis",3992,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins","2026-06-30T19:00:57.102",null,465,[],{"repoUrl":26,"stars":25,"forks":29,"topics":32,"description":33},[],"OpenAI Plugins","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins\u002Ftree\u002FHEAD\u002Fplugins\u002Fshopify\u002Fskills\u002Fshopify-app-store-review","---\nname: shopify-app-store-review\ndescription: \"Run a pre-submission compliance check against your Shopify app's codebase. Reviews App Store requirements and surfaces likely issues before you submit for official review.\"\ncompatibility: Claude Code, Claude Desktop, Cursor\nmetadata:\n  author: Shopify\n  version: \"1.9.1\"\n---\n\nYou are a Shopify App Store reviewer performing a pre-submission compliance check against a developer's local codebase. Your role is to evaluate each requirement listed below against the code in this project, identifying potential compliance issues before the app is submitted for official review.\n\n## How to Process Requirements\n\nTo manage context efficiently, process each requirement independently using a sub-agent or separate evaluation pass.\n\nFor each requirement:\n\n1. Read the requirement's name, description, and verification guidance carefully.\n2. Search the codebase for relevant code, configuration files, API calls, and patterns described in the guidance.\n3. Assign one of three statuses based on your findings:\n\n- ✅ **Likely passing**: You found positive evidence of compliance in the codebase (e.g., the required API call exists, the correct pattern is implemented, configuration is present).\n- ❌ **Likely failing**: You found code that clearly violates the requirement (e.g., a prohibited pattern is in use, a required implementation is incorrect or missing when it should be present).\n- ⚠️ **Needs review**: You cannot fully confirm or deny compliance from the codebase alone. You detected signals that make the requirement relevant, but the determination requires human judgment or context you don't have access to. Requirement guidance recommends extra consideration in certain met conditions. **When in doubt, use this status rather than silently passing.**\n\n### Important Evaluation Principles\n\n- **Error on the side of surfacing ambiguity when evaluating requirements.** If you're unsure whether something passes, mark it as ⚠️ Needs review. Do not silently pass a requirement you cannot verify.\n- **Be brief but specific in your explanations.** There are a lot of requirements, keep context brief for the user. Let them ask follow up questions for additional details like file paths.\n\n## Section and Group Context\n\nSome sections and groups include an **applicability note** immediately after their title. Evaluate this note _before_ processing any requirements inside the group. There are three types:\n\n- **Conditional** — Starts with \"Applies if…\". Check the codebase for the described signal. If the signal is **not** present, skip every requirement in the group and record the group as skipped (see below). If the signal **is** present, evaluate the group normally.\n- **Opt-in** — Starts with \"Opt-in:\". Skip the group unless the user explicitly asked for it in their request or after report delivery. Record it as skipped.\n- **Informational** — Starts with \"Note:\". Does not gate the group. Use the context to inform your evaluation of the requirements inside.\n\nWhen in doubt about whether a conditional signal is present, skip the group rather than evaluating it and allow the user to explicitly request evaluation.\n\n### Tracking skipped groups\n\nKeep a running list of any groups you skip, including:\n\n- The group number and name\n- The reason (conditional signal not detected, or opt-in not requested)\n\nReport this list in the **Skipped groups** section of the output (see Output Format).\n\n> Note: Gaps in requirement numbering (e.g., missing 1.1.5, 2.2.2) are intentional. Omitted requirements can only be verified at submission time and are not part of this local check.\n\n## List of Requirements\n\nFetch the canonical, up-to-date list of requirements from:\n\n```\nhttps:\u002F\u002Fshopify.dev\u002Fdocs\u002Fapps\u002Flaunch\u002Fapp-store-review\u002Fapp-store-ai-self-review-requirements\n```\n\nThat page is the source of truth — it contains every requirement to be evaluated, each with a **Description** and **Verification guidance**. Use whatever web-fetching capability you have (e.g., your web fetch tool, or `curl` via your shell tool) to retrieve it, then evaluate every requirement listed there using the rules in \"How to Process Requirements\" above.\n\nDo not rely on a cached or remembered list of requirements — always fetch the live page so the review reflects the latest policy.\n\n## Output Format\n\nAfter evaluating all requirements, compile the results into a single report using the format below. The goal is to give the developer a clear, actionable summary without overwhelming them. You'll notice we don't list details for passing requirements, we only count them, this is an example of keeping the report focussed and digestible. Keep explanations concise. If you could not evaluate a requirement due to insufficient codebase access or an unrelated project structure, note this separately at the end of the report.\n\n### Summary\n\n✅ **Likely passing:** {number}\n❌ **Likely failing:** {number}\n⚠️ **Needs review:** {number}\n⏭️ **Groups skipped:** {number} _(see below)_\n\n**Note:** The agent has reviewed a subset of requirements that have been selected by Shopify as checkable against a local codebase without browser context. These and additional requirements will still be reviewed by Shopify upon submission to the Shopify App Store.\n\n### ⚠️ Requirements that need review\n\nFor each requirement needing review, provide the following with a new line between each instance:\n\n⚠️ **Requirement name**\n\n**Why this needs attention:** Explain the ambiguity, what you can't determine from code alone and what the developer should verify.\n\n**What was detected:** Describe the signals or patterns found (or notably absent) that make this requirement relevant.\n\n### ❌ Requirements that are likely failing\n\nFor each requirement needing review, provide the following with a new line between each instance:\n\n❌ **Requirement name**\n\n**Why this matters:** A brief rationale explaining the compliance risk.\n\n**What was found:** A concise explanation of the violation detected, referencing specific files, code patterns, or configurations where possible.\n\n### Skipped groups\n\nThe following groups weren't evaluated because they didn't appear to apply to this codebase (or are opt-in). If you'd like me to check any of these anyway, just ask.\n\nFor each skipped group:\n\n- **{Group number} {Group name}** — {reason, e.g. \"No theme app extension detected\" or \"Opt-in only\"}\n\n### Resources\n\nUnless all requirements are labeled as likely passing, include these helpful resources at the end of the report:\n\n- [App Store requirements documentation](https:\u002F\u002Fshopify.dev\u002Fdocs\u002Fapps\u002Flaunch\u002Fshopify-app-store\u002Fapp-store-requirements)\n- [Best practices for apps](https:\u002F\u002Fshopify.dev\u002Fdocs\u002Fapps\u002Flaunch\u002Fshopify-app-store\u002Fbest-practices)\n- [About billing for your app](https:\u002F\u002Fshopify.dev\u002Fdocs\u002Fapps\u002Flaunch\u002Fbilling)\n- [Submitting your app for review](https:\u002F\u002Fshopify.dev\u002Fdocs\u002Fapps\u002Flaunch\u002Fapp-store-review\u002Fsubmit-app-for-review)\n",{"data":37,"body":41},{"name":4,"description":6,"compatibility":38,"metadata":39},"Claude Code, Claude Desktop, Cursor",{"author":20,"version":40},"1.9.1",{"type":42,"children":43},"root",[44,52,59,64,69,89,135,142,165,171,191,238,243,249,254,267,279,288,294,299,312,339,344,350,355,361,398,408,414,419,428,438,448,454,458,466,476,486,491,496,501,514,520,525],{"type":45,"tag":46,"props":47,"children":48},"element","p",{},[49],{"type":50,"value":51},"text","You are a Shopify App Store reviewer performing a pre-submission compliance check against a developer's local codebase. Your role is to evaluate each requirement listed below against the code in this project, identifying potential compliance issues before the app is submitted for official review.",{"type":45,"tag":53,"props":54,"children":56},"h2",{"id":55},"how-to-process-requirements",[57],{"type":50,"value":58},"How to Process Requirements",{"type":45,"tag":46,"props":60,"children":61},{},[62],{"type":50,"value":63},"To manage context efficiently, process each requirement independently using a sub-agent or separate evaluation pass.",{"type":45,"tag":46,"props":65,"children":66},{},[67],{"type":50,"value":68},"For each requirement:",{"type":45,"tag":70,"props":71,"children":72},"ol",{},[73,79,84],{"type":45,"tag":74,"props":75,"children":76},"li",{},[77],{"type":50,"value":78},"Read the requirement's name, description, and verification guidance carefully.",{"type":45,"tag":74,"props":80,"children":81},{},[82],{"type":50,"value":83},"Search the codebase for relevant code, configuration files, API calls, and patterns described in the guidance.",{"type":45,"tag":74,"props":85,"children":86},{},[87],{"type":50,"value":88},"Assign one of three statuses based on your findings:",{"type":45,"tag":90,"props":91,"children":92},"ul",{},[93,106,118],{"type":45,"tag":74,"props":94,"children":95},{},[96,98,104],{"type":50,"value":97},"✅ ",{"type":45,"tag":99,"props":100,"children":101},"strong",{},[102],{"type":50,"value":103},"Likely passing",{"type":50,"value":105},": You found positive evidence of compliance in the codebase (e.g., the required API call exists, the correct pattern is implemented, configuration is present).",{"type":45,"tag":74,"props":107,"children":108},{},[109,111,116],{"type":50,"value":110},"❌ ",{"type":45,"tag":99,"props":112,"children":113},{},[114],{"type":50,"value":115},"Likely failing",{"type":50,"value":117},": You found code that clearly violates the requirement (e.g., a prohibited pattern is in use, a required implementation is incorrect or missing when it should be present).",{"type":45,"tag":74,"props":119,"children":120},{},[121,123,128,130],{"type":50,"value":122},"⚠️ ",{"type":45,"tag":99,"props":124,"children":125},{},[126],{"type":50,"value":127},"Needs review",{"type":50,"value":129},": You cannot fully confirm or deny compliance from the codebase alone. You detected signals that make the requirement relevant, but the determination requires human judgment or context you don't have access to. Requirement guidance recommends extra consideration in certain met conditions. ",{"type":45,"tag":99,"props":131,"children":132},{},[133],{"type":50,"value":134},"When in doubt, use this status rather than silently passing.",{"type":45,"tag":136,"props":137,"children":139},"h3",{"id":138},"important-evaluation-principles",[140],{"type":50,"value":141},"Important Evaluation Principles",{"type":45,"tag":90,"props":143,"children":144},{},[145,155],{"type":45,"tag":74,"props":146,"children":147},{},[148,153],{"type":45,"tag":99,"props":149,"children":150},{},[151],{"type":50,"value":152},"Error on the side of surfacing ambiguity when evaluating requirements.",{"type":50,"value":154}," If you're unsure whether something passes, mark it as ⚠️ Needs review. Do not silently pass a requirement you cannot verify.",{"type":45,"tag":74,"props":156,"children":157},{},[158,163],{"type":45,"tag":99,"props":159,"children":160},{},[161],{"type":50,"value":162},"Be brief but specific in your explanations.",{"type":50,"value":164}," There are a lot of requirements, keep context brief for the user. Let them ask follow up questions for additional details like file paths.",{"type":45,"tag":53,"props":166,"children":168},{"id":167},"section-and-group-context",[169],{"type":50,"value":170},"Section and Group Context",{"type":45,"tag":46,"props":172,"children":173},{},[174,176,181,183,189],{"type":50,"value":175},"Some sections and groups include an ",{"type":45,"tag":99,"props":177,"children":178},{},[179],{"type":50,"value":180},"applicability note",{"type":50,"value":182}," immediately after their title. Evaluate this note ",{"type":45,"tag":184,"props":185,"children":186},"em",{},[187],{"type":50,"value":188},"before",{"type":50,"value":190}," processing any requirements inside the group. There are three types:",{"type":45,"tag":90,"props":192,"children":193},{},[194,218,228],{"type":45,"tag":74,"props":195,"children":196},{},[197,202,204,209,211,216],{"type":45,"tag":99,"props":198,"children":199},{},[200],{"type":50,"value":201},"Conditional",{"type":50,"value":203}," — Starts with \"Applies if…\". Check the codebase for the described signal. If the signal is ",{"type":45,"tag":99,"props":205,"children":206},{},[207],{"type":50,"value":208},"not",{"type":50,"value":210}," present, skip every requirement in the group and record the group as skipped (see below). If the signal ",{"type":45,"tag":99,"props":212,"children":213},{},[214],{"type":50,"value":215},"is",{"type":50,"value":217}," present, evaluate the group normally.",{"type":45,"tag":74,"props":219,"children":220},{},[221,226],{"type":45,"tag":99,"props":222,"children":223},{},[224],{"type":50,"value":225},"Opt-in",{"type":50,"value":227}," — Starts with \"Opt-in:\". Skip the group unless the user explicitly asked for it in their request or after report delivery. Record it as skipped.",{"type":45,"tag":74,"props":229,"children":230},{},[231,236],{"type":45,"tag":99,"props":232,"children":233},{},[234],{"type":50,"value":235},"Informational",{"type":50,"value":237}," — Starts with \"Note:\". Does not gate the group. Use the context to inform your evaluation of the requirements inside.",{"type":45,"tag":46,"props":239,"children":240},{},[241],{"type":50,"value":242},"When in doubt about whether a conditional signal is present, skip the group rather than evaluating it and allow the user to explicitly request evaluation.",{"type":45,"tag":136,"props":244,"children":246},{"id":245},"tracking-skipped-groups",[247],{"type":50,"value":248},"Tracking skipped groups",{"type":45,"tag":46,"props":250,"children":251},{},[252],{"type":50,"value":253},"Keep a running list of any groups you skip, including:",{"type":45,"tag":90,"props":255,"children":256},{},[257,262],{"type":45,"tag":74,"props":258,"children":259},{},[260],{"type":50,"value":261},"The group number and name",{"type":45,"tag":74,"props":263,"children":264},{},[265],{"type":50,"value":266},"The reason (conditional signal not detected, or opt-in not requested)",{"type":45,"tag":46,"props":268,"children":269},{},[270,272,277],{"type":50,"value":271},"Report this list in the ",{"type":45,"tag":99,"props":273,"children":274},{},[275],{"type":50,"value":276},"Skipped groups",{"type":50,"value":278}," section of the output (see Output Format).",{"type":45,"tag":280,"props":281,"children":282},"blockquote",{},[283],{"type":45,"tag":46,"props":284,"children":285},{},[286],{"type":50,"value":287},"Note: Gaps in requirement numbering (e.g., missing 1.1.5, 2.2.2) are intentional. Omitted requirements can only be verified at submission time and are not part of this local check.",{"type":45,"tag":53,"props":289,"children":291},{"id":290},"list-of-requirements",[292],{"type":50,"value":293},"List of Requirements",{"type":45,"tag":46,"props":295,"children":296},{},[297],{"type":50,"value":298},"Fetch the canonical, up-to-date list of requirements from:",{"type":45,"tag":300,"props":301,"children":305},"pre",{"className":302,"code":304,"language":50},[303],"language-text","https:\u002F\u002Fshopify.dev\u002Fdocs\u002Fapps\u002Flaunch\u002Fapp-store-review\u002Fapp-store-ai-self-review-requirements\n",[306],{"type":45,"tag":307,"props":308,"children":310},"code",{"__ignoreMap":309},"",[311],{"type":50,"value":304},{"type":45,"tag":46,"props":313,"children":314},{},[315,317,322,324,329,331,337],{"type":50,"value":316},"That page is the source of truth — it contains every requirement to be evaluated, each with a ",{"type":45,"tag":99,"props":318,"children":319},{},[320],{"type":50,"value":321},"Description",{"type":50,"value":323}," and ",{"type":45,"tag":99,"props":325,"children":326},{},[327],{"type":50,"value":328},"Verification guidance",{"type":50,"value":330},". Use whatever web-fetching capability you have (e.g., your web fetch tool, or ",{"type":45,"tag":307,"props":332,"children":334},{"className":333},[],[335],{"type":50,"value":336},"curl",{"type":50,"value":338}," via your shell tool) to retrieve it, then evaluate every requirement listed there using the rules in \"How to Process Requirements\" above.",{"type":45,"tag":46,"props":340,"children":341},{},[342],{"type":50,"value":343},"Do not rely on a cached or remembered list of requirements — always fetch the live page so the review reflects the latest policy.",{"type":45,"tag":53,"props":345,"children":347},{"id":346},"output-format",[348],{"type":50,"value":349},"Output Format",{"type":45,"tag":46,"props":351,"children":352},{},[353],{"type":50,"value":354},"After evaluating all requirements, compile the results into a single report using the format below. The goal is to give the developer a clear, actionable summary without overwhelming them. You'll notice we don't list details for passing requirements, we only count them, this is an example of keeping the report focussed and digestible. Keep explanations concise. If you could not evaluate a requirement due to insufficient codebase access or an unrelated project structure, note this separately at the end of the report.",{"type":45,"tag":136,"props":356,"children":358},{"id":357},"summary",[359],{"type":50,"value":360},"Summary",{"type":45,"tag":46,"props":362,"children":363},{},[364,365,370,372,377,379,384,386,391,393],{"type":50,"value":97},{"type":45,"tag":99,"props":366,"children":367},{},[368],{"type":50,"value":369},"Likely passing:",{"type":50,"value":371}," {number}\n❌ ",{"type":45,"tag":99,"props":373,"children":374},{},[375],{"type":50,"value":376},"Likely failing:",{"type":50,"value":378}," {number}\n⚠️ ",{"type":45,"tag":99,"props":380,"children":381},{},[382],{"type":50,"value":383},"Needs review:",{"type":50,"value":385}," {number}\n⏭️ ",{"type":45,"tag":99,"props":387,"children":388},{},[389],{"type":50,"value":390},"Groups skipped:",{"type":50,"value":392}," {number} ",{"type":45,"tag":184,"props":394,"children":395},{},[396],{"type":50,"value":397},"(see below)",{"type":45,"tag":46,"props":399,"children":400},{},[401,406],{"type":45,"tag":99,"props":402,"children":403},{},[404],{"type":50,"value":405},"Note:",{"type":50,"value":407}," The agent has reviewed a subset of requirements that have been selected by Shopify as checkable against a local codebase without browser context. These and additional requirements will still be reviewed by Shopify upon submission to the Shopify App Store.",{"type":45,"tag":136,"props":409,"children":411},{"id":410},"️-requirements-that-need-review",[412],{"type":50,"value":413},"⚠️ Requirements that need review",{"type":45,"tag":46,"props":415,"children":416},{},[417],{"type":50,"value":418},"For each requirement needing review, provide the following with a new line between each instance:",{"type":45,"tag":46,"props":420,"children":421},{},[422,423],{"type":50,"value":122},{"type":45,"tag":99,"props":424,"children":425},{},[426],{"type":50,"value":427},"Requirement name",{"type":45,"tag":46,"props":429,"children":430},{},[431,436],{"type":45,"tag":99,"props":432,"children":433},{},[434],{"type":50,"value":435},"Why this needs attention:",{"type":50,"value":437}," Explain the ambiguity, what you can't determine from code alone and what the developer should verify.",{"type":45,"tag":46,"props":439,"children":440},{},[441,446],{"type":45,"tag":99,"props":442,"children":443},{},[444],{"type":50,"value":445},"What was detected:",{"type":50,"value":447}," Describe the signals or patterns found (or notably absent) that make this requirement relevant.",{"type":45,"tag":136,"props":449,"children":451},{"id":450},"requirements-that-are-likely-failing",[452],{"type":50,"value":453},"❌ Requirements that are likely failing",{"type":45,"tag":46,"props":455,"children":456},{},[457],{"type":50,"value":418},{"type":45,"tag":46,"props":459,"children":460},{},[461,462],{"type":50,"value":110},{"type":45,"tag":99,"props":463,"children":464},{},[465],{"type":50,"value":427},{"type":45,"tag":46,"props":467,"children":468},{},[469,474],{"type":45,"tag":99,"props":470,"children":471},{},[472],{"type":50,"value":473},"Why this matters:",{"type":50,"value":475}," A brief rationale explaining the compliance risk.",{"type":45,"tag":46,"props":477,"children":478},{},[479,484],{"type":45,"tag":99,"props":480,"children":481},{},[482],{"type":50,"value":483},"What was found:",{"type":50,"value":485}," A concise explanation of the violation detected, referencing specific files, code patterns, or configurations where possible.",{"type":45,"tag":136,"props":487,"children":489},{"id":488},"skipped-groups",[490],{"type":50,"value":276},{"type":45,"tag":46,"props":492,"children":493},{},[494],{"type":50,"value":495},"The following groups weren't evaluated because they didn't appear to apply to this codebase (or are opt-in). If you'd like me to check any of these anyway, just ask.",{"type":45,"tag":46,"props":497,"children":498},{},[499],{"type":50,"value":500},"For each skipped group:",{"type":45,"tag":90,"props":502,"children":503},{},[504],{"type":45,"tag":74,"props":505,"children":506},{},[507,512],{"type":45,"tag":99,"props":508,"children":509},{"group":309,"number":309},[510],{"type":50,"value":511}," {Group name}",{"type":50,"value":513}," — {reason, e.g. \"No theme app extension detected\" or \"Opt-in only\"}",{"type":45,"tag":136,"props":515,"children":517},{"id":516},"resources",[518],{"type":50,"value":519},"Resources",{"type":45,"tag":46,"props":521,"children":522},{},[523],{"type":50,"value":524},"Unless all requirements are labeled as likely passing, include these helpful resources at the end of the report:",{"type":45,"tag":90,"props":526,"children":527},{},[528,540,550,560],{"type":45,"tag":74,"props":529,"children":530},{},[531],{"type":45,"tag":532,"props":533,"children":537},"a",{"href":534,"rel":535},"https:\u002F\u002Fshopify.dev\u002Fdocs\u002Fapps\u002Flaunch\u002Fshopify-app-store\u002Fapp-store-requirements",[536],"nofollow",[538],{"type":50,"value":539},"App Store requirements documentation",{"type":45,"tag":74,"props":541,"children":542},{},[543],{"type":45,"tag":532,"props":544,"children":547},{"href":545,"rel":546},"https:\u002F\u002Fshopify.dev\u002Fdocs\u002Fapps\u002Flaunch\u002Fshopify-app-store\u002Fbest-practices",[536],[548],{"type":50,"value":549},"Best practices for apps",{"type":45,"tag":74,"props":551,"children":552},{},[553],{"type":45,"tag":532,"props":554,"children":557},{"href":555,"rel":556},"https:\u002F\u002Fshopify.dev\u002Fdocs\u002Fapps\u002Flaunch\u002Fbilling",[536],[558],{"type":50,"value":559},"About billing for your app",{"type":45,"tag":74,"props":561,"children":562},{},[563],{"type":45,"tag":532,"props":564,"children":567},{"href":565,"rel":566},"https:\u002F\u002Fshopify.dev\u002Fdocs\u002Fapps\u002Flaunch\u002Fapp-store-review\u002Fsubmit-app-for-review",[536],[568],{"type":50,"value":569},"Submitting your app for review",{"items":571,"total":692},[572,590,606,618,638,660,680],{"slug":573,"name":573,"fn":574,"description":575,"org":576,"tags":577,"stars":25,"repoUrl":26,"updatedAt":27},"accessibility-and-inclusive-visualization","make data visualizations accessible","Make data visualizations accessible and inclusive. Use when the user needs chart or diagram accessibility guidance, text alternatives for complex visuals, color and contrast review, keyboard support, reduced-motion behavior for animation or parallax, or an accessibility QA workflow for exported figures, UML-like diagrams, and dashboards.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[578,581,584,587],{"name":579,"slug":580,"type":15},"Accessibility","accessibility",{"name":582,"slug":583,"type":15},"Charts","charts",{"name":585,"slug":586,"type":15},"Data Visualization","data-visualization",{"name":588,"slug":589,"type":15},"Design","design",{"slug":591,"name":591,"fn":592,"description":593,"org":594,"tags":595,"stars":25,"repoUrl":26,"updatedAt":605},"agent-browser","automate browser interactions for agents","Browser automation CLI for AI agents. Use when the user needs to interact with websites, verify dev server output, test web apps, navigate pages, fill forms, click buttons, take screenshots, extract data, or automate any browser task. Also triggers when a dev server starts so you can verify it visually.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[596,599,602],{"name":597,"slug":598,"type":15},"Agents","agents",{"name":600,"slug":601,"type":15},"Browser Automation","browser-automation",{"name":603,"slug":604,"type":15},"Testing","testing","2026-04-06T18:41:03.44016",{"slug":607,"name":607,"fn":608,"description":609,"org":610,"tags":611,"stars":25,"repoUrl":26,"updatedAt":617},"agent-browser-verify","verify dev server output with automated browser","Automated browser verification for dev servers. Triggers when a dev server starts to run a visual gut-check with agent-browser — verifies the page loads, checks for console errors, validates key UI elements, and reports pass\u002Ffail before continuing.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[612,613,616],{"name":600,"slug":601,"type":15},{"name":614,"slug":615,"type":15},"Local Development","local-development",{"name":603,"slug":604,"type":15},"2026-04-06T18:41:17.526867",{"slug":619,"name":619,"fn":620,"description":621,"org":622,"tags":623,"stars":25,"repoUrl":26,"updatedAt":637},"agents-sdk","build AI agents on Cloudflare Workers","Build AI agents on Cloudflare Workers using the Agents SDK. Load when creating stateful agents, durable workflows, real-time WebSocket apps, scheduled tasks, MCP servers, or chat applications. Covers Agent class, state management, callable RPC, Workflows integration, and React hooks. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[624,625,628,631,634],{"name":597,"slug":598,"type":15},{"name":626,"slug":627,"type":15},"Cloudflare Workers","cloudflare-workers",{"name":629,"slug":630,"type":15},"SDK","sdk",{"name":632,"slug":633,"type":15},"Serverless","serverless",{"name":635,"slug":636,"type":15},"WebSockets","websockets","2026-04-06T18:39:51.717063",{"slug":639,"name":639,"fn":640,"description":641,"org":642,"tags":643,"stars":25,"repoUrl":26,"updatedAt":659},"ai-elements","build chat UIs with AI Elements","AI Elements component library guidance — pre-built React components for AI interfaces built on shadcn\u002Fui. Use when building chat UIs, message displays, tool call rendering, streaming responses, reasoning panels, or any AI-native interface with the AI SDK.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[644,647,650,653,656],{"name":645,"slug":646,"type":15},"Frontend","frontend",{"name":648,"slug":649,"type":15},"React","react",{"name":651,"slug":652,"type":15},"shadcn\u002Fui","shadcn-ui",{"name":654,"slug":655,"type":15},"UI Components","ui-components",{"name":657,"slug":658,"type":15},"Vercel","vercel","2026-04-06T18:40:59.619419",{"slug":661,"name":661,"fn":662,"description":663,"org":664,"tags":665,"stars":25,"repoUrl":26,"updatedAt":679},"ai-gateway","configure Vercel AI Gateway","Vercel AI Gateway expert guidance. Use when configuring model routing, provider failover, cost tracking, or managing multiple AI providers through a unified API.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[666,669,672,675,678],{"name":667,"slug":668,"type":15},"AI Infrastructure","ai-infrastructure",{"name":670,"slug":671,"type":15},"Cost Optimization","cost-optimization",{"name":673,"slug":674,"type":15},"LLM","llm",{"name":676,"slug":677,"type":15},"Performance","performance",{"name":657,"slug":658,"type":15},"2026-04-06T18:40:44.377464",{"slug":681,"name":681,"fn":682,"description":683,"org":684,"tags":685,"stars":25,"repoUrl":26,"updatedAt":691},"ai-generation-persistence","implement persistence patterns for AI generations","AI generation persistence patterns — unique IDs, addressable URLs, database storage, and cost tracking for every LLM generation",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[686,687,690],{"name":670,"slug":671,"type":15},{"name":688,"slug":689,"type":15},"Database","database",{"name":673,"slug":674,"type":15},"2026-04-06T18:41:08.513425",600,{"items":694,"total":891},[695,716,739,756,772,789,808,820,834,848,860,875],{"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":788},"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,785],{"name":779,"slug":780,"type":15},"Cloudflare","cloudflare",{"name":782,"slug":783,"type":15},"Cloudflare Pages","cloudflare-pages",{"name":626,"slug":627,"type":15},{"name":786,"slug":787,"type":15},"Deployment","deployment","2026-04-12T05:07:14.275118",{"slug":790,"name":790,"fn":791,"description":792,"org":793,"tags":794,"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},[795,798,801,804],{"name":796,"slug":797,"type":15},"Productivity","productivity",{"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":819},"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,818],{"name":588,"slug":589,"type":15},{"name":816,"slug":809,"type":15},"Figma",{"name":645,"slug":646,"type":15},{"name":752,"slug":753,"type":15},"2026-04-12T05:06:47.939943",{"slug":821,"name":821,"fn":822,"description":823,"org":824,"tags":825,"stars":736,"repoUrl":737,"updatedAt":833},"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},[826,827,830,831,832],{"name":588,"slug":589,"type":15},{"name":828,"slug":829,"type":15},"Design System","design-system",{"name":816,"slug":809,"type":15},{"name":645,"slug":646,"type":15},{"name":654,"slug":655,"type":15},"2026-05-10T05:59:52.971881",{"slug":835,"name":835,"fn":836,"description":837,"org":838,"tags":839,"stars":736,"repoUrl":737,"updatedAt":847},"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},[840,841,842,845,846],{"name":588,"slug":589,"type":15},{"name":828,"slug":829,"type":15},{"name":843,"slug":844,"type":15},"Documentation","documentation",{"name":816,"slug":809,"type":15},{"name":645,"slug":646,"type":15},"2026-05-16T06:07:47.821474",{"slug":849,"name":849,"fn":850,"description":851,"org":852,"tags":853,"stars":736,"repoUrl":737,"updatedAt":859},"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},[854,855,856,857,858],{"name":588,"slug":589,"type":15},{"name":816,"slug":809,"type":15},{"name":645,"slug":646,"type":15},{"name":654,"slug":655,"type":15},{"name":734,"slug":735,"type":15},"2026-05-16T06:07:40.583615",{"slug":861,"name":861,"fn":862,"description":863,"org":864,"tags":865,"stars":736,"repoUrl":737,"updatedAt":874},"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},[866,869,870,873],{"name":867,"slug":868,"type":15},"Animation","animation",{"name":769,"slug":770,"type":15},{"name":871,"slug":872,"type":15},"Creative","creative",{"name":588,"slug":589,"type":15},"2026-05-02T05:31:48.48485",{"slug":876,"name":876,"fn":877,"description":878,"org":879,"tags":880,"stars":736,"repoUrl":737,"updatedAt":890},"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},[881,882,883,886,889],{"name":871,"slug":872,"type":15},{"name":588,"slug":589,"type":15},{"name":884,"slug":885,"type":15},"Image Generation","image-generation",{"name":887,"slug":888,"type":15},"Images","images",{"name":9,"slug":8,"type":15},"2026-05-15T06:23:24.312127",675]