[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-openai-sharepoint":3,"mdc--gnxfyk-key":35,"related-org-openai-sharepoint":872,"related-repo-openai-sharepoint":1077},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":24,"repoUrl":25,"updatedAt":26,"license":27,"forks":28,"topics":29,"repo":30,"sourceUrl":33,"mdContent":34},"sharepoint","inspect and plan changes for SharePoint sites","Inspect Microsoft SharePoint context, discover the right site or library, and prepare safe changes. Use when the user wants site, page, or file review, ownership and status extraction, or change planning before editing content, navigation, or information architecture.",{"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,18,21],{"name":13,"slug":14,"type":15},"Operations","operations","tag",{"name":17,"slug":4,"type":15},"SharePoint",{"name":19,"slug":20,"type":15},"Microsoft 365","microsoft-365",{"name":22,"slug":23,"type":15},"Documents","documents",3992,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins","2026-04-06T18:43:12.512405",null,465,[],{"repoUrl":25,"stars":24,"forks":28,"topics":31,"description":32},[],"OpenAI Plugins","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins\u002Ftree\u002FHEAD\u002Fplugins\u002Fsharepoint\u002Fskills\u002Fsharepoint","---\nname: sharepoint\ndescription: Inspect Microsoft SharePoint context, discover the right site or library, and prepare safe changes. Use when the user wants site, page, or file review, ownership and status extraction, or change planning before editing content, navigation, or information architecture.\n---\n\n# SharePoint\n\n## Overview\n\nUse this skill to turn SharePoint sites, pages, files, and document-library context into clear summaries and low-risk edit plans. Read the relevant content first, anchor recommendations in the exact site or file, and separate review from write actions.\n\n## Preferred Deliverables\n\n- Site or page briefs that capture purpose, owners, current status, and open issues.\n- File summaries that highlight the latest content, gaps, and action items.\n- Edit plans that specify what should change, where it should change, and why.\n- Recent-document summaries that identify what changed lately and which files are most active.\n- Sharing and permission summaries that explain who has access, how a file is shared, and what safe sharing change is needed.\n- Version-history or recovery plans that identify whether a file should be copied, moved, restored, or reverted to an earlier version.\n\n## Workflow Skills\n\n| Workflow | Skill |\n| --- | --- |\n| Resolve the right site, library, or folder before file work | [..\u002Fsharepoint-site-discovery\u002FSKILL.md](..\u002Fsharepoint-site-discovery\u002FSKILL.md) |\n| Word document edits that must preserve `.docx` structure and styling | [..\u002Fsharepoint-word-docs\u002FSKILL.md](..\u002Fsharepoint-word-docs\u002FSKILL.md) |\n| Spreadsheet edits that must preserve workbook structure, formulas, and formatting | [..\u002Fsharepoint-spreadsheets\u002FSKILL.md](..\u002Fsharepoint-spreadsheets\u002FSKILL.md) |\n| Formula design, repair, and rollout in a SharePoint-hosted workbook | [..\u002Fsharepoint-spreadsheet-formula-builder\u002FSKILL.md](..\u002Fsharepoint-spreadsheet-formula-builder\u002FSKILL.md) |\n| PowerPoint deck edits that must preserve slide style and template fidelity | [..\u002Fsharepoint-powerpoint\u002FSKILL.md](..\u002Fsharepoint-powerpoint\u002FSKILL.md) |\n| Cross-document synthesis and maintaining shared strategy or roadmap docs | [..\u002Fsharepoint-shared-doc-maintenance\u002FSKILL.md](..\u002Fsharepoint-shared-doc-maintenance\u002FSKILL.md) |\n\n## Workflow\n\n1. Read the relevant site, page, file, or library before proposing changes. Capture the current title, location, owners, linked documents, and the content that matters.\n2. When the user is exploring, summarize the current information architecture or document state before suggesting edits.\n3. Ground every recommendation in the exact SharePoint destination, such as the site name, page name, library, or file path.\n4. When the exact site, drive, or folder is not already known, use the truthful discovery path:\n   - `get_site(...)` to validate the site\n   - `list_site_drives(...)` to discover libraries on that site\n   - `search(query=None, hostname=..., site_path=..., folder_path=...)` to browse a known site or folder\n   - `search(query=\"...\")` only when the user actually wants keyword search\n5. If the user asks what they recently worked on or wants a recency-based shortlist rather than site discovery, use `list_recent_documents` instead of treating recency as browse context.\n6. If the request is about who can access a file, how it is shared, or how to share it, use:\n   - `list_item_permissions` to inspect current access\n   - `create_sharing_link` for link-based sharing when the user wants a link\n   - `invite_item_recipients` when the user wants to share with specific people\n7. If the request is about file recovery or controlled reorganization, use:\n   - `list_item_versions` before restore or rollback\n   - `restore_item_version` only when the user clearly wants an older version restored\n   - `copy_item`, `move_or_rename_item`, or `move_items_bulk` for explicit copy\u002Fmove\u002Freorg work\n   - `create_folder` or `create_folders_bulk` when the user is creating destination structure\n8. If the request is primarily about locating the right site, library, or folder before file work, route to [..\u002Fsharepoint-site-discovery\u002FSKILL.md](..\u002Fsharepoint-site-discovery\u002FSKILL.md).\n9. If the request targets an Office document, determine whether the task is content analysis only or an actual file edit before choosing the workflow.\n10. Route specialized Office workflows to the appropriate SharePoint skill:\n   - `.docx` edits -> [..\u002Fsharepoint-word-docs\u002FSKILL.md](..\u002Fsharepoint-word-docs\u002FSKILL.md)\n   - `.xlsx` edits -> [..\u002Fsharepoint-spreadsheets\u002FSKILL.md](..\u002Fsharepoint-spreadsheets\u002FSKILL.md)\n   - formula-heavy `.xlsx` work -> [..\u002Fsharepoint-spreadsheet-formula-builder\u002FSKILL.md](..\u002Fsharepoint-spreadsheet-formula-builder\u002FSKILL.md)\n   - style-sensitive `.pptx` edits -> [..\u002Fsharepoint-powerpoint\u002FSKILL.md](..\u002Fsharepoint-powerpoint\u002FSKILL.md)\n   - maintained strategy, roadmap, planning, or status docs -> [..\u002Fsharepoint-shared-doc-maintenance\u002FSKILL.md](..\u002Fsharepoint-shared-doc-maintenance\u002FSKILL.md)\n11. When using SharePoint file-update tools, prefer the drive-root-relative file path from the item's metadata rather than guessing a library-prefixed path. A file may appear under `Shared Documents\u002F...` in the web URL while the writable API path is just the filename or another root-relative path.\n12. After any write, re-fetch the file from SharePoint and verify the specific intended change in the returned content or metadata rather than assuming the upload succeeded.\n13. Treat verification as two separate checks whenever fidelity matters:\n   - Content verification: the intended sections, text, cells, or slides are present.\n   - Fidelity verification: headings, spacing, theme, layout, formatting, and template conventions still match the source file's visual language.\n14. If connector limitations prevent fidelity verification or safe style-preserving upload, say so explicitly before calling the edit complete.\n15. If the request is write-oriented, present the intended content change or structure change before applying broad edits.\n16. Call out content dependencies such as linked files, navigation references, approvals, owners, or downstream sharing expectations when they affect the update.\n17. Only change content, structure, metadata, sharing state, or version state when the user has clearly asked for that action.\n\n## Write Safety\n\n- In Codex, treat the Microsoft SharePoint app tools as the primary surface. Do not rely on generic MCP resource listing for SharePoint discovery; the backend wrapper routes through direct connector tools instead.\n- Prefer the exact SharePoint result `url` from keyword search or browse results when handing a file into `fetch`; the implementation supports browser or sharing URLs too, but those are fallback inputs rather than the primary discovery path.\n- Do not treat user-recency as site discovery. For site browsing, use `get_site(...)`, `list_site_drives(...)`, and explicit browse mode on `search(query=None, ...)`.\n- Preserve page titles, document names, file locations, ownership details, and linked references unless the user requests a change.\n- Treat page overwrites, navigation changes, library reorganizations, and sharing or permission changes as high-impact actions that require extra clarity.\n- Before changing sharing state, inspect the current permissions or link posture when that context affects whether the requested change is safe.\n- Before restoring an older version, make clear that this changes the current file state for downstream readers; use `copy_item` instead when the safer outcome is to preserve both versions.\n- If multiple similarly named sites, pages, or files exist, identify the intended destination before drafting or editing.\n- When a requested change could affect linked content or downstream readers, call that out before proposing the update.\n- For document edits, preserve the file format and existing structure. Do not replace a `.docx` or other Office file with plain text output when the user expects the original document to remain editable.\n- Treat SharePoint `update_file` as a whole-file overwrite, not an in-place Office patch. For rich Office edits, make the change locally to the real package, then replace the file deliberately.\n- If one failed binary overwrite strongly suggests inline base64 transport fragility, do not keep retrying richer Office packages blindly. Reassess the connector path, reduce scope, or stop and explain the limitation.\n\n## Output Conventions\n\n- Always reference the exact site, page, library, or file when describing findings or planned edits.\n- Summaries should lead with the current purpose or status, then list owners, important content, gaps, and next steps.\n- Edit plans should state the target, current state, intended change, and reason.\n- When the user asks for structure help, present the proposed navigation or information architecture in a short, scannable outline.\n- Distinguish clearly between content analysis and a write-ready update.\n- For completed file edits, report both the file that was changed and how you verified the updated result.\n\n## Operational Recovery Notes\n\n- Avoid unsupported wrapper patterns for SharePoint fetch or update calls. If a parallelized or delegated form of the same operation is not supported, retry with the direct connector call rather than spending turns debugging the wrapper.\n- On SharePoint `429` throttling, wait the stated retry interval and retry once cleanly.\n- If a binary overwrite fails with invalid base64 after a rich Office edit, treat that as likely transport fragility rather than proof that the Office file itself is corrupt.\n- When a request has both content and fidelity requirements, do not report overall success after content verification alone. Make the fidelity status explicit.\n\n## Example Requests\n\n- \"Summarize this SharePoint site and tell me who owns each major section.\"\n- \"Review the project page and draft the content changes needed to reflect the new timeline.\"\n- \"Tell me what this document library contains and which files look outdated.\"\n- \"Show me the SharePoint documents I touched recently and which ones probably need follow-up.\"\n- \"Who currently has access to this file, and create the right internal sharing link.\"\n- \"Restore the version from before yesterday's change, or tell me whether copying the file is safer.\"\n- \"Plan the information-architecture changes needed for the operations site before we edit it.\"\n- \"Update the team roadmap based on any milestone changes in the project docs.\"\n- \"Maintain the shared planning document so it reflects the latest source-of-truth timelines.\"\n\n## Light Fallback\n\nIf SharePoint data is missing or incomplete, say that Microsoft SharePoint access may be unavailable or pointed at the wrong site or file, then ask the user to reconnect or clarify the intended destination.\n",{"data":36,"body":37},{"name":4,"description":6},{"type":38,"children":39},"root",[40,47,54,60,66,101,107,241,246,468,540,567,580,604,610,731,737,770,776,807,813,861,867],{"type":41,"tag":42,"props":43,"children":44},"element","h1",{"id":4},[45],{"type":46,"value":17},"text",{"type":41,"tag":48,"props":49,"children":51},"h2",{"id":50},"overview",[52],{"type":46,"value":53},"Overview",{"type":41,"tag":55,"props":56,"children":57},"p",{},[58],{"type":46,"value":59},"Use this skill to turn SharePoint sites, pages, files, and document-library context into clear summaries and low-risk edit plans. Read the relevant content first, anchor recommendations in the exact site or file, and separate review from write actions.",{"type":41,"tag":48,"props":61,"children":63},{"id":62},"preferred-deliverables",[64],{"type":46,"value":65},"Preferred Deliverables",{"type":41,"tag":67,"props":68,"children":69},"ul",{},[70,76,81,86,91,96],{"type":41,"tag":71,"props":72,"children":73},"li",{},[74],{"type":46,"value":75},"Site or page briefs that capture purpose, owners, current status, and open issues.",{"type":41,"tag":71,"props":77,"children":78},{},[79],{"type":46,"value":80},"File summaries that highlight the latest content, gaps, and action items.",{"type":41,"tag":71,"props":82,"children":83},{},[84],{"type":46,"value":85},"Edit plans that specify what should change, where it should change, and why.",{"type":41,"tag":71,"props":87,"children":88},{},[89],{"type":46,"value":90},"Recent-document summaries that identify what changed lately and which files are most active.",{"type":41,"tag":71,"props":92,"children":93},{},[94],{"type":46,"value":95},"Sharing and permission summaries that explain who has access, how a file is shared, and what safe sharing change is needed.",{"type":41,"tag":71,"props":97,"children":98},{},[99],{"type":46,"value":100},"Version-history or recovery plans that identify whether a file should be copied, moved, restored, or reverted to an earlier version.",{"type":41,"tag":48,"props":102,"children":104},{"id":103},"workflow-skills",[105],{"type":46,"value":106},"Workflow Skills",{"type":41,"tag":108,"props":109,"children":110},"table",{},[111,130],{"type":41,"tag":112,"props":113,"children":114},"thead",{},[115],{"type":41,"tag":116,"props":117,"children":118},"tr",{},[119,125],{"type":41,"tag":120,"props":121,"children":122},"th",{},[123],{"type":46,"value":124},"Workflow",{"type":41,"tag":120,"props":126,"children":127},{},[128],{"type":46,"value":129},"Skill",{"type":41,"tag":131,"props":132,"children":133},"tbody",{},[134,152,177,193,209,225],{"type":41,"tag":116,"props":135,"children":136},{},[137,143],{"type":41,"tag":138,"props":139,"children":140},"td",{},[141],{"type":46,"value":142},"Resolve the right site, library, or folder before file work",{"type":41,"tag":138,"props":144,"children":145},{},[146],{"type":41,"tag":147,"props":148,"children":150},"a",{"href":149},"..\u002Fsharepoint-site-discovery\u002FSKILL.md",[151],{"type":46,"value":149},{"type":41,"tag":116,"props":153,"children":154},{},[155,169],{"type":41,"tag":138,"props":156,"children":157},{},[158,160,167],{"type":46,"value":159},"Word document edits that must preserve ",{"type":41,"tag":161,"props":162,"children":164},"code",{"className":163},[],[165],{"type":46,"value":166},".docx",{"type":46,"value":168}," structure and styling",{"type":41,"tag":138,"props":170,"children":171},{},[172],{"type":41,"tag":147,"props":173,"children":175},{"href":174},"..\u002Fsharepoint-word-docs\u002FSKILL.md",[176],{"type":46,"value":174},{"type":41,"tag":116,"props":178,"children":179},{},[180,185],{"type":41,"tag":138,"props":181,"children":182},{},[183],{"type":46,"value":184},"Spreadsheet edits that must preserve workbook structure, formulas, and formatting",{"type":41,"tag":138,"props":186,"children":187},{},[188],{"type":41,"tag":147,"props":189,"children":191},{"href":190},"..\u002Fsharepoint-spreadsheets\u002FSKILL.md",[192],{"type":46,"value":190},{"type":41,"tag":116,"props":194,"children":195},{},[196,201],{"type":41,"tag":138,"props":197,"children":198},{},[199],{"type":46,"value":200},"Formula design, repair, and rollout in a SharePoint-hosted workbook",{"type":41,"tag":138,"props":202,"children":203},{},[204],{"type":41,"tag":147,"props":205,"children":207},{"href":206},"..\u002Fsharepoint-spreadsheet-formula-builder\u002FSKILL.md",[208],{"type":46,"value":206},{"type":41,"tag":116,"props":210,"children":211},{},[212,217],{"type":41,"tag":138,"props":213,"children":214},{},[215],{"type":46,"value":216},"PowerPoint deck edits that must preserve slide style and template fidelity",{"type":41,"tag":138,"props":218,"children":219},{},[220],{"type":41,"tag":147,"props":221,"children":223},{"href":222},"..\u002Fsharepoint-powerpoint\u002FSKILL.md",[224],{"type":46,"value":222},{"type":41,"tag":116,"props":226,"children":227},{},[228,233],{"type":41,"tag":138,"props":229,"children":230},{},[231],{"type":46,"value":232},"Cross-document synthesis and maintaining shared strategy or roadmap docs",{"type":41,"tag":138,"props":234,"children":235},{},[236],{"type":41,"tag":147,"props":237,"children":239},{"href":238},"..\u002Fsharepoint-shared-doc-maintenance\u002FSKILL.md",[240],{"type":46,"value":238},{"type":41,"tag":48,"props":242,"children":244},{"id":243},"workflow",[245],{"type":46,"value":124},{"type":41,"tag":247,"props":248,"children":249},"ol",{},[250,255,260,265,317,330,371,447,458,463],{"type":41,"tag":71,"props":251,"children":252},{},[253],{"type":46,"value":254},"Read the relevant site, page, file, or library before proposing changes. Capture the current title, location, owners, linked documents, and the content that matters.",{"type":41,"tag":71,"props":256,"children":257},{},[258],{"type":46,"value":259},"When the user is exploring, summarize the current information architecture or document state before suggesting edits.",{"type":41,"tag":71,"props":261,"children":262},{},[263],{"type":46,"value":264},"Ground every recommendation in the exact SharePoint destination, such as the site name, page name, library, or file path.",{"type":41,"tag":71,"props":266,"children":267},{},[268,270],{"type":46,"value":269},"When the exact site, drive, or folder is not already known, use the truthful discovery path:\n",{"type":41,"tag":67,"props":271,"children":272},{},[273,284,295,306],{"type":41,"tag":71,"props":274,"children":275},{},[276,282],{"type":41,"tag":161,"props":277,"children":279},{"className":278},[],[280],{"type":46,"value":281},"get_site(...)",{"type":46,"value":283}," to validate the site",{"type":41,"tag":71,"props":285,"children":286},{},[287,293],{"type":41,"tag":161,"props":288,"children":290},{"className":289},[],[291],{"type":46,"value":292},"list_site_drives(...)",{"type":46,"value":294}," to discover libraries on that site",{"type":41,"tag":71,"props":296,"children":297},{},[298,304],{"type":41,"tag":161,"props":299,"children":301},{"className":300},[],[302],{"type":46,"value":303},"search(query=None, hostname=..., site_path=..., folder_path=...)",{"type":46,"value":305}," to browse a known site or folder",{"type":41,"tag":71,"props":307,"children":308},{},[309,315],{"type":41,"tag":161,"props":310,"children":312},{"className":311},[],[313],{"type":46,"value":314},"search(query=\"...\")",{"type":46,"value":316}," only when the user actually wants keyword search",{"type":41,"tag":71,"props":318,"children":319},{},[320,322,328],{"type":46,"value":321},"If the user asks what they recently worked on or wants a recency-based shortlist rather than site discovery, use ",{"type":41,"tag":161,"props":323,"children":325},{"className":324},[],[326],{"type":46,"value":327},"list_recent_documents",{"type":46,"value":329}," instead of treating recency as browse context.",{"type":41,"tag":71,"props":331,"children":332},{},[333,335],{"type":46,"value":334},"If the request is about who can access a file, how it is shared, or how to share it, use:\n",{"type":41,"tag":67,"props":336,"children":337},{},[338,349,360],{"type":41,"tag":71,"props":339,"children":340},{},[341,347],{"type":41,"tag":161,"props":342,"children":344},{"className":343},[],[345],{"type":46,"value":346},"list_item_permissions",{"type":46,"value":348}," to inspect current access",{"type":41,"tag":71,"props":350,"children":351},{},[352,358],{"type":41,"tag":161,"props":353,"children":355},{"className":354},[],[356],{"type":46,"value":357},"create_sharing_link",{"type":46,"value":359}," for link-based sharing when the user wants a link",{"type":41,"tag":71,"props":361,"children":362},{},[363,369],{"type":41,"tag":161,"props":364,"children":366},{"className":365},[],[367],{"type":46,"value":368},"invite_item_recipients",{"type":46,"value":370}," when the user wants to share with specific people",{"type":41,"tag":71,"props":372,"children":373},{},[374,376],{"type":46,"value":375},"If the request is about file recovery or controlled reorganization, use:\n",{"type":41,"tag":67,"props":377,"children":378},{},[379,390,401,428],{"type":41,"tag":71,"props":380,"children":381},{},[382,388],{"type":41,"tag":161,"props":383,"children":385},{"className":384},[],[386],{"type":46,"value":387},"list_item_versions",{"type":46,"value":389}," before restore or rollback",{"type":41,"tag":71,"props":391,"children":392},{},[393,399],{"type":41,"tag":161,"props":394,"children":396},{"className":395},[],[397],{"type":46,"value":398},"restore_item_version",{"type":46,"value":400}," only when the user clearly wants an older version restored",{"type":41,"tag":71,"props":402,"children":403},{},[404,410,412,418,420,426],{"type":41,"tag":161,"props":405,"children":407},{"className":406},[],[408],{"type":46,"value":409},"copy_item",{"type":46,"value":411},", ",{"type":41,"tag":161,"props":413,"children":415},{"className":414},[],[416],{"type":46,"value":417},"move_or_rename_item",{"type":46,"value":419},", or ",{"type":41,"tag":161,"props":421,"children":423},{"className":422},[],[424],{"type":46,"value":425},"move_items_bulk",{"type":46,"value":427}," for explicit copy\u002Fmove\u002Freorg work",{"type":41,"tag":71,"props":429,"children":430},{},[431,437,439,445],{"type":41,"tag":161,"props":432,"children":434},{"className":433},[],[435],{"type":46,"value":436},"create_folder",{"type":46,"value":438}," or ",{"type":41,"tag":161,"props":440,"children":442},{"className":441},[],[443],{"type":46,"value":444},"create_folders_bulk",{"type":46,"value":446}," when the user is creating destination structure",{"type":41,"tag":71,"props":448,"children":449},{},[450,452,456],{"type":46,"value":451},"If the request is primarily about locating the right site, library, or folder before file work, route to ",{"type":41,"tag":147,"props":453,"children":454},{"href":149},[455],{"type":46,"value":149},{"type":46,"value":457},".",{"type":41,"tag":71,"props":459,"children":460},{},[461],{"type":46,"value":462},"If the request targets an Office document, determine whether the task is content analysis only or an actual file edit before choosing the workflow.",{"type":41,"tag":71,"props":464,"children":465},{},[466],{"type":46,"value":467},"Route specialized Office workflows to the appropriate SharePoint skill:",{"type":41,"tag":67,"props":469,"children":470},{},[471,485,499,515,531],{"type":41,"tag":71,"props":472,"children":473},{},[474,479,481],{"type":41,"tag":161,"props":475,"children":477},{"className":476},[],[478],{"type":46,"value":166},{"type":46,"value":480}," edits -> ",{"type":41,"tag":147,"props":482,"children":483},{"href":174},[484],{"type":46,"value":174},{"type":41,"tag":71,"props":486,"children":487},{},[488,494,495],{"type":41,"tag":161,"props":489,"children":491},{"className":490},[],[492],{"type":46,"value":493},".xlsx",{"type":46,"value":480},{"type":41,"tag":147,"props":496,"children":497},{"href":190},[498],{"type":46,"value":190},{"type":41,"tag":71,"props":500,"children":501},{},[502,504,509,511],{"type":46,"value":503},"formula-heavy ",{"type":41,"tag":161,"props":505,"children":507},{"className":506},[],[508],{"type":46,"value":493},{"type":46,"value":510}," work -> ",{"type":41,"tag":147,"props":512,"children":513},{"href":206},[514],{"type":46,"value":206},{"type":41,"tag":71,"props":516,"children":517},{},[518,520,526,527],{"type":46,"value":519},"style-sensitive ",{"type":41,"tag":161,"props":521,"children":523},{"className":522},[],[524],{"type":46,"value":525},".pptx",{"type":46,"value":480},{"type":41,"tag":147,"props":528,"children":529},{"href":222},[530],{"type":46,"value":222},{"type":41,"tag":71,"props":532,"children":533},{},[534,536],{"type":46,"value":535},"maintained strategy, roadmap, planning, or status docs -> ",{"type":41,"tag":147,"props":537,"children":538},{"href":238},[539],{"type":46,"value":238},{"type":41,"tag":247,"props":541,"children":543},{"start":542},11,[544,557,562],{"type":41,"tag":71,"props":545,"children":546},{},[547,549,555],{"type":46,"value":548},"When using SharePoint file-update tools, prefer the drive-root-relative file path from the item's metadata rather than guessing a library-prefixed path. A file may appear under ",{"type":41,"tag":161,"props":550,"children":552},{"className":551},[],[553],{"type":46,"value":554},"Shared Documents\u002F...",{"type":46,"value":556}," in the web URL while the writable API path is just the filename or another root-relative path.",{"type":41,"tag":71,"props":558,"children":559},{},[560],{"type":46,"value":561},"After any write, re-fetch the file from SharePoint and verify the specific intended change in the returned content or metadata rather than assuming the upload succeeded.",{"type":41,"tag":71,"props":563,"children":564},{},[565],{"type":46,"value":566},"Treat verification as two separate checks whenever fidelity matters:",{"type":41,"tag":67,"props":568,"children":569},{},[570,575],{"type":41,"tag":71,"props":571,"children":572},{},[573],{"type":46,"value":574},"Content verification: the intended sections, text, cells, or slides are present.",{"type":41,"tag":71,"props":576,"children":577},{},[578],{"type":46,"value":579},"Fidelity verification: headings, spacing, theme, layout, formatting, and template conventions still match the source file's visual language.",{"type":41,"tag":247,"props":581,"children":583},{"start":582},14,[584,589,594,599],{"type":41,"tag":71,"props":585,"children":586},{},[587],{"type":46,"value":588},"If connector limitations prevent fidelity verification or safe style-preserving upload, say so explicitly before calling the edit complete.",{"type":41,"tag":71,"props":590,"children":591},{},[592],{"type":46,"value":593},"If the request is write-oriented, present the intended content change or structure change before applying broad edits.",{"type":41,"tag":71,"props":595,"children":596},{},[597],{"type":46,"value":598},"Call out content dependencies such as linked files, navigation references, approvals, owners, or downstream sharing expectations when they affect the update.",{"type":41,"tag":71,"props":600,"children":601},{},[602],{"type":46,"value":603},"Only change content, structure, metadata, sharing state, or version state when the user has clearly asked for that action.",{"type":41,"tag":48,"props":605,"children":607},{"id":606},"write-safety",[608],{"type":46,"value":609},"Write Safety",{"type":41,"tag":67,"props":611,"children":612},{},[613,618,639,664,669,674,679,691,696,701,713,726],{"type":41,"tag":71,"props":614,"children":615},{},[616],{"type":46,"value":617},"In Codex, treat the Microsoft SharePoint app tools as the primary surface. Do not rely on generic MCP resource listing for SharePoint discovery; the backend wrapper routes through direct connector tools instead.",{"type":41,"tag":71,"props":619,"children":620},{},[621,623,629,631,637],{"type":46,"value":622},"Prefer the exact SharePoint result ",{"type":41,"tag":161,"props":624,"children":626},{"className":625},[],[627],{"type":46,"value":628},"url",{"type":46,"value":630}," from keyword search or browse results when handing a file into ",{"type":41,"tag":161,"props":632,"children":634},{"className":633},[],[635],{"type":46,"value":636},"fetch",{"type":46,"value":638},"; the implementation supports browser or sharing URLs too, but those are fallback inputs rather than the primary discovery path.",{"type":41,"tag":71,"props":640,"children":641},{},[642,644,649,650,655,657,663],{"type":46,"value":643},"Do not treat user-recency as site discovery. For site browsing, use ",{"type":41,"tag":161,"props":645,"children":647},{"className":646},[],[648],{"type":46,"value":281},{"type":46,"value":411},{"type":41,"tag":161,"props":651,"children":653},{"className":652},[],[654],{"type":46,"value":292},{"type":46,"value":656},", and explicit browse mode on ",{"type":41,"tag":161,"props":658,"children":660},{"className":659},[],[661],{"type":46,"value":662},"search(query=None, ...)",{"type":46,"value":457},{"type":41,"tag":71,"props":665,"children":666},{},[667],{"type":46,"value":668},"Preserve page titles, document names, file locations, ownership details, and linked references unless the user requests a change.",{"type":41,"tag":71,"props":670,"children":671},{},[672],{"type":46,"value":673},"Treat page overwrites, navigation changes, library reorganizations, and sharing or permission changes as high-impact actions that require extra clarity.",{"type":41,"tag":71,"props":675,"children":676},{},[677],{"type":46,"value":678},"Before changing sharing state, inspect the current permissions or link posture when that context affects whether the requested change is safe.",{"type":41,"tag":71,"props":680,"children":681},{},[682,684,689],{"type":46,"value":683},"Before restoring an older version, make clear that this changes the current file state for downstream readers; use ",{"type":41,"tag":161,"props":685,"children":687},{"className":686},[],[688],{"type":46,"value":409},{"type":46,"value":690}," instead when the safer outcome is to preserve both versions.",{"type":41,"tag":71,"props":692,"children":693},{},[694],{"type":46,"value":695},"If multiple similarly named sites, pages, or files exist, identify the intended destination before drafting or editing.",{"type":41,"tag":71,"props":697,"children":698},{},[699],{"type":46,"value":700},"When a requested change could affect linked content or downstream readers, call that out before proposing the update.",{"type":41,"tag":71,"props":702,"children":703},{},[704,706,711],{"type":46,"value":705},"For document edits, preserve the file format and existing structure. Do not replace a ",{"type":41,"tag":161,"props":707,"children":709},{"className":708},[],[710],{"type":46,"value":166},{"type":46,"value":712}," or other Office file with plain text output when the user expects the original document to remain editable.",{"type":41,"tag":71,"props":714,"children":715},{},[716,718,724],{"type":46,"value":717},"Treat SharePoint ",{"type":41,"tag":161,"props":719,"children":721},{"className":720},[],[722],{"type":46,"value":723},"update_file",{"type":46,"value":725}," as a whole-file overwrite, not an in-place Office patch. For rich Office edits, make the change locally to the real package, then replace the file deliberately.",{"type":41,"tag":71,"props":727,"children":728},{},[729],{"type":46,"value":730},"If one failed binary overwrite strongly suggests inline base64 transport fragility, do not keep retrying richer Office packages blindly. Reassess the connector path, reduce scope, or stop and explain the limitation.",{"type":41,"tag":48,"props":732,"children":734},{"id":733},"output-conventions",[735],{"type":46,"value":736},"Output Conventions",{"type":41,"tag":67,"props":738,"children":739},{},[740,745,750,755,760,765],{"type":41,"tag":71,"props":741,"children":742},{},[743],{"type":46,"value":744},"Always reference the exact site, page, library, or file when describing findings or planned edits.",{"type":41,"tag":71,"props":746,"children":747},{},[748],{"type":46,"value":749},"Summaries should lead with the current purpose or status, then list owners, important content, gaps, and next steps.",{"type":41,"tag":71,"props":751,"children":752},{},[753],{"type":46,"value":754},"Edit plans should state the target, current state, intended change, and reason.",{"type":41,"tag":71,"props":756,"children":757},{},[758],{"type":46,"value":759},"When the user asks for structure help, present the proposed navigation or information architecture in a short, scannable outline.",{"type":41,"tag":71,"props":761,"children":762},{},[763],{"type":46,"value":764},"Distinguish clearly between content analysis and a write-ready update.",{"type":41,"tag":71,"props":766,"children":767},{},[768],{"type":46,"value":769},"For completed file edits, report both the file that was changed and how you verified the updated result.",{"type":41,"tag":48,"props":771,"children":773},{"id":772},"operational-recovery-notes",[774],{"type":46,"value":775},"Operational Recovery Notes",{"type":41,"tag":67,"props":777,"children":778},{},[779,784,797,802],{"type":41,"tag":71,"props":780,"children":781},{},[782],{"type":46,"value":783},"Avoid unsupported wrapper patterns for SharePoint fetch or update calls. If a parallelized or delegated form of the same operation is not supported, retry with the direct connector call rather than spending turns debugging the wrapper.",{"type":41,"tag":71,"props":785,"children":786},{},[787,789,795],{"type":46,"value":788},"On SharePoint ",{"type":41,"tag":161,"props":790,"children":792},{"className":791},[],[793],{"type":46,"value":794},"429",{"type":46,"value":796}," throttling, wait the stated retry interval and retry once cleanly.",{"type":41,"tag":71,"props":798,"children":799},{},[800],{"type":46,"value":801},"If a binary overwrite fails with invalid base64 after a rich Office edit, treat that as likely transport fragility rather than proof that the Office file itself is corrupt.",{"type":41,"tag":71,"props":803,"children":804},{},[805],{"type":46,"value":806},"When a request has both content and fidelity requirements, do not report overall success after content verification alone. Make the fidelity status explicit.",{"type":41,"tag":48,"props":808,"children":810},{"id":809},"example-requests",[811],{"type":46,"value":812},"Example Requests",{"type":41,"tag":67,"props":814,"children":815},{},[816,821,826,831,836,841,846,851,856],{"type":41,"tag":71,"props":817,"children":818},{},[819],{"type":46,"value":820},"\"Summarize this SharePoint site and tell me who owns each major section.\"",{"type":41,"tag":71,"props":822,"children":823},{},[824],{"type":46,"value":825},"\"Review the project page and draft the content changes needed to reflect the new timeline.\"",{"type":41,"tag":71,"props":827,"children":828},{},[829],{"type":46,"value":830},"\"Tell me what this document library contains and which files look outdated.\"",{"type":41,"tag":71,"props":832,"children":833},{},[834],{"type":46,"value":835},"\"Show me the SharePoint documents I touched recently and which ones probably need follow-up.\"",{"type":41,"tag":71,"props":837,"children":838},{},[839],{"type":46,"value":840},"\"Who currently has access to this file, and create the right internal sharing link.\"",{"type":41,"tag":71,"props":842,"children":843},{},[844],{"type":46,"value":845},"\"Restore the version from before yesterday's change, or tell me whether copying the file is safer.\"",{"type":41,"tag":71,"props":847,"children":848},{},[849],{"type":46,"value":850},"\"Plan the information-architecture changes needed for the operations site before we edit it.\"",{"type":41,"tag":71,"props":852,"children":853},{},[854],{"type":46,"value":855},"\"Update the team roadmap based on any milestone changes in the project docs.\"",{"type":41,"tag":71,"props":857,"children":858},{},[859],{"type":46,"value":860},"\"Maintain the shared planning document so it reflects the latest source-of-truth timelines.\"",{"type":41,"tag":48,"props":862,"children":864},{"id":863},"light-fallback",[865],{"type":46,"value":866},"Light Fallback",{"type":41,"tag":55,"props":868,"children":869},{},[870],{"type":46,"value":871},"If SharePoint data is missing or incomplete, say that Microsoft SharePoint access may be unavailable or pointed at the wrong site or file, then ask the user to reconnect or clarify the intended destination.",{"items":873,"total":1076},[874,893,916,933,949,968,987,1003,1019,1033,1045,1060],{"slug":875,"name":875,"fn":876,"description":877,"org":878,"tags":879,"stars":890,"repoUrl":891,"updatedAt":892},"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},[880,881,884,887],{"name":22,"slug":23,"type":15},{"name":882,"slug":883,"type":15},"Healthcare","healthcare",{"name":885,"slug":886,"type":15},"Insurance","insurance",{"name":888,"slug":889,"type":15},"Regulatory Compliance","regulatory-compliance",28169,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fopenai-agents-python","2026-04-16T05:11:39.180399",{"slug":894,"name":894,"fn":895,"description":896,"org":897,"tags":898,"stars":913,"repoUrl":914,"updatedAt":915},"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},[899,902,904,907,910],{"name":900,"slug":901,"type":15},".NET","dotnet",{"name":903,"slug":894,"type":15},"ASP.NET Core",{"name":905,"slug":906,"type":15},"Blazor","blazor",{"name":908,"slug":909,"type":15},"C#","csharp",{"name":911,"slug":912,"type":15},"Web Development","web-development",23787,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fskills","2026-04-12T05:07:02.819491",{"slug":917,"name":917,"fn":918,"description":919,"org":920,"tags":921,"stars":913,"repoUrl":914,"updatedAt":932},"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},[922,925,928,931],{"name":923,"slug":924,"type":15},"Apps SDK","apps-sdk",{"name":926,"slug":927,"type":15},"ChatGPT","chatgpt",{"name":929,"slug":930,"type":15},"MCP","mcp",{"name":9,"slug":8,"type":15},"2026-04-12T05:07:05.468097",{"slug":934,"name":934,"fn":935,"description":936,"org":937,"tags":938,"stars":913,"repoUrl":914,"updatedAt":948},"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},[939,942,945],{"name":940,"slug":941,"type":15},"API Development","api-development",{"name":943,"slug":944,"type":15},"CLI","cli",{"name":946,"slug":947,"type":15},"Codex","codex","2026-04-12T05:07:04.132762",{"slug":950,"name":950,"fn":951,"description":952,"org":953,"tags":954,"stars":913,"repoUrl":914,"updatedAt":967},"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},[955,958,961,964],{"name":956,"slug":957,"type":15},"Cloudflare","cloudflare",{"name":959,"slug":960,"type":15},"Cloudflare Pages","cloudflare-pages",{"name":962,"slug":963,"type":15},"Cloudflare Workers","cloudflare-workers",{"name":965,"slug":966,"type":15},"Deployment","deployment","2026-04-12T05:07:14.275118",{"slug":969,"name":969,"fn":970,"description":971,"org":972,"tags":973,"stars":913,"repoUrl":914,"updatedAt":986},"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},[974,977,980,983],{"name":975,"slug":976,"type":15},"Productivity","productivity",{"name":978,"slug":979,"type":15},"Project Management","project-management",{"name":981,"slug":982,"type":15},"Strategy","strategy",{"name":984,"slug":985,"type":15},"Task Management","task-management","2026-05-23T06:17:16.870838",{"slug":988,"name":988,"fn":989,"description":990,"org":991,"tags":992,"stars":913,"repoUrl":914,"updatedAt":1002},"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},[993,996,998,1001],{"name":994,"slug":995,"type":15},"Design","design",{"name":997,"slug":988,"type":15},"Figma",{"name":999,"slug":1000,"type":15},"Frontend","frontend",{"name":929,"slug":930,"type":15},"2026-04-12T05:06:47.939943",{"slug":1004,"name":1004,"fn":1005,"description":1006,"org":1007,"tags":1008,"stars":913,"repoUrl":914,"updatedAt":1018},"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},[1009,1010,1013,1014,1015],{"name":994,"slug":995,"type":15},{"name":1011,"slug":1012,"type":15},"Design System","design-system",{"name":997,"slug":988,"type":15},{"name":999,"slug":1000,"type":15},{"name":1016,"slug":1017,"type":15},"UI Components","ui-components","2026-05-10T05:59:52.971881",{"slug":1020,"name":1020,"fn":1021,"description":1022,"org":1023,"tags":1024,"stars":913,"repoUrl":914,"updatedAt":1032},"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},[1025,1026,1027,1030,1031],{"name":994,"slug":995,"type":15},{"name":1011,"slug":1012,"type":15},{"name":1028,"slug":1029,"type":15},"Documentation","documentation",{"name":997,"slug":988,"type":15},{"name":999,"slug":1000,"type":15},"2026-05-16T06:07:47.821474",{"slug":1034,"name":1034,"fn":1035,"description":1036,"org":1037,"tags":1038,"stars":913,"repoUrl":914,"updatedAt":1044},"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},[1039,1040,1041,1042,1043],{"name":994,"slug":995,"type":15},{"name":997,"slug":988,"type":15},{"name":999,"slug":1000,"type":15},{"name":1016,"slug":1017,"type":15},{"name":911,"slug":912,"type":15},"2026-05-16T06:07:40.583615",{"slug":1046,"name":1046,"fn":1047,"description":1048,"org":1049,"tags":1050,"stars":913,"repoUrl":914,"updatedAt":1059},"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},[1051,1054,1055,1058],{"name":1052,"slug":1053,"type":15},"Animation","animation",{"name":946,"slug":947,"type":15},{"name":1056,"slug":1057,"type":15},"Creative","creative",{"name":994,"slug":995,"type":15},"2026-05-02T05:31:48.48485",{"slug":1061,"name":1061,"fn":1062,"description":1063,"org":1064,"tags":1065,"stars":913,"repoUrl":914,"updatedAt":1075},"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},[1066,1067,1068,1071,1074],{"name":1056,"slug":1057,"type":15},{"name":994,"slug":995,"type":15},{"name":1069,"slug":1070,"type":15},"Image Generation","image-generation",{"name":1072,"slug":1073,"type":15},"Images","images",{"name":9,"slug":8,"type":15},"2026-05-15T06:23:24.312127",675,{"items":1078,"total":1192},[1079,1096,1112,1124,1142,1160,1180],{"slug":1080,"name":1080,"fn":1081,"description":1082,"org":1083,"tags":1084,"stars":24,"repoUrl":25,"updatedAt":1095},"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},[1085,1088,1091,1094],{"name":1086,"slug":1087,"type":15},"Accessibility","accessibility",{"name":1089,"slug":1090,"type":15},"Charts","charts",{"name":1092,"slug":1093,"type":15},"Data Visualization","data-visualization",{"name":994,"slug":995,"type":15},"2026-06-30T19:00:57.102",{"slug":1097,"name":1097,"fn":1098,"description":1099,"org":1100,"tags":1101,"stars":24,"repoUrl":25,"updatedAt":1111},"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},[1102,1105,1108],{"name":1103,"slug":1104,"type":15},"Agents","agents",{"name":1106,"slug":1107,"type":15},"Browser Automation","browser-automation",{"name":1109,"slug":1110,"type":15},"Testing","testing","2026-04-06T18:41:03.44016",{"slug":1113,"name":1113,"fn":1114,"description":1115,"org":1116,"tags":1117,"stars":24,"repoUrl":25,"updatedAt":1123},"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},[1118,1119,1122],{"name":1106,"slug":1107,"type":15},{"name":1120,"slug":1121,"type":15},"Local Development","local-development",{"name":1109,"slug":1110,"type":15},"2026-04-06T18:41:17.526867",{"slug":1125,"name":1125,"fn":1126,"description":1127,"org":1128,"tags":1129,"stars":24,"repoUrl":25,"updatedAt":1141},"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},[1130,1131,1132,1135,1138],{"name":1103,"slug":1104,"type":15},{"name":962,"slug":963,"type":15},{"name":1133,"slug":1134,"type":15},"SDK","sdk",{"name":1136,"slug":1137,"type":15},"Serverless","serverless",{"name":1139,"slug":1140,"type":15},"WebSockets","websockets","2026-04-06T18:39:51.717063",{"slug":1143,"name":1143,"fn":1144,"description":1145,"org":1146,"tags":1147,"stars":24,"repoUrl":25,"updatedAt":1159},"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},[1148,1149,1152,1155,1156],{"name":999,"slug":1000,"type":15},{"name":1150,"slug":1151,"type":15},"React","react",{"name":1153,"slug":1154,"type":15},"shadcn\u002Fui","shadcn-ui",{"name":1016,"slug":1017,"type":15},{"name":1157,"slug":1158,"type":15},"Vercel","vercel","2026-04-06T18:40:59.619419",{"slug":1161,"name":1161,"fn":1162,"description":1163,"org":1164,"tags":1165,"stars":24,"repoUrl":25,"updatedAt":1179},"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},[1166,1169,1172,1175,1178],{"name":1167,"slug":1168,"type":15},"AI Infrastructure","ai-infrastructure",{"name":1170,"slug":1171,"type":15},"Cost Optimization","cost-optimization",{"name":1173,"slug":1174,"type":15},"LLM","llm",{"name":1176,"slug":1177,"type":15},"Performance","performance",{"name":1157,"slug":1158,"type":15},"2026-04-06T18:40:44.377464",{"slug":1181,"name":1181,"fn":1182,"description":1183,"org":1184,"tags":1185,"stars":24,"repoUrl":25,"updatedAt":1191},"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},[1186,1187,1190],{"name":1170,"slug":1171,"type":15},{"name":1188,"slug":1189,"type":15},"Database","database",{"name":1173,"slug":1174,"type":15},"2026-04-06T18:41:08.513425",600]