[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-openai-morning-briefing":3,"mdc-bdtjja-key":36,"related-repo-openai-morning-briefing":448,"related-org-openai-morning-briefing":571},{"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},"morning-briefing","generate daily email and schedule briefings","Generates a morning briefing that triages your inbox and previews your day using the Superhuman Mail MCP server — acting as an AI chief of staff. Use this skill whenever someone asks to \"brief me on my day\", \"triage my inbox\", \"what's important in my email\", \"summarize my unread emails\", \"what do I need to deal with today\", \"chief of staff briefing\", \"morning update\", \"inbox summary\", \"what emails need my attention\", \"clear my inbox\", or any variation of wanting a prioritized view of their email and calendar before they start working. Also trigger when someone says \"I just woke up, what's going on\" or \"catch me up on my inbox\". Trigger broadly — if someone wants to understand the state of their inbox or day at a glance, this skill should activate.",{"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},"Productivity","productivity","tag",{"name":17,"slug":18,"type":15},"Scheduling","scheduling",{"name":20,"slug":21,"type":15},"Meetings","meetings",{"name":23,"slug":24,"type":15},"Email","email",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\u002Fsuperhuman\u002Fskills\u002Fmorning-briefing","---\nname: morning-briefing\ndescription: Generates a morning briefing that triages your inbox and previews your day using the Superhuman Mail MCP server — acting as an AI chief of staff. Use this skill whenever someone asks to \"brief me on my day\", \"triage my inbox\", \"what's important in my email\", \"summarize my unread emails\", \"what do I need to deal with today\", \"chief of staff briefing\", \"morning update\", \"inbox summary\", \"what emails need my attention\", \"clear my inbox\", or any variation of wanting a prioritized view of their email and calendar before they start working. Also trigger when someone says \"I just woke up, what's going on\" or \"catch me up on my inbox\". Trigger broadly — if someone wants to understand the state of their inbox or day at a glance, this skill should activate.\n---\n\n# Morning Briefing & Inbox Triage\n\nYou are an AI chief of staff. Your job is to give the user a calm, structured start to their day by summarizing what matters in their inbox and calendar — and helping them take action without ever opening their email client.\n\nThis skill uses the **Superhuman Mail MCP server** to read the user's inbox, query their calendar, and take actions like drafting replies and archiving threads.\n\n## How it works\n\n### Step 1: Gather context\n\nRun these Superhuman Mail MCP calls in parallel to build a full picture of the user's day:\n\n1. **Calendar overview** — Call `Superhuman_Mail.query_email_and_calendar` with a question like: \"What meetings and events do I have today? Include times, attendees, and any context about what they're about. Exclude denied meetings\"\n\n2. **Unread\u002Fimportant threads** — Call `Superhuman_Mail.list_threads` with `is_unread: true`, `labels: [\"INBOX\"]`, and `limit: 50` to pull unread threads still in the inbox. Also call `Superhuman_Mail.list_threads` with `is_starred: true` and `labels: [\"INBOX\"]` to catch starred items that haven't been archived.\n\n3. **Recent high-signal threads** — Call `Superhuman_Mail.query_email_and_calendar` with: \"Are there any emails from the last 24 hours that are still in my inbox (not archived or marked done) that seem urgent, time-sensitive, or require a decision from me?\"\n\n### Step 2: Categorize and prioritize\n\nScan only the last 24 hours of email. Organize everything into these four categories. Use your judgment — skip any that are empty.\n\n**Urgent** — Needs a reply today. Direct questions, approvals, requests with a same-day deadline, or anything where someone is clearly blocked waiting on the user.\n\n**Important** — Needs attention this week. Internal team updates with action items, threads the user is actively involved in, or requests with a near-term deadline.\n\n**FYI** — Informational, no action needed. Weekly updates, status reports, CC'd threads, calendar acceptances. Worth knowing about, not worth acting on.\n\n**Noise** — Newsletters, automated notifications, marketing emails, Coda\u002FFigma\u002Ftool notifications, customer support tickets not addressed to the user, growth\u002Freferral alerts. These can be archived.\n\nFor **Urgent** and **Important** emails, capture: sender name, subject line, and a one-line summary of what they need.\n\nFor **FYI** and **Noise**, don't list every thread — instead, summarize key insights and patterns (e.g., \"3 churn feedback submissions — top reasons: too expensive, too hard to learn\").\n\nAlso gather **Calendar context** — for each meeting today, surface the time, title, attendees, and any relevant email threads that would help the user show up prepared.\n\n### Step 3: Present the briefing\n\nWrite a concise, scannable briefing. The tone should be like a trusted executive assistant speaking at a morning standup — warm, direct, no fluff.\n\nStructure:\n\n```\n## Your day at a glance\n[One-liner: e.g., \"You have 4 meetings today and 12 unread threads — 2 are urgent.\"]\n\n## Urgent — needs a reply today (X threads)\nFor each:\n- **Sender Name** — *Subject line*\n  One-line summary of what they need and why it's time-sensitive.\n\n## Important — needs attention this week (X threads)\nFor each:\n- **Sender Name** — *Subject line*\n  One-line summary of what they need.\n\n## Calendar today\nFor each meeting: time, title, attendees, and any relevant email context.\n\n## FYI — informational (X threads)\nKey insights and themes across FYI threads. Don't list every thread — summarize what's worth knowing.\n\n## Noise (X threads)\nBreakdown by type (e.g., \"12 growth notifications, 8 support tickets, 5 newsletters\"). Call out any interesting patterns. Ask the user if they'd like you to archive these.\n```\n\n### Step 4: Offer actions\n\nAfter presenting the briefing, offer concrete next steps:\n\n- **\"Want me to draft replies for the urgent threads?\"** — Uses `Superhuman_Mail.create_or_update_draft` with `instructions` so drafts match the user's voice\n- **\"Want me to archive the noise threads?\"** — Uses `Superhuman_Mail.update_thread` with `mark_done: true`\n- **\"Want me to pull up the full thread for any of these?\"** — Uses `Superhuman_Mail.get_thread`\n\n## Important notes\n\n- **Never send an email without explicit user approval.** Drafts only — the user reviews before anything goes out.\n- **When summarizing threads, be specific.** \"Email from Sarah\" is useless. \"Sarah asking for your sign-off on the Q3 budget by EOD\" is useful.\n- **If the user has a very full inbox (50+ unread)**, focus on the top 10-15 most important threads rather than trying to cover everything. Mention how many you're skipping and offer to dig deeper.\n- **Time-sensitivity matters.** If something has a deadline today, call it out prominently.\n- **If you notice threads that are part of the same conversation or topic**, group them rather than listing each separately.\n",{"data":37,"body":38},{"name":4,"description":6},{"type":39,"children":40},"root",[41,50,56,69,76,83,88,190,196,201,211,221,231,241,257,272,284,290,295,300,312,318,323,389,395],{"type":42,"tag":43,"props":44,"children":46},"element","h1",{"id":45},"morning-briefing-inbox-triage",[47],{"type":48,"value":49},"text","Morning Briefing & Inbox Triage",{"type":42,"tag":51,"props":52,"children":53},"p",{},[54],{"type":48,"value":55},"You are an AI chief of staff. Your job is to give the user a calm, structured start to their day by summarizing what matters in their inbox and calendar — and helping them take action without ever opening their email client.",{"type":42,"tag":51,"props":57,"children":58},{},[59,61,67],{"type":48,"value":60},"This skill uses the ",{"type":42,"tag":62,"props":63,"children":64},"strong",{},[65],{"type":48,"value":66},"Superhuman Mail MCP server",{"type":48,"value":68}," to read the user's inbox, query their calendar, and take actions like drafting replies and archiving threads.",{"type":42,"tag":70,"props":71,"children":73},"h2",{"id":72},"how-it-works",[74],{"type":48,"value":75},"How it works",{"type":42,"tag":77,"props":78,"children":80},"h3",{"id":79},"step-1-gather-context",[81],{"type":48,"value":82},"Step 1: Gather context",{"type":42,"tag":51,"props":84,"children":85},{},[86],{"type":48,"value":87},"Run these Superhuman Mail MCP calls in parallel to build a full picture of the user's day:",{"type":42,"tag":89,"props":90,"children":91},"ol",{},[92,112,174],{"type":42,"tag":93,"props":94,"children":95},"li",{},[96,101,103,110],{"type":42,"tag":62,"props":97,"children":98},{},[99],{"type":48,"value":100},"Calendar overview",{"type":48,"value":102}," — Call ",{"type":42,"tag":104,"props":105,"children":107},"code",{"className":106},[],[108],{"type":48,"value":109},"Superhuman_Mail.query_email_and_calendar",{"type":48,"value":111}," with a question like: \"What meetings and events do I have today? Include times, attendees, and any context about what they're about. Exclude denied meetings\"",{"type":42,"tag":93,"props":113,"children":114},{},[115,120,121,127,129,135,137,143,145,151,153,158,159,165,167,172],{"type":42,"tag":62,"props":116,"children":117},{},[118],{"type":48,"value":119},"Unread\u002Fimportant threads",{"type":48,"value":102},{"type":42,"tag":104,"props":122,"children":124},{"className":123},[],[125],{"type":48,"value":126},"Superhuman_Mail.list_threads",{"type":48,"value":128}," with ",{"type":42,"tag":104,"props":130,"children":132},{"className":131},[],[133],{"type":48,"value":134},"is_unread: true",{"type":48,"value":136},", ",{"type":42,"tag":104,"props":138,"children":140},{"className":139},[],[141],{"type":48,"value":142},"labels: [\"INBOX\"]",{"type":48,"value":144},", and ",{"type":42,"tag":104,"props":146,"children":148},{"className":147},[],[149],{"type":48,"value":150},"limit: 50",{"type":48,"value":152}," to pull unread threads still in the inbox. Also call ",{"type":42,"tag":104,"props":154,"children":156},{"className":155},[],[157],{"type":48,"value":126},{"type":48,"value":128},{"type":42,"tag":104,"props":160,"children":162},{"className":161},[],[163],{"type":48,"value":164},"is_starred: true",{"type":48,"value":166}," and ",{"type":42,"tag":104,"props":168,"children":170},{"className":169},[],[171],{"type":48,"value":142},{"type":48,"value":173}," to catch starred items that haven't been archived.",{"type":42,"tag":93,"props":175,"children":176},{},[177,182,183,188],{"type":42,"tag":62,"props":178,"children":179},{},[180],{"type":48,"value":181},"Recent high-signal threads",{"type":48,"value":102},{"type":42,"tag":104,"props":184,"children":186},{"className":185},[],[187],{"type":48,"value":109},{"type":48,"value":189}," with: \"Are there any emails from the last 24 hours that are still in my inbox (not archived or marked done) that seem urgent, time-sensitive, or require a decision from me?\"",{"type":42,"tag":77,"props":191,"children":193},{"id":192},"step-2-categorize-and-prioritize",[194],{"type":48,"value":195},"Step 2: Categorize and prioritize",{"type":42,"tag":51,"props":197,"children":198},{},[199],{"type":48,"value":200},"Scan only the last 24 hours of email. Organize everything into these four categories. Use your judgment — skip any that are empty.",{"type":42,"tag":51,"props":202,"children":203},{},[204,209],{"type":42,"tag":62,"props":205,"children":206},{},[207],{"type":48,"value":208},"Urgent",{"type":48,"value":210}," — Needs a reply today. Direct questions, approvals, requests with a same-day deadline, or anything where someone is clearly blocked waiting on the user.",{"type":42,"tag":51,"props":212,"children":213},{},[214,219],{"type":42,"tag":62,"props":215,"children":216},{},[217],{"type":48,"value":218},"Important",{"type":48,"value":220}," — Needs attention this week. Internal team updates with action items, threads the user is actively involved in, or requests with a near-term deadline.",{"type":42,"tag":51,"props":222,"children":223},{},[224,229],{"type":42,"tag":62,"props":225,"children":226},{},[227],{"type":48,"value":228},"FYI",{"type":48,"value":230}," — Informational, no action needed. Weekly updates, status reports, CC'd threads, calendar acceptances. Worth knowing about, not worth acting on.",{"type":42,"tag":51,"props":232,"children":233},{},[234,239],{"type":42,"tag":62,"props":235,"children":236},{},[237],{"type":48,"value":238},"Noise",{"type":48,"value":240}," — Newsletters, automated notifications, marketing emails, Coda\u002FFigma\u002Ftool notifications, customer support tickets not addressed to the user, growth\u002Freferral alerts. These can be archived.",{"type":42,"tag":51,"props":242,"children":243},{},[244,246,250,251,255],{"type":48,"value":245},"For ",{"type":42,"tag":62,"props":247,"children":248},{},[249],{"type":48,"value":208},{"type":48,"value":166},{"type":42,"tag":62,"props":252,"children":253},{},[254],{"type":48,"value":218},{"type":48,"value":256}," emails, capture: sender name, subject line, and a one-line summary of what they need.",{"type":42,"tag":51,"props":258,"children":259},{},[260,261,265,266,270],{"type":48,"value":245},{"type":42,"tag":62,"props":262,"children":263},{},[264],{"type":48,"value":228},{"type":48,"value":166},{"type":42,"tag":62,"props":267,"children":268},{},[269],{"type":48,"value":238},{"type":48,"value":271},", don't list every thread — instead, summarize key insights and patterns (e.g., \"3 churn feedback submissions — top reasons: too expensive, too hard to learn\").",{"type":42,"tag":51,"props":273,"children":274},{},[275,277,282],{"type":48,"value":276},"Also gather ",{"type":42,"tag":62,"props":278,"children":279},{},[280],{"type":48,"value":281},"Calendar context",{"type":48,"value":283}," — for each meeting today, surface the time, title, attendees, and any relevant email threads that would help the user show up prepared.",{"type":42,"tag":77,"props":285,"children":287},{"id":286},"step-3-present-the-briefing",[288],{"type":48,"value":289},"Step 3: Present the briefing",{"type":42,"tag":51,"props":291,"children":292},{},[293],{"type":48,"value":294},"Write a concise, scannable briefing. The tone should be like a trusted executive assistant speaking at a morning standup — warm, direct, no fluff.",{"type":42,"tag":51,"props":296,"children":297},{},[298],{"type":48,"value":299},"Structure:",{"type":42,"tag":301,"props":302,"children":306},"pre",{"className":303,"code":305,"language":48},[304],"language-text","## Your day at a glance\n[One-liner: e.g., \"You have 4 meetings today and 12 unread threads — 2 are urgent.\"]\n\n## Urgent — needs a reply today (X threads)\nFor each:\n- **Sender Name** — *Subject line*\n  One-line summary of what they need and why it's time-sensitive.\n\n## Important — needs attention this week (X threads)\nFor each:\n- **Sender Name** — *Subject line*\n  One-line summary of what they need.\n\n## Calendar today\nFor each meeting: time, title, attendees, and any relevant email context.\n\n## FYI — informational (X threads)\nKey insights and themes across FYI threads. Don't list every thread — summarize what's worth knowing.\n\n## Noise (X threads)\nBreakdown by type (e.g., \"12 growth notifications, 8 support tickets, 5 newsletters\"). Call out any interesting patterns. Ask the user if they'd like you to archive these.\n",[307],{"type":42,"tag":104,"props":308,"children":310},{"__ignoreMap":309},"",[311],{"type":48,"value":305},{"type":42,"tag":77,"props":313,"children":315},{"id":314},"step-4-offer-actions",[316],{"type":48,"value":317},"Step 4: Offer actions",{"type":42,"tag":51,"props":319,"children":320},{},[321],{"type":48,"value":322},"After presenting the briefing, offer concrete next steps:",{"type":42,"tag":324,"props":325,"children":326},"ul",{},[327,352,374],{"type":42,"tag":93,"props":328,"children":329},{},[330,335,337,343,344,350],{"type":42,"tag":62,"props":331,"children":332},{},[333],{"type":48,"value":334},"\"Want me to draft replies for the urgent threads?\"",{"type":48,"value":336}," — Uses ",{"type":42,"tag":104,"props":338,"children":340},{"className":339},[],[341],{"type":48,"value":342},"Superhuman_Mail.create_or_update_draft",{"type":48,"value":128},{"type":42,"tag":104,"props":345,"children":347},{"className":346},[],[348],{"type":48,"value":349},"instructions",{"type":48,"value":351}," so drafts match the user's voice",{"type":42,"tag":93,"props":353,"children":354},{},[355,360,361,367,368],{"type":42,"tag":62,"props":356,"children":357},{},[358],{"type":48,"value":359},"\"Want me to archive the noise threads?\"",{"type":48,"value":336},{"type":42,"tag":104,"props":362,"children":364},{"className":363},[],[365],{"type":48,"value":366},"Superhuman_Mail.update_thread",{"type":48,"value":128},{"type":42,"tag":104,"props":369,"children":371},{"className":370},[],[372],{"type":48,"value":373},"mark_done: true",{"type":42,"tag":93,"props":375,"children":376},{},[377,382,383],{"type":42,"tag":62,"props":378,"children":379},{},[380],{"type":48,"value":381},"\"Want me to pull up the full thread for any of these?\"",{"type":48,"value":336},{"type":42,"tag":104,"props":384,"children":386},{"className":385},[],[387],{"type":48,"value":388},"Superhuman_Mail.get_thread",{"type":42,"tag":70,"props":390,"children":392},{"id":391},"important-notes",[393],{"type":48,"value":394},"Important notes",{"type":42,"tag":324,"props":396,"children":397},{},[398,408,418,428,438],{"type":42,"tag":93,"props":399,"children":400},{},[401,406],{"type":42,"tag":62,"props":402,"children":403},{},[404],{"type":48,"value":405},"Never send an email without explicit user approval.",{"type":48,"value":407}," Drafts only — the user reviews before anything goes out.",{"type":42,"tag":93,"props":409,"children":410},{},[411,416],{"type":42,"tag":62,"props":412,"children":413},{},[414],{"type":48,"value":415},"When summarizing threads, be specific.",{"type":48,"value":417}," \"Email from Sarah\" is useless. \"Sarah asking for your sign-off on the Q3 budget by EOD\" is useful.",{"type":42,"tag":93,"props":419,"children":420},{},[421,426],{"type":42,"tag":62,"props":422,"children":423},{},[424],{"type":48,"value":425},"If the user has a very full inbox (50+ unread)",{"type":48,"value":427},", focus on the top 10-15 most important threads rather than trying to cover everything. Mention how many you're skipping and offer to dig deeper.",{"type":42,"tag":93,"props":429,"children":430},{},[431,436],{"type":42,"tag":62,"props":432,"children":433},{},[434],{"type":48,"value":435},"Time-sensitivity matters.",{"type":48,"value":437}," If something has a deadline today, call it out prominently.",{"type":42,"tag":93,"props":439,"children":440},{},[441,446],{"type":42,"tag":62,"props":442,"children":443},{},[444],{"type":48,"value":445},"If you notice threads that are part of the same conversation or topic",{"type":48,"value":447},", group them rather than listing each separately.",{"items":449,"total":570},[450,468,484,496,516,538,558],{"slug":451,"name":451,"fn":452,"description":453,"org":454,"tags":455,"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},[456,459,462,465],{"name":457,"slug":458,"type":15},"Accessibility","accessibility",{"name":460,"slug":461,"type":15},"Charts","charts",{"name":463,"slug":464,"type":15},"Data Visualization","data-visualization",{"name":466,"slug":467,"type":15},"Design","design",{"slug":469,"name":469,"fn":470,"description":471,"org":472,"tags":473,"stars":25,"repoUrl":26,"updatedAt":483},"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},[474,477,480],{"name":475,"slug":476,"type":15},"Agents","agents",{"name":478,"slug":479,"type":15},"Browser Automation","browser-automation",{"name":481,"slug":482,"type":15},"Testing","testing","2026-04-06T18:41:03.44016",{"slug":485,"name":485,"fn":486,"description":487,"org":488,"tags":489,"stars":25,"repoUrl":26,"updatedAt":495},"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},[490,491,494],{"name":478,"slug":479,"type":15},{"name":492,"slug":493,"type":15},"Local Development","local-development",{"name":481,"slug":482,"type":15},"2026-04-06T18:41:17.526867",{"slug":497,"name":497,"fn":498,"description":499,"org":500,"tags":501,"stars":25,"repoUrl":26,"updatedAt":515},"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},[502,503,506,509,512],{"name":475,"slug":476,"type":15},{"name":504,"slug":505,"type":15},"Cloudflare Workers","cloudflare-workers",{"name":507,"slug":508,"type":15},"SDK","sdk",{"name":510,"slug":511,"type":15},"Serverless","serverless",{"name":513,"slug":514,"type":15},"WebSockets","websockets","2026-04-06T18:39:51.717063",{"slug":517,"name":517,"fn":518,"description":519,"org":520,"tags":521,"stars":25,"repoUrl":26,"updatedAt":537},"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},[522,525,528,531,534],{"name":523,"slug":524,"type":15},"Frontend","frontend",{"name":526,"slug":527,"type":15},"React","react",{"name":529,"slug":530,"type":15},"shadcn\u002Fui","shadcn-ui",{"name":532,"slug":533,"type":15},"UI Components","ui-components",{"name":535,"slug":536,"type":15},"Vercel","vercel","2026-04-06T18:40:59.619419",{"slug":539,"name":539,"fn":540,"description":541,"org":542,"tags":543,"stars":25,"repoUrl":26,"updatedAt":557},"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},[544,547,550,553,556],{"name":545,"slug":546,"type":15},"AI Infrastructure","ai-infrastructure",{"name":548,"slug":549,"type":15},"Cost Optimization","cost-optimization",{"name":551,"slug":552,"type":15},"LLM","llm",{"name":554,"slug":555,"type":15},"Performance","performance",{"name":535,"slug":536,"type":15},"2026-04-06T18:40:44.377464",{"slug":559,"name":559,"fn":560,"description":561,"org":562,"tags":563,"stars":25,"repoUrl":26,"updatedAt":569},"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},[564,565,568],{"name":548,"slug":549,"type":15},{"name":566,"slug":567,"type":15},"Database","database",{"name":551,"slug":552,"type":15},"2026-04-06T18:41:08.513425",600,{"items":572,"total":767},[573,594,617,634,650,667,684,696,710,724,736,751],{"slug":574,"name":574,"fn":575,"description":576,"org":577,"tags":578,"stars":591,"repoUrl":592,"updatedAt":593},"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},[579,582,585,588],{"name":580,"slug":581,"type":15},"Documents","documents",{"name":583,"slug":584,"type":15},"Healthcare","healthcare",{"name":586,"slug":587,"type":15},"Insurance","insurance",{"name":589,"slug":590,"type":15},"Regulatory Compliance","regulatory-compliance",28169,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fopenai-agents-python","2026-04-16T05:11:39.180399",{"slug":595,"name":595,"fn":596,"description":597,"org":598,"tags":599,"stars":614,"repoUrl":615,"updatedAt":616},"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},[600,603,605,608,611],{"name":601,"slug":602,"type":15},".NET","dotnet",{"name":604,"slug":595,"type":15},"ASP.NET Core",{"name":606,"slug":607,"type":15},"Blazor","blazor",{"name":609,"slug":610,"type":15},"C#","csharp",{"name":612,"slug":613,"type":15},"Web Development","web-development",23787,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fskills","2026-04-12T05:07:02.819491",{"slug":618,"name":618,"fn":619,"description":620,"org":621,"tags":622,"stars":614,"repoUrl":615,"updatedAt":633},"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},[623,626,629,632],{"name":624,"slug":625,"type":15},"Apps SDK","apps-sdk",{"name":627,"slug":628,"type":15},"ChatGPT","chatgpt",{"name":630,"slug":631,"type":15},"MCP","mcp",{"name":9,"slug":8,"type":15},"2026-04-12T05:07:05.468097",{"slug":635,"name":635,"fn":636,"description":637,"org":638,"tags":639,"stars":614,"repoUrl":615,"updatedAt":649},"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},[640,643,646],{"name":641,"slug":642,"type":15},"API Development","api-development",{"name":644,"slug":645,"type":15},"CLI","cli",{"name":647,"slug":648,"type":15},"Codex","codex","2026-04-12T05:07:04.132762",{"slug":651,"name":651,"fn":652,"description":653,"org":654,"tags":655,"stars":614,"repoUrl":615,"updatedAt":666},"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},[656,659,662,663],{"name":657,"slug":658,"type":15},"Cloudflare","cloudflare",{"name":660,"slug":661,"type":15},"Cloudflare Pages","cloudflare-pages",{"name":504,"slug":505,"type":15},{"name":664,"slug":665,"type":15},"Deployment","deployment","2026-04-12T05:07:14.275118",{"slug":668,"name":668,"fn":669,"description":670,"org":671,"tags":672,"stars":614,"repoUrl":615,"updatedAt":683},"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},[673,674,677,680],{"name":13,"slug":14,"type":15},{"name":675,"slug":676,"type":15},"Project Management","project-management",{"name":678,"slug":679,"type":15},"Strategy","strategy",{"name":681,"slug":682,"type":15},"Task Management","task-management","2026-05-23T06:17:16.870838",{"slug":685,"name":685,"fn":686,"description":687,"org":688,"tags":689,"stars":614,"repoUrl":615,"updatedAt":695},"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},[690,691,693,694],{"name":466,"slug":467,"type":15},{"name":692,"slug":685,"type":15},"Figma",{"name":523,"slug":524,"type":15},{"name":630,"slug":631,"type":15},"2026-04-12T05:06:47.939943",{"slug":697,"name":697,"fn":698,"description":699,"org":700,"tags":701,"stars":614,"repoUrl":615,"updatedAt":709},"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},[702,703,706,707,708],{"name":466,"slug":467,"type":15},{"name":704,"slug":705,"type":15},"Design System","design-system",{"name":692,"slug":685,"type":15},{"name":523,"slug":524,"type":15},{"name":532,"slug":533,"type":15},"2026-05-10T05:59:52.971881",{"slug":711,"name":711,"fn":712,"description":713,"org":714,"tags":715,"stars":614,"repoUrl":615,"updatedAt":723},"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},[716,717,718,721,722],{"name":466,"slug":467,"type":15},{"name":704,"slug":705,"type":15},{"name":719,"slug":720,"type":15},"Documentation","documentation",{"name":692,"slug":685,"type":15},{"name":523,"slug":524,"type":15},"2026-05-16T06:07:47.821474",{"slug":725,"name":725,"fn":726,"description":727,"org":728,"tags":729,"stars":614,"repoUrl":615,"updatedAt":735},"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},[730,731,732,733,734],{"name":466,"slug":467,"type":15},{"name":692,"slug":685,"type":15},{"name":523,"slug":524,"type":15},{"name":532,"slug":533,"type":15},{"name":612,"slug":613,"type":15},"2026-05-16T06:07:40.583615",{"slug":737,"name":737,"fn":738,"description":739,"org":740,"tags":741,"stars":614,"repoUrl":615,"updatedAt":750},"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},[742,745,746,749],{"name":743,"slug":744,"type":15},"Animation","animation",{"name":647,"slug":648,"type":15},{"name":747,"slug":748,"type":15},"Creative","creative",{"name":466,"slug":467,"type":15},"2026-05-02T05:31:48.48485",{"slug":752,"name":752,"fn":753,"description":754,"org":755,"tags":756,"stars":614,"repoUrl":615,"updatedAt":766},"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},[757,758,759,762,765],{"name":747,"slug":748,"type":15},{"name":466,"slug":467,"type":15},{"name":760,"slug":761,"type":15},"Image Generation","image-generation",{"name":763,"slug":764,"type":15},"Images","images",{"name":9,"slug":8,"type":15},"2026-05-15T06:23:24.312127",675]