[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-openai-security-threat-model":3,"mdc-mutn3r-key":33,"related-repo-openai-security-threat-model":426,"related-org-openai-security-threat-model":553},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":22,"repoUrl":23,"updatedAt":24,"license":25,"forks":26,"topics":27,"repo":28,"sourceUrl":31,"mdContent":32},"security-threat-model","build repository-grounded threat models","Repository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, and writes a concise Markdown threat model. Trigger only when the user explicitly asks to threat model a codebase or path, enumerate threats\u002Fabuse paths, or perform AppSec threat modeling. Do not trigger for general architecture summaries, code review, or non-security design work.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},"openai","OpenAI","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fopenai.png",[12,16,19],{"name":13,"slug":14,"type":15},"Security","security","tag",{"name":17,"slug":18,"type":15},"Threat Modeling","threat-modeling",{"name":20,"slug":21,"type":15},"Risk Assessment","risk-assessment",23787,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fskills","2026-04-12T05:07:17.835598",null,1614,[],{"repoUrl":23,"stars":22,"forks":26,"topics":29,"description":30},[],"Skills Catalog for Codex","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fskills\u002Ftree\u002FHEAD\u002Fskills\u002F.curated\u002Fsecurity-threat-model","---\nname: \"security-threat-model\"\ndescription: \"Repository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, and writes a concise Markdown threat model. Trigger only when the user explicitly asks to threat model a codebase or path, enumerate threats\u002Fabuse paths, or perform AppSec threat modeling. Do not trigger for general architecture summaries, code review, or non-security design work.\"\n---\n\n# Threat Model Source Code Repo\n\nDeliver an actionable AppSec-grade threat model that is specific to the repository or a project path, not a generic checklist. Anchor every architectural claim to evidence in the repo and keep assumptions explicit. Prioritizing realistic attacker goals and concrete impacts over generic checklists.\n\n## Quick start\n\n1) Collect (or infer) inputs:\n- Repo root path and any in-scope paths.\n- Intended usage, deployment model, internet exposure, and auth expectations (if known).\n- Any existing repository summary or architecture spec.\n- Use prompts in `references\u002Fprompt-template.md` to generate a repository summary.\n- Follow the required output contract in `references\u002Fprompt-template.md`. Use it verbatim when possible.\n\n## Workflow\n\n### 1) Scope and extract the system model\n- Identify primary components, data stores, and external integrations from the repo summary.\n- Identify how the system runs (server, CLI, library, worker) and its entrypoints.\n- Separate runtime behavior from CI\u002Fbuild\u002Fdev tooling and from tests\u002Fexamples.\n- Map the in-scope locations to those components and exclude out-of-scope items explicitly.\n- Do not claim components, flows, or controls without evidence.\n\n### 2) Derive boundaries, assets, and entry points\n- Enumerate trust boundaries as concrete edges between components, noting protocol, auth, encryption, validation, and rate limiting.\n- List assets that drive risk (data, credentials, models, config, compute resources, audit logs).\n- Identify entry points (endpoints, upload surfaces, parsers\u002Fdecoders, job triggers, admin tooling, logging\u002Ferror sinks).\n\n### 3) Calibrate assets and attacker capabilities\n- List the assets that drive risk (credentials, PII, integrity-critical state, availability-critical components, build artifacts).\n- Describe realistic attacker capabilities based on exposure and intended usage.\n- Explicitly note non-capabilities to avoid inflated severity.\n\n\n### 4) Enumerate threats as abuse paths\n- Prefer attacker goals that map to assets and boundaries (exfiltration, privilege escalation, integrity compromise, denial of service).\n- Classify each threat and tie it to impacted assets.\n- Keep the number of threats small but high quality.\n\n### 5) Prioritize with explicit likelihood and impact reasoning\n- Use qualitative likelihood and impact (low\u002Fmedium\u002Fhigh) with short justifications.\n- Set overall priority (critical\u002Fhigh\u002Fmedium\u002Flow) using likelihood x impact, adjusted for existing controls.\n- State which assumptions most influence the ranking.\n\n### 6) Validate service context and assumptions with the user\n- Summarize key assumptions that materially affect threat ranking or scope, then ask the user to confirm or correct them.\n- Ask 1–3 targeted questions to resolve missing context (service owner and environment, scale\u002Fusers, deployment model, authn\u002Fauthz, internet exposure, data sensitivity, multi-tenancy).\n- Pause and wait for user feedback before producing the final report.\n- If the user declines or can’t answer, state which assumptions remain and how they influence priority.\n\n### 7) Recommend mitigations and focus paths\n- Distinguish existing mitigations (with evidence) from recommended mitigations.\n- Tie mitigations to concrete locations (component, boundary, or entry point) and control types (authZ checks, input validation, schema enforcement, sandboxing, rate limits, secrets isolation, audit logging).\n- Prefer specific implementation hints over generic advice (e.g., \"enforce schema at gateway for upload payloads\" vs \"validate inputs\").\n- Base recommendations on validated user context; if assumptions remain unresolved, mark recommendations as conditional.\n\n### 8) Run a quality check before finalizing\n- Confirm all discovered entrypoints are covered.\n- Confirm each trust boundary is represented in threats.\n- Confirm runtime vs CI\u002Fdev separation.\n- Confirm user clarifications (or explicit non-responses) are reflected.\n- Confirm assumptions and open questions are explicit.\n- Confirm that the format of the report matches closely the required output format defined in prompt template: `references\u002Fprompt-template.md`\n- Write the final Markdown to a file named `\u003Crepo-or-dir-name>-threat-model.md` (use the basename of the repo root, or the in-scope directory if you were asked to model a subpath).\n\n\n## Risk prioritization guidance (illustrative, not exhaustive)\n- High: pre-auth RCE, auth bypass, cross-tenant access, sensitive data exfiltration, key or token theft, model or config integrity compromise, sandbox escape.\n- Medium: targeted DoS of critical components, partial data exposure, rate-limit bypass with measurable impact, log\u002Fmetrics poisoning that affects detection.\n- Low: low-sensitivity info leaks, noisy DoS with easy mitigation, issues requiring unlikely preconditions.\n\n## References\n\n- Output contract and full prompt template: `references\u002Fprompt-template.md`\n- Optional controls\u002Fasset list: `references\u002Fsecurity-controls-and-assets.md`\n\nOnly load the reference files you need. Keep the final result concise, grounded, and reviewable.\n",{"data":34,"body":35},{"name":4,"description":6},{"type":36,"children":37},"root",[38,47,53,60,70,115,121,128,156,162,180,186,204,210,228,234,252,258,281,287,310,316,367,373,391,397,421],{"type":39,"tag":40,"props":41,"children":43},"element","h1",{"id":42},"threat-model-source-code-repo",[44],{"type":45,"value":46},"text","Threat Model Source Code Repo",{"type":39,"tag":48,"props":49,"children":50},"p",{},[51],{"type":45,"value":52},"Deliver an actionable AppSec-grade threat model that is specific to the repository or a project path, not a generic checklist. Anchor every architectural claim to evidence in the repo and keep assumptions explicit. Prioritizing realistic attacker goals and concrete impacts over generic checklists.",{"type":39,"tag":54,"props":55,"children":57},"h2",{"id":56},"quick-start",[58],{"type":45,"value":59},"Quick start",{"type":39,"tag":61,"props":62,"children":63},"ol",{},[64],{"type":39,"tag":65,"props":66,"children":67},"li",{},[68],{"type":45,"value":69},"Collect (or infer) inputs:",{"type":39,"tag":71,"props":72,"children":73},"ul",{},[74,79,84,89,103],{"type":39,"tag":65,"props":75,"children":76},{},[77],{"type":45,"value":78},"Repo root path and any in-scope paths.",{"type":39,"tag":65,"props":80,"children":81},{},[82],{"type":45,"value":83},"Intended usage, deployment model, internet exposure, and auth expectations (if known).",{"type":39,"tag":65,"props":85,"children":86},{},[87],{"type":45,"value":88},"Any existing repository summary or architecture spec.",{"type":39,"tag":65,"props":90,"children":91},{},[92,94,101],{"type":45,"value":93},"Use prompts in ",{"type":39,"tag":95,"props":96,"children":98},"code",{"className":97},[],[99],{"type":45,"value":100},"references\u002Fprompt-template.md",{"type":45,"value":102}," to generate a repository summary.",{"type":39,"tag":65,"props":104,"children":105},{},[106,108,113],{"type":45,"value":107},"Follow the required output contract in ",{"type":39,"tag":95,"props":109,"children":111},{"className":110},[],[112],{"type":45,"value":100},{"type":45,"value":114},". Use it verbatim when possible.",{"type":39,"tag":54,"props":116,"children":118},{"id":117},"workflow",[119],{"type":45,"value":120},"Workflow",{"type":39,"tag":122,"props":123,"children":125},"h3",{"id":124},"_1-scope-and-extract-the-system-model",[126],{"type":45,"value":127},"1) Scope and extract the system model",{"type":39,"tag":71,"props":129,"children":130},{},[131,136,141,146,151],{"type":39,"tag":65,"props":132,"children":133},{},[134],{"type":45,"value":135},"Identify primary components, data stores, and external integrations from the repo summary.",{"type":39,"tag":65,"props":137,"children":138},{},[139],{"type":45,"value":140},"Identify how the system runs (server, CLI, library, worker) and its entrypoints.",{"type":39,"tag":65,"props":142,"children":143},{},[144],{"type":45,"value":145},"Separate runtime behavior from CI\u002Fbuild\u002Fdev tooling and from tests\u002Fexamples.",{"type":39,"tag":65,"props":147,"children":148},{},[149],{"type":45,"value":150},"Map the in-scope locations to those components and exclude out-of-scope items explicitly.",{"type":39,"tag":65,"props":152,"children":153},{},[154],{"type":45,"value":155},"Do not claim components, flows, or controls without evidence.",{"type":39,"tag":122,"props":157,"children":159},{"id":158},"_2-derive-boundaries-assets-and-entry-points",[160],{"type":45,"value":161},"2) Derive boundaries, assets, and entry points",{"type":39,"tag":71,"props":163,"children":164},{},[165,170,175],{"type":39,"tag":65,"props":166,"children":167},{},[168],{"type":45,"value":169},"Enumerate trust boundaries as concrete edges between components, noting protocol, auth, encryption, validation, and rate limiting.",{"type":39,"tag":65,"props":171,"children":172},{},[173],{"type":45,"value":174},"List assets that drive risk (data, credentials, models, config, compute resources, audit logs).",{"type":39,"tag":65,"props":176,"children":177},{},[178],{"type":45,"value":179},"Identify entry points (endpoints, upload surfaces, parsers\u002Fdecoders, job triggers, admin tooling, logging\u002Ferror sinks).",{"type":39,"tag":122,"props":181,"children":183},{"id":182},"_3-calibrate-assets-and-attacker-capabilities",[184],{"type":45,"value":185},"3) Calibrate assets and attacker capabilities",{"type":39,"tag":71,"props":187,"children":188},{},[189,194,199],{"type":39,"tag":65,"props":190,"children":191},{},[192],{"type":45,"value":193},"List the assets that drive risk (credentials, PII, integrity-critical state, availability-critical components, build artifacts).",{"type":39,"tag":65,"props":195,"children":196},{},[197],{"type":45,"value":198},"Describe realistic attacker capabilities based on exposure and intended usage.",{"type":39,"tag":65,"props":200,"children":201},{},[202],{"type":45,"value":203},"Explicitly note non-capabilities to avoid inflated severity.",{"type":39,"tag":122,"props":205,"children":207},{"id":206},"_4-enumerate-threats-as-abuse-paths",[208],{"type":45,"value":209},"4) Enumerate threats as abuse paths",{"type":39,"tag":71,"props":211,"children":212},{},[213,218,223],{"type":39,"tag":65,"props":214,"children":215},{},[216],{"type":45,"value":217},"Prefer attacker goals that map to assets and boundaries (exfiltration, privilege escalation, integrity compromise, denial of service).",{"type":39,"tag":65,"props":219,"children":220},{},[221],{"type":45,"value":222},"Classify each threat and tie it to impacted assets.",{"type":39,"tag":65,"props":224,"children":225},{},[226],{"type":45,"value":227},"Keep the number of threats small but high quality.",{"type":39,"tag":122,"props":229,"children":231},{"id":230},"_5-prioritize-with-explicit-likelihood-and-impact-reasoning",[232],{"type":45,"value":233},"5) Prioritize with explicit likelihood and impact reasoning",{"type":39,"tag":71,"props":235,"children":236},{},[237,242,247],{"type":39,"tag":65,"props":238,"children":239},{},[240],{"type":45,"value":241},"Use qualitative likelihood and impact (low\u002Fmedium\u002Fhigh) with short justifications.",{"type":39,"tag":65,"props":243,"children":244},{},[245],{"type":45,"value":246},"Set overall priority (critical\u002Fhigh\u002Fmedium\u002Flow) using likelihood x impact, adjusted for existing controls.",{"type":39,"tag":65,"props":248,"children":249},{},[250],{"type":45,"value":251},"State which assumptions most influence the ranking.",{"type":39,"tag":122,"props":253,"children":255},{"id":254},"_6-validate-service-context-and-assumptions-with-the-user",[256],{"type":45,"value":257},"6) Validate service context and assumptions with the user",{"type":39,"tag":71,"props":259,"children":260},{},[261,266,271,276],{"type":39,"tag":65,"props":262,"children":263},{},[264],{"type":45,"value":265},"Summarize key assumptions that materially affect threat ranking or scope, then ask the user to confirm or correct them.",{"type":39,"tag":65,"props":267,"children":268},{},[269],{"type":45,"value":270},"Ask 1–3 targeted questions to resolve missing context (service owner and environment, scale\u002Fusers, deployment model, authn\u002Fauthz, internet exposure, data sensitivity, multi-tenancy).",{"type":39,"tag":65,"props":272,"children":273},{},[274],{"type":45,"value":275},"Pause and wait for user feedback before producing the final report.",{"type":39,"tag":65,"props":277,"children":278},{},[279],{"type":45,"value":280},"If the user declines or can’t answer, state which assumptions remain and how they influence priority.",{"type":39,"tag":122,"props":282,"children":284},{"id":283},"_7-recommend-mitigations-and-focus-paths",[285],{"type":45,"value":286},"7) Recommend mitigations and focus paths",{"type":39,"tag":71,"props":288,"children":289},{},[290,295,300,305],{"type":39,"tag":65,"props":291,"children":292},{},[293],{"type":45,"value":294},"Distinguish existing mitigations (with evidence) from recommended mitigations.",{"type":39,"tag":65,"props":296,"children":297},{},[298],{"type":45,"value":299},"Tie mitigations to concrete locations (component, boundary, or entry point) and control types (authZ checks, input validation, schema enforcement, sandboxing, rate limits, secrets isolation, audit logging).",{"type":39,"tag":65,"props":301,"children":302},{},[303],{"type":45,"value":304},"Prefer specific implementation hints over generic advice (e.g., \"enforce schema at gateway for upload payloads\" vs \"validate inputs\").",{"type":39,"tag":65,"props":306,"children":307},{},[308],{"type":45,"value":309},"Base recommendations on validated user context; if assumptions remain unresolved, mark recommendations as conditional.",{"type":39,"tag":122,"props":311,"children":313},{"id":312},"_8-run-a-quality-check-before-finalizing",[314],{"type":45,"value":315},"8) Run a quality check before finalizing",{"type":39,"tag":71,"props":317,"children":318},{},[319,324,329,334,339,344,354],{"type":39,"tag":65,"props":320,"children":321},{},[322],{"type":45,"value":323},"Confirm all discovered entrypoints are covered.",{"type":39,"tag":65,"props":325,"children":326},{},[327],{"type":45,"value":328},"Confirm each trust boundary is represented in threats.",{"type":39,"tag":65,"props":330,"children":331},{},[332],{"type":45,"value":333},"Confirm runtime vs CI\u002Fdev separation.",{"type":39,"tag":65,"props":335,"children":336},{},[337],{"type":45,"value":338},"Confirm user clarifications (or explicit non-responses) are reflected.",{"type":39,"tag":65,"props":340,"children":341},{},[342],{"type":45,"value":343},"Confirm assumptions and open questions are explicit.",{"type":39,"tag":65,"props":345,"children":346},{},[347,349],{"type":45,"value":348},"Confirm that the format of the report matches closely the required output format defined in prompt template: ",{"type":39,"tag":95,"props":350,"children":352},{"className":351},[],[353],{"type":45,"value":100},{"type":39,"tag":65,"props":355,"children":356},{},[357,359,365],{"type":45,"value":358},"Write the final Markdown to a file named ",{"type":39,"tag":95,"props":360,"children":362},{"className":361},[],[363],{"type":45,"value":364},"\u003Crepo-or-dir-name>-threat-model.md",{"type":45,"value":366}," (use the basename of the repo root, or the in-scope directory if you were asked to model a subpath).",{"type":39,"tag":54,"props":368,"children":370},{"id":369},"risk-prioritization-guidance-illustrative-not-exhaustive",[371],{"type":45,"value":372},"Risk prioritization guidance (illustrative, not exhaustive)",{"type":39,"tag":71,"props":374,"children":375},{},[376,381,386],{"type":39,"tag":65,"props":377,"children":378},{},[379],{"type":45,"value":380},"High: pre-auth RCE, auth bypass, cross-tenant access, sensitive data exfiltration, key or token theft, model or config integrity compromise, sandbox escape.",{"type":39,"tag":65,"props":382,"children":383},{},[384],{"type":45,"value":385},"Medium: targeted DoS of critical components, partial data exposure, rate-limit bypass with measurable impact, log\u002Fmetrics poisoning that affects detection.",{"type":39,"tag":65,"props":387,"children":388},{},[389],{"type":45,"value":390},"Low: low-sensitivity info leaks, noisy DoS with easy mitigation, issues requiring unlikely preconditions.",{"type":39,"tag":54,"props":392,"children":394},{"id":393},"references",[395],{"type":45,"value":396},"References",{"type":39,"tag":71,"props":398,"children":399},{},[400,410],{"type":39,"tag":65,"props":401,"children":402},{},[403,405],{"type":45,"value":404},"Output contract and full prompt template: ",{"type":39,"tag":95,"props":406,"children":408},{"className":407},[],[409],{"type":45,"value":100},{"type":39,"tag":65,"props":411,"children":412},{},[413,415],{"type":45,"value":414},"Optional controls\u002Fasset list: ",{"type":39,"tag":95,"props":416,"children":418},{"className":417},[],[419],{"type":45,"value":420},"references\u002Fsecurity-controls-and-assets.md",{"type":39,"tag":48,"props":422,"children":423},{},[424],{"type":45,"value":425},"Only load the reference files you need. Keep the final result concise, grounded, and reviewable.",{"items":427,"total":552},[428,449,466,482,501,520,536],{"slug":429,"name":429,"fn":430,"description":431,"org":432,"tags":433,"stars":22,"repoUrl":23,"updatedAt":448},"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},[434,437,439,442,445],{"name":435,"slug":436,"type":15},".NET","dotnet",{"name":438,"slug":429,"type":15},"ASP.NET Core",{"name":440,"slug":441,"type":15},"Blazor","blazor",{"name":443,"slug":444,"type":15},"C#","csharp",{"name":446,"slug":447,"type":15},"Web Development","web-development","2026-04-12T05:07:02.819491",{"slug":450,"name":450,"fn":451,"description":452,"org":453,"tags":454,"stars":22,"repoUrl":23,"updatedAt":465},"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},[455,458,461,464],{"name":456,"slug":457,"type":15},"Apps SDK","apps-sdk",{"name":459,"slug":460,"type":15},"ChatGPT","chatgpt",{"name":462,"slug":463,"type":15},"MCP","mcp",{"name":9,"slug":8,"type":15},"2026-04-12T05:07:05.468097",{"slug":467,"name":467,"fn":468,"description":469,"org":470,"tags":471,"stars":22,"repoUrl":23,"updatedAt":481},"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},[472,475,478],{"name":473,"slug":474,"type":15},"API Development","api-development",{"name":476,"slug":477,"type":15},"CLI","cli",{"name":479,"slug":480,"type":15},"Codex","codex","2026-04-12T05:07:04.132762",{"slug":483,"name":483,"fn":484,"description":485,"org":486,"tags":487,"stars":22,"repoUrl":23,"updatedAt":500},"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},[488,491,494,497],{"name":489,"slug":490,"type":15},"Cloudflare","cloudflare",{"name":492,"slug":493,"type":15},"Cloudflare Pages","cloudflare-pages",{"name":495,"slug":496,"type":15},"Cloudflare Workers","cloudflare-workers",{"name":498,"slug":499,"type":15},"Deployment","deployment","2026-04-12T05:07:14.275118",{"slug":502,"name":502,"fn":503,"description":504,"org":505,"tags":506,"stars":22,"repoUrl":23,"updatedAt":519},"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},[507,510,513,516],{"name":508,"slug":509,"type":15},"Productivity","productivity",{"name":511,"slug":512,"type":15},"Project Management","project-management",{"name":514,"slug":515,"type":15},"Strategy","strategy",{"name":517,"slug":518,"type":15},"Task Management","task-management","2026-05-23T06:17:16.870838",{"slug":521,"name":521,"fn":522,"description":523,"org":524,"tags":525,"stars":22,"repoUrl":23,"updatedAt":535},"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},[526,529,531,534],{"name":527,"slug":528,"type":15},"Design","design",{"name":530,"slug":521,"type":15},"Figma",{"name":532,"slug":533,"type":15},"Frontend","frontend",{"name":462,"slug":463,"type":15},"2026-04-12T05:06:47.939943",{"slug":537,"name":537,"fn":538,"description":539,"org":540,"tags":541,"stars":22,"repoUrl":23,"updatedAt":551},"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},[542,543,546,547,548],{"name":527,"slug":528,"type":15},{"name":544,"slug":545,"type":15},"Design System","design-system",{"name":530,"slug":521,"type":15},{"name":532,"slug":533,"type":15},{"name":549,"slug":550,"type":15},"UI Components","ui-components","2026-05-10T05:59:52.971881",29,{"items":554,"total":683},[555,576,584,591,597,604,611,618,626,640,652,667],{"slug":556,"name":556,"fn":557,"description":558,"org":559,"tags":560,"stars":573,"repoUrl":574,"updatedAt":575},"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},[561,564,567,570],{"name":562,"slug":563,"type":15},"Documents","documents",{"name":565,"slug":566,"type":15},"Healthcare","healthcare",{"name":568,"slug":569,"type":15},"Insurance","insurance",{"name":571,"slug":572,"type":15},"Regulatory Compliance","regulatory-compliance",28169,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fopenai-agents-python","2026-04-16T05:11:39.180399",{"slug":429,"name":429,"fn":430,"description":431,"org":577,"tags":578,"stars":22,"repoUrl":23,"updatedAt":448},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[579,580,581,582,583],{"name":435,"slug":436,"type":15},{"name":438,"slug":429,"type":15},{"name":440,"slug":441,"type":15},{"name":443,"slug":444,"type":15},{"name":446,"slug":447,"type":15},{"slug":450,"name":450,"fn":451,"description":452,"org":585,"tags":586,"stars":22,"repoUrl":23,"updatedAt":465},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[587,588,589,590],{"name":456,"slug":457,"type":15},{"name":459,"slug":460,"type":15},{"name":462,"slug":463,"type":15},{"name":9,"slug":8,"type":15},{"slug":467,"name":467,"fn":468,"description":469,"org":592,"tags":593,"stars":22,"repoUrl":23,"updatedAt":481},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[594,595,596],{"name":473,"slug":474,"type":15},{"name":476,"slug":477,"type":15},{"name":479,"slug":480,"type":15},{"slug":483,"name":483,"fn":484,"description":485,"org":598,"tags":599,"stars":22,"repoUrl":23,"updatedAt":500},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[600,601,602,603],{"name":489,"slug":490,"type":15},{"name":492,"slug":493,"type":15},{"name":495,"slug":496,"type":15},{"name":498,"slug":499,"type":15},{"slug":502,"name":502,"fn":503,"description":504,"org":605,"tags":606,"stars":22,"repoUrl":23,"updatedAt":519},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[607,608,609,610],{"name":508,"slug":509,"type":15},{"name":511,"slug":512,"type":15},{"name":514,"slug":515,"type":15},{"name":517,"slug":518,"type":15},{"slug":521,"name":521,"fn":522,"description":523,"org":612,"tags":613,"stars":22,"repoUrl":23,"updatedAt":535},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[614,615,616,617],{"name":527,"slug":528,"type":15},{"name":530,"slug":521,"type":15},{"name":532,"slug":533,"type":15},{"name":462,"slug":463,"type":15},{"slug":537,"name":537,"fn":538,"description":539,"org":619,"tags":620,"stars":22,"repoUrl":23,"updatedAt":551},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[621,622,623,624,625],{"name":527,"slug":528,"type":15},{"name":544,"slug":545,"type":15},{"name":530,"slug":521,"type":15},{"name":532,"slug":533,"type":15},{"name":549,"slug":550,"type":15},{"slug":627,"name":627,"fn":628,"description":629,"org":630,"tags":631,"stars":22,"repoUrl":23,"updatedAt":639},"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},[632,633,634,637,638],{"name":527,"slug":528,"type":15},{"name":544,"slug":545,"type":15},{"name":635,"slug":636,"type":15},"Documentation","documentation",{"name":530,"slug":521,"type":15},{"name":532,"slug":533,"type":15},"2026-05-16T06:07:47.821474",{"slug":641,"name":641,"fn":642,"description":643,"org":644,"tags":645,"stars":22,"repoUrl":23,"updatedAt":651},"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},[646,647,648,649,650],{"name":527,"slug":528,"type":15},{"name":530,"slug":521,"type":15},{"name":532,"slug":533,"type":15},{"name":549,"slug":550,"type":15},{"name":446,"slug":447,"type":15},"2026-05-16T06:07:40.583615",{"slug":653,"name":653,"fn":654,"description":655,"org":656,"tags":657,"stars":22,"repoUrl":23,"updatedAt":666},"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},[658,661,662,665],{"name":659,"slug":660,"type":15},"Animation","animation",{"name":479,"slug":480,"type":15},{"name":663,"slug":664,"type":15},"Creative","creative",{"name":527,"slug":528,"type":15},"2026-05-02T05:31:48.48485",{"slug":668,"name":668,"fn":669,"description":670,"org":671,"tags":672,"stars":22,"repoUrl":23,"updatedAt":682},"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},[673,674,675,678,681],{"name":663,"slug":664,"type":15},{"name":527,"slug":528,"type":15},{"name":676,"slug":677,"type":15},"Image Generation","image-generation",{"name":679,"slug":680,"type":15},"Images","images",{"name":9,"slug":8,"type":15},"2026-05-15T06:23:24.312127",675]