[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ACDR797YSE6SK3PXHC5Q0K":3,"skill-same:01M6ACDR797YSE6SK3PXHC5Q0K":144},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":28,"publishedAt":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":6,"ownerHtmlUrl":45,"ownerBlogUrl":46,"ownerDescription":6,"updatedAt":47,"install":48,"resources":61},"01M6ACDR797YSE6SK3PXHC5Q0K","expo-module",null,"Guide for writing Expo native modules and views using the Expo Modules API (Swift, Kotlin, TypeScript). Covers module definition DSL, native views, shared objects, config plugins, lifecycle hooks, autolinking, and type system. Use when building or modifying native modules for Expo.","openai\u002Fplugins","openai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F14957082?v=4","01M6AC29YGCR4S2NTJFV0G8B81","OpenAI","01M6AC38CEN570NMR96RNGD2NK",7942,"MIT","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins\u002Fblob\u002Fmain\u002Fplugins\u002Fexpo\u002Fskills\u002Fexpo-module\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[29,30,31,32,33],"expo module","writing","swift","typescript","config","2026-11-10 10:12:30",false,"---\nname: expo-module\ndescription: Guide for writing Expo native modules and views using the Expo Modules API (Swift, Kotlin, TypeScript). Covers module definition DSL, native views, shared objects, config plugins, lifecycle hooks, autolinking, and type system. Use when building or modifying native modules for Expo.\nversion: 1.0.0\nlicense: MIT\n---\n\n# Writing Expo Modules\n\nComplete reference for building native modules and views using the Expo Modules API. Covers Swift (iOS), Kotlin (Android), and TypeScript.\n\n## When to Use\n\n- Creating a new Expo native module or native view\n- Adding native functionality (camera, sensors, system APIs) to an Expo app\n- Wrapping platform SDKs for React Native consumption\n- Building config plugins that modify native project files\n\n## References\n\nConsult these resources as needed:\n\n```\nreferences\u002F\n  native-module.md           Module definition DSL: Name, Function, AsyncFunction, Property, Constant, Events, type system, shared objects\n  native-view.md             Native view components: View, Prop, EventDispatcher, view lifecycle, ref-based functions\n  lifecycle.md               Lifecycle hooks: module, iOS app\u002FAppDelegate, Android activity\u002Fapplication listeners\n  config-plugin.md           Config plugins: modifying Info.plist, AndroidManifest.xml, reading values in native code\n  module-config.md           expo-module.config.json fields and autolinking configuration\n```\n\n## Quick Start\n\n### Create a Local Module (in existing app)\n\n**Always scaffold with `create-expo-module` first**, then modify the generated code. This ensures correct podspec, build.gradle, and module config — avoiding common build errors.\n\n```bash\nCI=1 npx create-expo-module@latest --local \\\n  --name MyModule \\\n  --description \"My Expo module\" \\\n  --package expo.modules.mymodule\n```\n\n`CI=1` skips interactive prompts and uses the provided flags.\n\n> **Important:** In `CI=1` (non-interactive) mode, the scaffold always creates the directory as `modules\u002Fmy-module\u002F` because the slug is derived from `customTargetPath` which is `undefined` for `--local` modules — the `--name` flag only sets the native class name, not the directory. After scaffolding, rename it to a kebab-case name matching your module (e.g., `KeyValueStore` → `modules\u002Fkey-value-store\u002F`), then run `cd ios && pod install` so CocoaPods picks up the correct path. Skipping the rename is fine functionally, but skipping `pod install` after any rename causes iOS build failures (\"Build input file cannot be found\").\n\nAvailable flags:\n\n| Flag | Description | Example |\n|------|-------------|---------|\n| `--name` | Native module name (PascalCase) | `--name KeyValueStore` |\n| `--description` | Module description | `--description \"Native key-value storage\"` |\n| `--package` | Android package name | `--package expo.modules.keyvaluestore` |\n| `--author-name` | Author name | `--author-name \"dev\"` |\n| `--author-email` | Author email | `--author-email \"dev@example.com\"` |\n| `--author-url` | Author profile URL | `--author-url \"https:\u002F\u002Fgithub.com\u002Fdev\"` |\n| `--repo` | Repository URL | `--repo \"https:\u002F\u002Fgithub.com\u002Fdev\u002Frepo\"` |\n\nThe scaffold generates both a **native module** (functions, events, constants) and a **native view component** (WebView example with props and events). After scaffolding:\n\n1. **Decide what you need**: If you only need a native module (no UI), remove the view files. If you only need a native view, remove the module function boilerplate. If you need both, keep both and replace the implementations.\n2. **Remove unnecessary boilerplate**: The scaffold includes example code (`hello()` function, `PI` constant, `onChange` event, WebView-based view with `url` prop). Strip all of this and replace with your actual implementation.\n3. **Remove web files if not needed**: The scaffold generates `*.web.ts`\u002F`*.web.tsx` files for web platform support. Remove these if the module is native-only. Also remove `\"web\"` from the `platforms` array in `expo-module.config.json`.\n\n#### What to remove for a module-only (no native view):\n\n- Delete `ios\u002FMyModuleView.swift`, `android\u002F...\u002FMyModuleView.kt`\n- Delete `src\u002FMyModuleView.tsx`, `src\u002FMyModuleView.web.tsx`\n- Remove the `View(...)` block from the module definition in both Swift and Kotlin\n- Remove view-related types from `MyModule.types.ts` and view export from `index.ts`\n\n#### What to remove for a view-only (no module functions):\n\n- Remove `Function`, `AsyncFunction`, `Constant`, `Events` blocks from the module definition (keep `Name` and `View`)\n- Simplify the TypeScript module file to only export the view\n\nGenerated structure (after renaming from `my-module` to your module's kebab-case name):\n\n```\nmodules\u002F\n  my-module\u002F                     # Rename to kebab-case, e.g. key-value-store\u002F\n    android\u002F\n      build.gradle\n      src\u002Fmain\u002Fjava\u002Fexpo\u002Fmodules\u002Fmymodule\u002F\n        MyModule.kt              # Module definition (functions, events, view registration)\n        MyModuleView.kt          # Native view (ExpoView subclass)\n    ios\u002F\n      MyModule.podspec\n      MyModule.swift             # Module definition\n      MyModuleView.swift         # Native view (ExpoView subclass)\n    src\u002F\n      MyModule.ts                # Native module binding\n      MyModule.web.ts            # Web implementation\n      MyModule.types.ts          # Shared types\n      MyModuleView.tsx           # Native view component\n      MyModuleView.web.tsx       # Web view component\n    expo-module.config.json\n    index.ts                     # Re-exports module + view\n```\n\n### Create a Standalone Module (for publishing)\n\n```bash\nnpx create-expo-module@latest my-module\n```\n\n---\n\n## Module Structure Reference\n\nThe Swift and Kotlin DSL share the same structure. Both platforms are shown here for reference — in other reference files, Swift is shown as the primary language unless the Kotlin pattern meaningfully differs.\n\n**Swift (iOS):**\n\n```swift\nimport ExpoModulesCore\n\npublic class MyModule: Module {\n  public func definition() -> ModuleDefinition {\n    Name(\"MyModule\")\n\n    Function(\"hello\") { (name: String) -> String in\n      return \"Hello \\(name)!\"\n    }\n  }\n}\n```\n\n**Kotlin (Android):**\n\n```kotlin\npackage expo.modules.mymodule\n\nimport expo.modules.kotlin.modules.Module\nimport expo.modules.kotlin.modules.ModuleDefinition\n\nclass MyModule : Module() {\n  override fun definition() = ModuleDefinition {\n    Name(\"MyModule\")\n\n    Function(\"hello\") { name: String ->\n      \"Hello $name!\"\n    }\n  }\n}\n```\n\n**TypeScript:**\n\n```typescript\nimport { requireNativeModule } from \"expo\";\n\nconst MyModule = requireNativeModule(\"MyModule\");\n\nexport function hello(name: string): string {\n  return MyModule.hello(name);\n}\n```\n\n### expo-module.config.json\n\n```json\n{\n  \"platforms\": [\"android\", \"apple\"],\n  \"apple\": {\n    \"modules\": [\"MyModule\"]\n  },\n  \"android\": {\n    \"modules\": [\"expo.modules.mymodule.MyModule\"]\n  }\n}\n```\n\nNote: iOS uses just the class name; Android uses the fully-qualified class name (package + class). See `references\u002Fmodule-config.md` for all fields.\n","# Writing Expo Modules\n\nComplete reference for building native modules and views using the Expo Modules API. Covers Swift (iOS), Kotlin (Android), and TypeScript.\n\n## When to Use\n\n- Creating a new Expo native module or native view\n- Adding native functionality (camera, sensors, system APIs) to an Expo app\n- Wrapping platform SDKs for React Native consumption\n- Building config plugins that modify native project files\n\n## References\n\nConsult these resources as needed:\n\n```\nreferences\u002F\n  native-module.md           Module definition DSL: Name, Function, AsyncFunction, Property, Constant, Events, type system, shared objects\n  native-view.md             Native view components: View, Prop, EventDispatcher, view lifecycle, ref-based functions\n  lifecycle.md               Lifecycle hooks: module, iOS app\u002FAppDelegate, Android activity\u002Fapplication listeners\n  config-plugin.md           Config plugins: modifying Info.plist, AndroidManifest.xml, reading values in native code\n  module-config.md           expo-module.config.json fields and autolinking configuration\n```\n\n## Quick Start\n\n### Create a Local Module (in existing app)\n\n**Always scaffold with `create-expo-module` first**, then modify the generated code. This ensures correct podspec, build.gradle, and module config — avoiding common build errors.\n\n```bash\nCI=1 npx create-expo-module@latest --local \\\n  --name MyModule \\\n  --description \"My Expo module\" \\\n  --package expo.modules.mymodule\n```\n\n`CI=1` skips interactive prompts and uses the provided flags.\n\n> **Important:** In `CI=1` (non-interactive) mode, the scaffold always creates the directory as `modules\u002Fmy-module\u002F` because the slug is derived from `customTargetPath` which is `undefined` for `--local` modules — the `--name` flag only sets the native class name, not the directory. After scaffolding, rename it to a kebab-case name matching your module (e.g., `KeyValueStore` → `modules\u002Fkey-value-store\u002F`), then run `cd ios && pod install` so CocoaPods picks up the correct path. Skipping the rename is fine functionally, but skipping `pod install` after any rename causes iOS build failures (\"Build input file cannot be found\").\n\nAvailable flags:\n\n| Flag | Description | Example |\n|------|-------------|---------|\n| `--name` | Native module name (PascalCase) | `--name KeyValueStore` |\n| `--description` | Module description | `--description \"Native key-value storage\"` |\n| `--package` | Android package name | `--package expo.modules.keyvaluestore` |\n| `--author-name` | Author name | `--author-name \"dev\"` |\n| `--author-email` | Author email | `--author-email \"dev@example.com\"` |\n| `--author-url` | Author profile URL | `--author-url \"https:\u002F\u002Fgithub.com\u002Fdev\"` |\n| `--repo` | Repository URL | `--repo \"https:\u002F\u002Fgithub.com\u002Fdev\u002Frepo\"` |\n\nThe scaffold generates both a **native module** (functions, events, constants) and a **native view component** (WebView example with props and events). After scaffolding:\n\n1. **Decide what you need**: If you only need a native module (no UI), remove the view files. If you only need a native view, remove the module function boilerplate. If you need both, keep both and replace the implementations.\n2. **Remove unnecessary boilerplate**: The scaffold includes example code (`hello()` function, `PI` constant, `onChange` event, WebView-based view with `url` prop). Strip all of this and replace with your actual implementation.\n3. **Remove web files if not needed**: The scaffold generates `*.web.ts`\u002F`*.web.tsx` files for web platform support. Remove these if the module is native-only. Also remove `\"web\"` from the `platforms` array in `expo-module.config.json`.\n\n#### What to remove for a module-only (no native view):\n\n- Delete `ios\u002FMyModuleView.swift`, `android\u002F...\u002FMyModuleView.kt`\n- Delete `src\u002FMyModuleView.tsx`, `src\u002FMyModuleView.web.tsx`\n- Remove the `View(...)` block from the module definition in both Swift and Kotlin\n- Remove view-related types from `MyModule.types.ts` and view export from `index.ts`\n\n#### What to remove for a view-only (no module functions):\n\n- Remove `Function`, `AsyncFunction`, `Constant`, `Events` blocks from the module definition (keep `Name` and `View`)\n- Simplify the TypeScript module file to only export the view\n\nGenerated structure (after renaming from `my-module` to your module's kebab-case name):\n\n```\nmodules\u002F\n  my-module\u002F                     # Rename to kebab-case, e.g. key-value-store\u002F\n    android\u002F\n      build.gradle\n      src\u002Fmain\u002Fjava\u002Fexpo\u002Fmodules\u002Fmymodule\u002F\n        MyModule.kt              # Module definition (functions, events, view registration)\n        MyModuleView.kt          # Native view (ExpoView subclass)\n    ios\u002F\n      MyModule.podspec\n      MyModule.swift             # Module definition\n      MyModuleView.swift         # Native view (ExpoView subclass)\n    src\u002F\n      MyModule.ts                # Native module binding\n      MyModule.web.ts            # Web implementation\n      MyModule.types.ts          # Shared types\n      MyModuleView.tsx           # Native view component\n      MyModuleView.web.tsx       # Web view component\n    expo-module.config.json\n    index.ts                     # Re-exports module + view\n```\n\n### Create a Standalone Module (for publishing)\n\n```bash\nnpx create-expo-module@latest my-module\n```\n\n---\n\n## Module Structure Reference\n\nThe Swift and Kotlin DSL share the same structure. Both platforms are shown here for reference — in other reference files, Swift is shown as the primary language unless the Kotlin pattern meaningfully differs.\n\n**Swift (iOS):**\n\n```swift\nimport ExpoModulesCore\n\npublic class MyModule: Module {\n  public func definition() -> ModuleDefinition {\n    Name(\"MyModule\")\n\n    Function(\"hello\") { (name: String) -> String in\n      return \"Hello \\(name)!\"\n    }\n  }\n}\n```\n\n**Kotlin (Android):**\n\n```kotlin\npackage expo.modules.mymodule\n\nimport expo.modules.kotlin.modules.Module\nimport expo.modules.kotlin.modules.ModuleDefinition\n\nclass MyModule : Module() {\n  override fun definition() = ModuleDefinition {\n    Name(\"MyModule\")\n\n    Function(\"hello\") { name: String ->\n      \"Hello $name!\"\n    }\n  }\n}\n```\n\n**TypeScript:**\n\n```typescript\nimport { requireNativeModule } from \"expo\";\n\nconst MyModule = requireNativeModule(\"MyModule\");\n\nexport function hello(name: string): string {\n  return MyModule.hello(name);\n}\n```\n\n### expo-module.config.json\n\n```json\n{\n  \"platforms\": [\"android\", \"apple\"],\n  \"apple\": {\n    \"modules\": [\"MyModule\"]\n  },\n  \"android\": {\n    \"modules\": [\"expo.modules.mymodule.MyModule\"]\n  }\n}\n```\n\nNote: iOS uses just the class name; Android uses the fully-qualified class name (package + class). See `references\u002Fmodule-config.md` for all fields.\n",{"name":5,"license":15,"version":39,"description":7},"1.0.0","main","0722921d5542fc593105c27bd52630babd8b8c2a","plugins\u002Fexpo\u002Fskills\u002Fexpo-module",1025,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins","https:\u002F\u002Fgithub.com\u002Fopenai","https:\u002F\u002Fopenai.com\u002F","2026-11-14 08:11:13",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add openai\u002Fplugins --skill expo-module",{"tool":54,"command":55},"bunx","bunx skills add openai\u002Fplugins --skill expo-module",{"tool":57,"command":58},"pnpm","pnpm dlx skills add openai\u002Fplugins --skill expo-module","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins\u002Fblob\u002Fmain\u002Fplugins\u002Fexpo\u002Fskills\u002Fexpo-module\u002FSKILL.md",true,[62,68,72,76,82,86,90,94,98,102,106,110,114,118,122,126,130,134,138],{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":67},"agents\u002Fopenai.yaml","REFERENCE","参考文档",367,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins\u002Fblob\u002Fmain\u002Fplugins\u002Fexpo\u002Fskills\u002Fexpo-module\u002Fagents\u002Fopenai.yaml",{"path":69,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":70,"sourceHtmlUrl":71},"DELIVERY_SUMMARY.md",16933,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Fexecuting-marketing-campaigns\u002FDELIVERY_SUMMARY.md",{"path":73,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":74,"sourceHtmlUrl":75},"DIRECTORY_STRUCTURE.md",10836,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Fexecuting-marketing-campaigns\u002FDIRECTORY_STRUCTURE.md",{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"examples\u002Fcampaigns_sample.csv","ASSET","资产文件",1543,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Fexecuting-marketing-campaigns\u002Fexamples\u002Fcampaigns_sample.csv",{"path":83,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":84,"sourceHtmlUrl":85},"IMPLEMENTATION_GUIDE.md",11003,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Fexecuting-marketing-campaigns\u002FIMPLEMENTATION_GUIDE.md",{"path":87,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":88,"sourceHtmlUrl":89},"README.md",10682,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Fexecuting-marketing-campaigns\u002FREADME.md",{"path":91,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":92,"sourceHtmlUrl":93},"reference\u002Fanalytics.md",10867,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Fexecuting-marketing-campaigns\u002Freference\u002Fanalytics.md",{"path":95,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":96,"sourceHtmlUrl":97},"reference\u002Fbrand.md",9175,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Fexecuting-marketing-campaigns\u002Freference\u002Fbrand.md",{"path":99,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":100,"sourceHtmlUrl":101},"reference\u002Fcampaigns.md",7347,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Fexecuting-marketing-campaigns\u002Freference\u002Fcampaigns.md",{"path":103,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":104,"sourceHtmlUrl":105},"reference\u002Fcontent.md",9577,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Fexecuting-marketing-campaigns\u002Freference\u002Fcontent.md",{"path":107,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":108,"sourceHtmlUrl":109},"reference\u002Femail.md",9797,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Fexecuting-marketing-campaigns\u002Freference\u002Femail.md",{"path":111,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":112,"sourceHtmlUrl":113},"reference\u002Fsocial_media.md",9449,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Fexecuting-marketing-campaigns\u002Freference\u002Fsocial_media.md",{"path":115,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":116,"sourceHtmlUrl":117},"reference\u002Ftemplates.md",11863,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Fexecuting-marketing-campaigns\u002Freference\u002Ftemplates.md",{"path":119,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":120,"sourceHtmlUrl":121},"references\u002Fconfig-plugin.md",2040,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins\u002Fblob\u002Fmain\u002Fplugins\u002Fexpo\u002Fskills\u002Fexpo-module\u002Freferences\u002Fconfig-plugin.md",{"path":123,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":124,"sourceHtmlUrl":125},"references\u002Flifecycle.md",3763,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins\u002Fblob\u002Fmain\u002Fplugins\u002Fexpo\u002Fskills\u002Fexpo-module\u002Freferences\u002Flifecycle.md",{"path":127,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":128,"sourceHtmlUrl":129},"references\u002Fmodule-config.md",1139,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins\u002Fblob\u002Fmain\u002Fplugins\u002Fexpo\u002Fskills\u002Fexpo-module\u002Freferences\u002Fmodule-config.md",{"path":131,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":132,"sourceHtmlUrl":133},"references\u002Fnative-module.md",5869,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins\u002Fblob\u002Fmain\u002Fplugins\u002Fexpo\u002Fskills\u002Fexpo-module\u002Freferences\u002Fnative-module.md",{"path":135,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":136,"sourceHtmlUrl":137},"references\u002Fnative-view.md",3590,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins\u002Fblob\u002Fmain\u002Fplugins\u002Fexpo\u002Fskills\u002Fexpo-module\u002Freferences\u002Fnative-view.md",{"path":139,"resourceType":140,"resourceTypeDesc":141,"sizeBytes":142,"sourceHtmlUrl":143},"scripts\u002Fmarketing_utils.py","SCRIPT","脚本",11857,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Fexecuting-marketing-campaigns\u002Fscripts\u002Fmarketing_utils.py",[145,163,176,194,221,234],{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":154,"publishedAt":34},"01M6ACYN431ER9AFG508JJH3VT","supabase-postgres-best-practices","Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins\u002Fblob\u002Fmain\u002Fplugins\u002Fsupabase\u002Fskills\u002Fsupabase-postgres-best-practices\u002FSKILL.md",[151],{"categoryNo":152,"categoryName":153,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[155,156,30,157,158,159,160,161,162],"best practices","supabase postgres best practices","performance","sql","code","database","metrics","examples",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":172,"publishedAt":34},"01M6ACQRGGJYVNDPQWB9XGWRNZ","minimal-skill","Minimal example skill for plugin-eval tests. Use when the user wants a compact demonstration of a well-structured skill.","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins\u002Fblob\u002Fmain\u002Fplugins\u002Fplugin-eval\u002Ffixtures\u002Fminimal-skill\u002FSKILL.md",[169],{"categoryNo":170,"categoryName":171,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[173,174,175],"minimal skill","example skill","plugin",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":180,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":183,"publishedAt":34},"01M6ACQ406M83341YPKPEXBXDZ","physical-ai-neural-reconstruction","Router for NVIDIA NuRec\u002FNRE: USDZ rendering, NCore conversion, 3DGS, gRPC sensor sim, PhysicalAI HF datasets. Do NOT use for SimReady or infra setup.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins\u002Fblob\u002Fmain\u002Fplugins\u002Fnvidia\u002Fskills\u002Fphysical-ai-neural-reconstruction\u002FSKILL.md",[],[184,185,186,187,188,189,190,191,192,193],"physical ai neural reconstruction","https","python","github","docker","setup","toolkit","gpu","index","grpc",{"skillNo":195,"name":196,"nameZh":6,"description":197,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":180,"licenseFileUrl":6,"sourceHtmlUrl":198,"categories":199,"keywords":203,"publishedAt":34},"01M6ACPVRFPVATXD7H38Z56QC5","physical-ai-infrastructure-setup-and-resilient-scaling","Use when the user wants to set up, scale, validate, or harden NVIDIA physical AI infrastructure for synthetic data generation workflows across local MicroK8s or Azure AKS, including Kubernetes clusters, inference endpoint deployment, OSMO deployment, workload submission readiness, and infrastructure failure recovery. Trigger keywords: physical ai infrastructure, resilient scaling, SDG infrastructure, microk8s, azure aks, NVCF deployment, NIM Operator, OSMO deploy, workflow scaling. Don't trigger for: OSMO log summarization or workload-only operations unless infrastructure setup, scaling, validation, or recovery is requested.","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins\u002Fblob\u002Fmain\u002Fplugins\u002Fnvidia\u002Fskills\u002Fphysical-ai-infrastructure-setup-and-resilient-scaling\u002FSKILL.md",[200],{"categoryNo":201,"categoryName":202,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",[204,189,205,206,207,208,209,210,211,212,213,214,215,216,217,218,219,220],"physical ai infrastructure setup and resilient scaling","infrastructure","validation","terraform","deployment","synthetic data","workload","ml","cli","kubernetes","inference","workflow","workflows","component","validate","deploy","azure",{"skillNo":222,"name":223,"nameZh":6,"description":224,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":180,"licenseFileUrl":6,"sourceHtmlUrl":225,"categories":226,"keywords":228,"publishedAt":34},"01M6ACPG9JPDSS6MMKVKR3P56E","omniverse-usd-performance-tuning","Top-level workflow skill for USD performance diagnosis and optimization. Use for slow loading, high memory, low FPS, or 'optimize my scene' requests; delegates auth\u002Fruntime setup to Phase 0 owners.","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins\u002Fblob\u002Fmain\u002Fplugins\u002Fnvidia\u002Fskills\u002Fomniverse-usd-performance-tuning\u002FSKILL.md",[227],{"categoryNo":170,"categoryName":171,"taxonomyType":21,"taxonomyTypeDesc":22},[229,157,230,186,231,232,215,189,211,233],"omniverse usd performance tuning","auth","memory","triage","authentication",{"skillNo":235,"name":236,"nameZh":6,"description":237,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":180,"licenseFileUrl":6,"sourceHtmlUrl":238,"categories":239,"keywords":241,"publishedAt":34},"01M6ACP73X9YS5Y730C2WE58YF","omniverse-realtime-viewer","Use as the top-level router for Omniverse Realtime Viewer USD app requests and focused viewer reference documents.","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins\u002Fblob\u002Fmain\u002Fplugins\u002Fnvidia\u002Fskills\u002Fomniverse-realtime-viewer\u002FSKILL.md",[240],{"categoryNo":170,"categoryName":171,"taxonomyType":21,"taxonomyTypeDesc":22},[242,243,186,215,244,245,246,211,208,247,191,32],"omniverse realtime viewer","realtime","electron","react","documents","cpp"]