[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-openai-notion-spec-to-implementation":3,"mdc--rqkrrx-key":36,"related-repo-openai-notion-spec-to-implementation":654,"related-org-openai-notion-spec-to-implementation":778},{"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},"notion-spec-to-implementation","convert Notion specs into implementation plans","Turn Notion specs into implementation plans, tasks, and progress tracking; use when implementing PRDs\u002Ffeature specs and creating Notion plans + tasks from them.",{"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},"Project Management","project-management","tag",{"name":17,"slug":18,"type":15},"Notion","notion",{"name":20,"slug":21,"type":15},"Engineering","engineering",{"name":23,"slug":24,"type":15},"Task Management","task-management",3992,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins","2026-04-06T18:43:04.81501",null,465,[],{"repoUrl":26,"stars":25,"forks":29,"topics":32,"description":33},[],"OpenAI Plugins","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins\u002Ftree\u002FHEAD\u002Fplugins\u002Fnotion\u002Fskills\u002Fnotion-spec-to-implementation","---\nname: notion-spec-to-implementation\ndescription: Turn Notion specs into implementation plans, tasks, and progress tracking; use when implementing PRDs\u002Ffeature specs and creating Notion plans + tasks from them.\nmetadata:\n  short-description: Turn Notion specs into implementation plans, tasks, and progress tracking\n---\n\n# Spec to Implementation\n\nConvert a Notion spec into linked implementation plans, tasks, and ongoing status updates.\n\n## Quick start\n1) Locate the spec with `Notion:search`, then fetch it with `Notion:fetch`.\n2) Parse requirements and ambiguities using `reference\u002Fspec-parsing.md`.\n3) Create a plan page with `Notion:notion-create-pages` (pick a template: quick vs. full).\n4) Find the task database, confirm schema, then create tasks with `Notion:notion-create-pages`.\n5) Link spec ↔ plan ↔ tasks; keep status current with `Notion:notion-update-page`.\n\n## Tool-call guardrails\n- Notion tool availability can vary by workspace. If a Notion MCP call returns `Tool \u003Cname> not found`, treat that tool as unavailable for the rest of the current task. Do not retry it with different arguments or call it again later; use `Notion:search` and `Notion:fetch` where sufficient.\n- Use one literal search query per `Notion:search` call and include `filters: {}` when no narrower filter is needed. Run separate searches for alternate phrasings instead of putting `or` in a single query string.\n- Only send Notion page, database, or data-source URLs\u002FIDs to `Notion:fetch`; external connected-source search results are not fetch targets.\n- Create plans and task pages with explicit `parent` and `pages` fields. For task databases, fetch first and use the returned `collection:\u002F\u002F...` data source ID.\n- To append an implementation section to a spec, fetch the current section text first, then use `Notion:notion-update-page` with `command: \"update_content\"`, `properties: {}`, and exact `old_str` \u002F `new_str` content. For property-only edits, use `command: \"update_properties\"` with `content_updates: []`; the current deployed schema expects both top-level fields even when one is unused.\n\n## Workflow\n\n### 0) If Notion tools are unavailable, pause and ask the user to connect the Notion app:\n1. Enable the bundled Notion app for this plugin or session.\n2. Complete the Notion auth flow if Codex prompts for it.\n3. Restart Codex or the current session if the tools still do not appear.\n\nAfter the app is connected, finish your answer and tell the user to retry so they can continue with Step 1.\n\n### 1) Locate and read the spec\n- Search first (`Notion:search`); if multiple hits, ask the user which to use.\n- Fetch the page (`Notion:fetch`) and scan for requirements, acceptance criteria, constraints, and priorities. See `reference\u002Fspec-parsing.md` for extraction patterns.\n- Capture gaps\u002Fassumptions in a clarifications block before proceeding.\n\n### 2) Choose plan depth\n- Simple change → use `reference\u002Fquick-implementation-plan.md`.\n- Multi-phase feature\u002Fmigration → use `reference\u002Fstandard-implementation-plan.md`.\n- Create the plan via `Notion:notion-create-pages`, include: overview, linked spec, requirements summary, phases, dependencies\u002Frisks, and success criteria. Link back to the spec.\n\n### 3) Create tasks\n- Find the task database (`Notion:search` → `Notion:fetch` to confirm the data source and required properties). Patterns in `reference\u002Ftask-creation.md`.\n- Size tasks to 1–2 days. Use `reference\u002Ftask-creation-template.md` for content (context, objective, acceptance criteria, dependencies, resources).\n- Set properties: title\u002Faction verb, status, priority, relations to spec + plan, due date\u002Fstory points\u002Fassignee if provided.\n- Create pages with `Notion:notion-create-pages` using the database’s `data_source_id`.\n\n### 4) Link artifacts\n- Plan links to spec; tasks link to both plan and spec.\n- Optionally update the spec with a short “Implementation” section pointing to the plan and tasks using `Notion:notion-update-page`.\n\n### 5) Track progress\n- Use the cadence in `reference\u002Fprogress-tracking.md`.\n- Post updates with `reference\u002Fprogress-update-template.md`; close phases with `reference\u002Fmilestone-summary-template.md`.\n- Keep checklists and status fields in plan\u002Ftasks in sync; note blockers and decisions.\n\n## References and examples\n- `reference\u002F` — parsing patterns, plan\u002Ftask templates, progress cadence (e.g., `spec-parsing.md`, `standard-implementation-plan.md`, `task-creation.md`, `progress-tracking.md`).\n- `examples\u002F` — end-to-end walkthroughs (e.g., `ui-component.md`, `api-feature.md`, `database-migration.md`).\n",{"data":37,"body":40},{"name":4,"description":6,"metadata":38},{"short-description":39},"Turn Notion specs into implementation plans, tasks, and progress tracking",{"type":41,"children":42},"root",[43,52,58,65,140,146,304,310,317,335,340,346,385,391,430,436,502,508,527,533,573,579],{"type":44,"tag":45,"props":46,"children":48},"element","h1",{"id":47},"spec-to-implementation",[49],{"type":50,"value":51},"text","Spec to Implementation",{"type":44,"tag":53,"props":54,"children":55},"p",{},[56],{"type":50,"value":57},"Convert a Notion spec into linked implementation plans, tasks, and ongoing status updates.",{"type":44,"tag":59,"props":60,"children":62},"h2",{"id":61},"quick-start",[63],{"type":50,"value":64},"Quick start",{"type":44,"tag":66,"props":67,"children":68},"ol",{},[69,92,104,117,128],{"type":44,"tag":70,"props":71,"children":72},"li",{},[73,75,82,84,90],{"type":50,"value":74},"Locate the spec with ",{"type":44,"tag":76,"props":77,"children":79},"code",{"className":78},[],[80],{"type":50,"value":81},"Notion:search",{"type":50,"value":83},", then fetch it with ",{"type":44,"tag":76,"props":85,"children":87},{"className":86},[],[88],{"type":50,"value":89},"Notion:fetch",{"type":50,"value":91},".",{"type":44,"tag":70,"props":93,"children":94},{},[95,97,103],{"type":50,"value":96},"Parse requirements and ambiguities using ",{"type":44,"tag":76,"props":98,"children":100},{"className":99},[],[101],{"type":50,"value":102},"reference\u002Fspec-parsing.md",{"type":50,"value":91},{"type":44,"tag":70,"props":105,"children":106},{},[107,109,115],{"type":50,"value":108},"Create a plan page with ",{"type":44,"tag":76,"props":110,"children":112},{"className":111},[],[113],{"type":50,"value":114},"Notion:notion-create-pages",{"type":50,"value":116}," (pick a template: quick vs. full).",{"type":44,"tag":70,"props":118,"children":119},{},[120,122,127],{"type":50,"value":121},"Find the task database, confirm schema, then create tasks with ",{"type":44,"tag":76,"props":123,"children":125},{"className":124},[],[126],{"type":50,"value":114},{"type":50,"value":91},{"type":44,"tag":70,"props":129,"children":130},{},[131,133,139],{"type":50,"value":132},"Link spec ↔ plan ↔ tasks; keep status current with ",{"type":44,"tag":76,"props":134,"children":136},{"className":135},[],[137],{"type":50,"value":138},"Notion:notion-update-page",{"type":50,"value":91},{"type":44,"tag":59,"props":141,"children":143},{"id":142},"tool-call-guardrails",[144],{"type":50,"value":145},"Tool-call guardrails",{"type":44,"tag":147,"props":148,"children":149},"ul",{},[150,177,205,217,245],{"type":44,"tag":70,"props":151,"children":152},{},[153,155,161,163,168,170,175],{"type":50,"value":154},"Notion tool availability can vary by workspace. If a Notion MCP call returns ",{"type":44,"tag":76,"props":156,"children":158},{"className":157},[],[159],{"type":50,"value":160},"Tool \u003Cname> not found",{"type":50,"value":162},", treat that tool as unavailable for the rest of the current task. Do not retry it with different arguments or call it again later; use ",{"type":44,"tag":76,"props":164,"children":166},{"className":165},[],[167],{"type":50,"value":81},{"type":50,"value":169}," and ",{"type":44,"tag":76,"props":171,"children":173},{"className":172},[],[174],{"type":50,"value":89},{"type":50,"value":176}," where sufficient.",{"type":44,"tag":70,"props":178,"children":179},{},[180,182,187,189,195,197,203],{"type":50,"value":181},"Use one literal search query per ",{"type":44,"tag":76,"props":183,"children":185},{"className":184},[],[186],{"type":50,"value":81},{"type":50,"value":188}," call and include ",{"type":44,"tag":76,"props":190,"children":192},{"className":191},[],[193],{"type":50,"value":194},"filters: {}",{"type":50,"value":196}," when no narrower filter is needed. Run separate searches for alternate phrasings instead of putting ",{"type":44,"tag":76,"props":198,"children":200},{"className":199},[],[201],{"type":50,"value":202},"or",{"type":50,"value":204}," in a single query string.",{"type":44,"tag":70,"props":206,"children":207},{},[208,210,215],{"type":50,"value":209},"Only send Notion page, database, or data-source URLs\u002FIDs to ",{"type":44,"tag":76,"props":211,"children":213},{"className":212},[],[214],{"type":50,"value":89},{"type":50,"value":216},"; external connected-source search results are not fetch targets.",{"type":44,"tag":70,"props":218,"children":219},{},[220,222,228,229,235,237,243],{"type":50,"value":221},"Create plans and task pages with explicit ",{"type":44,"tag":76,"props":223,"children":225},{"className":224},[],[226],{"type":50,"value":227},"parent",{"type":50,"value":169},{"type":44,"tag":76,"props":230,"children":232},{"className":231},[],[233],{"type":50,"value":234},"pages",{"type":50,"value":236}," fields. For task databases, fetch first and use the returned ",{"type":44,"tag":76,"props":238,"children":240},{"className":239},[],[241],{"type":50,"value":242},"collection:\u002F\u002F...",{"type":50,"value":244}," data source ID.",{"type":44,"tag":70,"props":246,"children":247},{},[248,250,255,257,263,265,271,273,279,281,287,289,295,296,302],{"type":50,"value":249},"To append an implementation section to a spec, fetch the current section text first, then use ",{"type":44,"tag":76,"props":251,"children":253},{"className":252},[],[254],{"type":50,"value":138},{"type":50,"value":256}," with ",{"type":44,"tag":76,"props":258,"children":260},{"className":259},[],[261],{"type":50,"value":262},"command: \"update_content\"",{"type":50,"value":264},", ",{"type":44,"tag":76,"props":266,"children":268},{"className":267},[],[269],{"type":50,"value":270},"properties: {}",{"type":50,"value":272},", and exact ",{"type":44,"tag":76,"props":274,"children":276},{"className":275},[],[277],{"type":50,"value":278},"old_str",{"type":50,"value":280}," \u002F ",{"type":44,"tag":76,"props":282,"children":284},{"className":283},[],[285],{"type":50,"value":286},"new_str",{"type":50,"value":288}," content. For property-only edits, use ",{"type":44,"tag":76,"props":290,"children":292},{"className":291},[],[293],{"type":50,"value":294},"command: \"update_properties\"",{"type":50,"value":256},{"type":44,"tag":76,"props":297,"children":299},{"className":298},[],[300],{"type":50,"value":301},"content_updates: []",{"type":50,"value":303},"; the current deployed schema expects both top-level fields even when one is unused.",{"type":44,"tag":59,"props":305,"children":307},{"id":306},"workflow",[308],{"type":50,"value":309},"Workflow",{"type":44,"tag":311,"props":312,"children":314},"h3",{"id":313},"_0-if-notion-tools-are-unavailable-pause-and-ask-the-user-to-connect-the-notion-app",[315],{"type":50,"value":316},"0) If Notion tools are unavailable, pause and ask the user to connect the Notion app:",{"type":44,"tag":66,"props":318,"children":319},{},[320,325,330],{"type":44,"tag":70,"props":321,"children":322},{},[323],{"type":50,"value":324},"Enable the bundled Notion app for this plugin or session.",{"type":44,"tag":70,"props":326,"children":327},{},[328],{"type":50,"value":329},"Complete the Notion auth flow if Codex prompts for it.",{"type":44,"tag":70,"props":331,"children":332},{},[333],{"type":50,"value":334},"Restart Codex or the current session if the tools still do not appear.",{"type":44,"tag":53,"props":336,"children":337},{},[338],{"type":50,"value":339},"After the app is connected, finish your answer and tell the user to retry so they can continue with Step 1.",{"type":44,"tag":311,"props":341,"children":343},{"id":342},"_1-locate-and-read-the-spec",[344],{"type":50,"value":345},"1) Locate and read the spec",{"type":44,"tag":147,"props":347,"children":348},{},[349,361,380],{"type":44,"tag":70,"props":350,"children":351},{},[352,354,359],{"type":50,"value":353},"Search first (",{"type":44,"tag":76,"props":355,"children":357},{"className":356},[],[358],{"type":50,"value":81},{"type":50,"value":360},"); if multiple hits, ask the user which to use.",{"type":44,"tag":70,"props":362,"children":363},{},[364,366,371,373,378],{"type":50,"value":365},"Fetch the page (",{"type":44,"tag":76,"props":367,"children":369},{"className":368},[],[370],{"type":50,"value":89},{"type":50,"value":372},") and scan for requirements, acceptance criteria, constraints, and priorities. See ",{"type":44,"tag":76,"props":374,"children":376},{"className":375},[],[377],{"type":50,"value":102},{"type":50,"value":379}," for extraction patterns.",{"type":44,"tag":70,"props":381,"children":382},{},[383],{"type":50,"value":384},"Capture gaps\u002Fassumptions in a clarifications block before proceeding.",{"type":44,"tag":311,"props":386,"children":388},{"id":387},"_2-choose-plan-depth",[389],{"type":50,"value":390},"2) Choose plan depth",{"type":44,"tag":147,"props":392,"children":393},{},[394,406,418],{"type":44,"tag":70,"props":395,"children":396},{},[397,399,405],{"type":50,"value":398},"Simple change → use ",{"type":44,"tag":76,"props":400,"children":402},{"className":401},[],[403],{"type":50,"value":404},"reference\u002Fquick-implementation-plan.md",{"type":50,"value":91},{"type":44,"tag":70,"props":407,"children":408},{},[409,411,417],{"type":50,"value":410},"Multi-phase feature\u002Fmigration → use ",{"type":44,"tag":76,"props":412,"children":414},{"className":413},[],[415],{"type":50,"value":416},"reference\u002Fstandard-implementation-plan.md",{"type":50,"value":91},{"type":44,"tag":70,"props":419,"children":420},{},[421,423,428],{"type":50,"value":422},"Create the plan via ",{"type":44,"tag":76,"props":424,"children":426},{"className":425},[],[427],{"type":50,"value":114},{"type":50,"value":429},", include: overview, linked spec, requirements summary, phases, dependencies\u002Frisks, and success criteria. Link back to the spec.",{"type":44,"tag":311,"props":431,"children":433},{"id":432},"_3-create-tasks",[434],{"type":50,"value":435},"3) Create tasks",{"type":44,"tag":147,"props":437,"children":438},{},[439,465,478,483],{"type":44,"tag":70,"props":440,"children":441},{},[442,444,449,451,456,458,464],{"type":50,"value":443},"Find the task database (",{"type":44,"tag":76,"props":445,"children":447},{"className":446},[],[448],{"type":50,"value":81},{"type":50,"value":450}," → ",{"type":44,"tag":76,"props":452,"children":454},{"className":453},[],[455],{"type":50,"value":89},{"type":50,"value":457}," to confirm the data source and required properties). Patterns in ",{"type":44,"tag":76,"props":459,"children":461},{"className":460},[],[462],{"type":50,"value":463},"reference\u002Ftask-creation.md",{"type":50,"value":91},{"type":44,"tag":70,"props":466,"children":467},{},[468,470,476],{"type":50,"value":469},"Size tasks to 1–2 days. Use ",{"type":44,"tag":76,"props":471,"children":473},{"className":472},[],[474],{"type":50,"value":475},"reference\u002Ftask-creation-template.md",{"type":50,"value":477}," for content (context, objective, acceptance criteria, dependencies, resources).",{"type":44,"tag":70,"props":479,"children":480},{},[481],{"type":50,"value":482},"Set properties: title\u002Faction verb, status, priority, relations to spec + plan, due date\u002Fstory points\u002Fassignee if provided.",{"type":44,"tag":70,"props":484,"children":485},{},[486,488,493,495,501],{"type":50,"value":487},"Create pages with ",{"type":44,"tag":76,"props":489,"children":491},{"className":490},[],[492],{"type":50,"value":114},{"type":50,"value":494}," using the database’s ",{"type":44,"tag":76,"props":496,"children":498},{"className":497},[],[499],{"type":50,"value":500},"data_source_id",{"type":50,"value":91},{"type":44,"tag":311,"props":503,"children":505},{"id":504},"_4-link-artifacts",[506],{"type":50,"value":507},"4) Link artifacts",{"type":44,"tag":147,"props":509,"children":510},{},[511,516],{"type":44,"tag":70,"props":512,"children":513},{},[514],{"type":50,"value":515},"Plan links to spec; tasks link to both plan and spec.",{"type":44,"tag":70,"props":517,"children":518},{},[519,521,526],{"type":50,"value":520},"Optionally update the spec with a short “Implementation” section pointing to the plan and tasks using ",{"type":44,"tag":76,"props":522,"children":524},{"className":523},[],[525],{"type":50,"value":138},{"type":50,"value":91},{"type":44,"tag":311,"props":528,"children":530},{"id":529},"_5-track-progress",[531],{"type":50,"value":532},"5) Track progress",{"type":44,"tag":147,"props":534,"children":535},{},[536,548,568],{"type":44,"tag":70,"props":537,"children":538},{},[539,541,547],{"type":50,"value":540},"Use the cadence in ",{"type":44,"tag":76,"props":542,"children":544},{"className":543},[],[545],{"type":50,"value":546},"reference\u002Fprogress-tracking.md",{"type":50,"value":91},{"type":44,"tag":70,"props":549,"children":550},{},[551,553,559,561,567],{"type":50,"value":552},"Post updates with ",{"type":44,"tag":76,"props":554,"children":556},{"className":555},[],[557],{"type":50,"value":558},"reference\u002Fprogress-update-template.md",{"type":50,"value":560},"; close phases with ",{"type":44,"tag":76,"props":562,"children":564},{"className":563},[],[565],{"type":50,"value":566},"reference\u002Fmilestone-summary-template.md",{"type":50,"value":91},{"type":44,"tag":70,"props":569,"children":570},{},[571],{"type":50,"value":572},"Keep checklists and status fields in plan\u002Ftasks in sync; note blockers and decisions.",{"type":44,"tag":59,"props":574,"children":576},{"id":575},"references-and-examples",[577],{"type":50,"value":578},"References and examples",{"type":44,"tag":147,"props":580,"children":581},{},[582,622],{"type":44,"tag":70,"props":583,"children":584},{},[585,591,593,599,600,606,607,613,614,620],{"type":44,"tag":76,"props":586,"children":588},{"className":587},[],[589],{"type":50,"value":590},"reference\u002F",{"type":50,"value":592}," — parsing patterns, plan\u002Ftask templates, progress cadence (e.g., ",{"type":44,"tag":76,"props":594,"children":596},{"className":595},[],[597],{"type":50,"value":598},"spec-parsing.md",{"type":50,"value":264},{"type":44,"tag":76,"props":601,"children":603},{"className":602},[],[604],{"type":50,"value":605},"standard-implementation-plan.md",{"type":50,"value":264},{"type":44,"tag":76,"props":608,"children":610},{"className":609},[],[611],{"type":50,"value":612},"task-creation.md",{"type":50,"value":264},{"type":44,"tag":76,"props":615,"children":617},{"className":616},[],[618],{"type":50,"value":619},"progress-tracking.md",{"type":50,"value":621},").",{"type":44,"tag":70,"props":623,"children":624},{},[625,631,633,639,640,646,647,653],{"type":44,"tag":76,"props":626,"children":628},{"className":627},[],[629],{"type":50,"value":630},"examples\u002F",{"type":50,"value":632}," — end-to-end walkthroughs (e.g., ",{"type":44,"tag":76,"props":634,"children":636},{"className":635},[],[637],{"type":50,"value":638},"ui-component.md",{"type":50,"value":264},{"type":44,"tag":76,"props":641,"children":643},{"className":642},[],[644],{"type":50,"value":645},"api-feature.md",{"type":50,"value":264},{"type":44,"tag":76,"props":648,"children":650},{"className":649},[],[651],{"type":50,"value":652},"database-migration.md",{"type":50,"value":621},{"items":655,"total":777},[656,675,691,703,723,745,765],{"slug":657,"name":657,"fn":658,"description":659,"org":660,"tags":661,"stars":25,"repoUrl":26,"updatedAt":674},"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},[662,665,668,671],{"name":663,"slug":664,"type":15},"Accessibility","accessibility",{"name":666,"slug":667,"type":15},"Charts","charts",{"name":669,"slug":670,"type":15},"Data Visualization","data-visualization",{"name":672,"slug":673,"type":15},"Design","design","2026-06-30T19:00:57.102",{"slug":676,"name":676,"fn":677,"description":678,"org":679,"tags":680,"stars":25,"repoUrl":26,"updatedAt":690},"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},[681,684,687],{"name":682,"slug":683,"type":15},"Agents","agents",{"name":685,"slug":686,"type":15},"Browser Automation","browser-automation",{"name":688,"slug":689,"type":15},"Testing","testing","2026-04-06T18:41:03.44016",{"slug":692,"name":692,"fn":693,"description":694,"org":695,"tags":696,"stars":25,"repoUrl":26,"updatedAt":702},"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},[697,698,701],{"name":685,"slug":686,"type":15},{"name":699,"slug":700,"type":15},"Local Development","local-development",{"name":688,"slug":689,"type":15},"2026-04-06T18:41:17.526867",{"slug":704,"name":704,"fn":705,"description":706,"org":707,"tags":708,"stars":25,"repoUrl":26,"updatedAt":722},"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},[709,710,713,716,719],{"name":682,"slug":683,"type":15},{"name":711,"slug":712,"type":15},"Cloudflare Workers","cloudflare-workers",{"name":714,"slug":715,"type":15},"SDK","sdk",{"name":717,"slug":718,"type":15},"Serverless","serverless",{"name":720,"slug":721,"type":15},"WebSockets","websockets","2026-04-06T18:39:51.717063",{"slug":724,"name":724,"fn":725,"description":726,"org":727,"tags":728,"stars":25,"repoUrl":26,"updatedAt":744},"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},[729,732,735,738,741],{"name":730,"slug":731,"type":15},"Frontend","frontend",{"name":733,"slug":734,"type":15},"React","react",{"name":736,"slug":737,"type":15},"shadcn\u002Fui","shadcn-ui",{"name":739,"slug":740,"type":15},"UI Components","ui-components",{"name":742,"slug":743,"type":15},"Vercel","vercel","2026-04-06T18:40:59.619419",{"slug":746,"name":746,"fn":747,"description":748,"org":749,"tags":750,"stars":25,"repoUrl":26,"updatedAt":764},"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},[751,754,757,760,763],{"name":752,"slug":753,"type":15},"AI Infrastructure","ai-infrastructure",{"name":755,"slug":756,"type":15},"Cost Optimization","cost-optimization",{"name":758,"slug":759,"type":15},"LLM","llm",{"name":761,"slug":762,"type":15},"Performance","performance",{"name":742,"slug":743,"type":15},"2026-04-06T18:40:44.377464",{"slug":766,"name":766,"fn":767,"description":768,"org":769,"tags":770,"stars":25,"repoUrl":26,"updatedAt":776},"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},[771,772,775],{"name":755,"slug":756,"type":15},{"name":773,"slug":774,"type":15},"Database","database",{"name":758,"slug":759,"type":15},"2026-04-06T18:41:08.513425",600,{"items":779,"total":972},[780,801,824,841,857,874,889,901,915,929,941,956],{"slug":781,"name":781,"fn":782,"description":783,"org":784,"tags":785,"stars":798,"repoUrl":799,"updatedAt":800},"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},[786,789,792,795],{"name":787,"slug":788,"type":15},"Documents","documents",{"name":790,"slug":791,"type":15},"Healthcare","healthcare",{"name":793,"slug":794,"type":15},"Insurance","insurance",{"name":796,"slug":797,"type":15},"Regulatory Compliance","regulatory-compliance",28169,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fopenai-agents-python","2026-04-16T05:11:39.180399",{"slug":802,"name":802,"fn":803,"description":804,"org":805,"tags":806,"stars":821,"repoUrl":822,"updatedAt":823},"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},[807,810,812,815,818],{"name":808,"slug":809,"type":15},".NET","dotnet",{"name":811,"slug":802,"type":15},"ASP.NET Core",{"name":813,"slug":814,"type":15},"Blazor","blazor",{"name":816,"slug":817,"type":15},"C#","csharp",{"name":819,"slug":820,"type":15},"Web Development","web-development",23787,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fskills","2026-04-12T05:07:02.819491",{"slug":825,"name":825,"fn":826,"description":827,"org":828,"tags":829,"stars":821,"repoUrl":822,"updatedAt":840},"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},[830,833,836,839],{"name":831,"slug":832,"type":15},"Apps SDK","apps-sdk",{"name":834,"slug":835,"type":15},"ChatGPT","chatgpt",{"name":837,"slug":838,"type":15},"MCP","mcp",{"name":9,"slug":8,"type":15},"2026-04-12T05:07:05.468097",{"slug":842,"name":842,"fn":843,"description":844,"org":845,"tags":846,"stars":821,"repoUrl":822,"updatedAt":856},"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},[847,850,853],{"name":848,"slug":849,"type":15},"API Development","api-development",{"name":851,"slug":852,"type":15},"CLI","cli",{"name":854,"slug":855,"type":15},"Codex","codex","2026-04-12T05:07:04.132762",{"slug":858,"name":858,"fn":859,"description":860,"org":861,"tags":862,"stars":821,"repoUrl":822,"updatedAt":873},"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},[863,866,869,870],{"name":864,"slug":865,"type":15},"Cloudflare","cloudflare",{"name":867,"slug":868,"type":15},"Cloudflare Pages","cloudflare-pages",{"name":711,"slug":712,"type":15},{"name":871,"slug":872,"type":15},"Deployment","deployment","2026-04-12T05:07:14.275118",{"slug":875,"name":875,"fn":876,"description":877,"org":878,"tags":879,"stars":821,"repoUrl":822,"updatedAt":888},"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},[880,883,884,887],{"name":881,"slug":882,"type":15},"Productivity","productivity",{"name":13,"slug":14,"type":15},{"name":885,"slug":886,"type":15},"Strategy","strategy",{"name":23,"slug":24,"type":15},"2026-05-23T06:17:16.870838",{"slug":890,"name":890,"fn":891,"description":892,"org":893,"tags":894,"stars":821,"repoUrl":822,"updatedAt":900},"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},[895,896,898,899],{"name":672,"slug":673,"type":15},{"name":897,"slug":890,"type":15},"Figma",{"name":730,"slug":731,"type":15},{"name":837,"slug":838,"type":15},"2026-04-12T05:06:47.939943",{"slug":902,"name":902,"fn":903,"description":904,"org":905,"tags":906,"stars":821,"repoUrl":822,"updatedAt":914},"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},[907,908,911,912,913],{"name":672,"slug":673,"type":15},{"name":909,"slug":910,"type":15},"Design System","design-system",{"name":897,"slug":890,"type":15},{"name":730,"slug":731,"type":15},{"name":739,"slug":740,"type":15},"2026-05-10T05:59:52.971881",{"slug":916,"name":916,"fn":917,"description":918,"org":919,"tags":920,"stars":821,"repoUrl":822,"updatedAt":928},"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},[921,922,923,926,927],{"name":672,"slug":673,"type":15},{"name":909,"slug":910,"type":15},{"name":924,"slug":925,"type":15},"Documentation","documentation",{"name":897,"slug":890,"type":15},{"name":730,"slug":731,"type":15},"2026-05-16T06:07:47.821474",{"slug":930,"name":930,"fn":931,"description":932,"org":933,"tags":934,"stars":821,"repoUrl":822,"updatedAt":940},"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},[935,936,937,938,939],{"name":672,"slug":673,"type":15},{"name":897,"slug":890,"type":15},{"name":730,"slug":731,"type":15},{"name":739,"slug":740,"type":15},{"name":819,"slug":820,"type":15},"2026-05-16T06:07:40.583615",{"slug":942,"name":942,"fn":943,"description":944,"org":945,"tags":946,"stars":821,"repoUrl":822,"updatedAt":955},"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},[947,950,951,954],{"name":948,"slug":949,"type":15},"Animation","animation",{"name":854,"slug":855,"type":15},{"name":952,"slug":953,"type":15},"Creative","creative",{"name":672,"slug":673,"type":15},"2026-05-02T05:31:48.48485",{"slug":957,"name":957,"fn":958,"description":959,"org":960,"tags":961,"stars":821,"repoUrl":822,"updatedAt":971},"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},[962,963,964,967,970],{"name":952,"slug":953,"type":15},{"name":672,"slug":673,"type":15},{"name":965,"slug":966,"type":15},"Image Generation","image-generation",{"name":968,"slug":969,"type":15},"Images","images",{"name":9,"slug":8,"type":15},"2026-05-15T06:23:24.312127",675]