[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6GR5Q2GYYKCBW4698QBPSZ8":3,"skill-same:01M6GR5Q2GYYKCBW4698QBPSZ8":98},{"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":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":14,"repositoryHtmlUrl":58,"repositoryHomepageUrl":6,"ownerHtmlUrl":59,"ownerBlogUrl":60,"ownerDescription":6,"updatedAt":61,"install":62,"resources":75},"01M6GR5Q2GYYKCBW4698QBPSZ8","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.","gaos6e\u002FMyOpenclaw","gaos6e","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F246307622?v=4","01M6GQWTQ9F7C09EV7E2XHF4WY","Gao Se","01M6GQWTVEYHK6B8YJT9M9BJA3",0,"MIT","https:\u002F\u002Fgithub.com\u002Fgaos6e\u002FMyOpenclaw\u002Fblob\u002Fmain\u002F.codex-openclaw\u002F.tmp\u002Fplugins\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,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"expo module","module","expo","use","native","type","shared","type system","objects","modules","hooks","writing","guide","kotlin","system","api","lifecycle","plugins","config","typescript","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":54,"description":7},"1.0.0","main","2f5832fbc22d173cdfdfb1eb0fbb00c0945c30fe",".codex-openclaw\u002F.tmp\u002Fplugins\u002Fplugins\u002Fexpo\u002Fskills\u002Fexpo-module","https:\u002F\u002Fgithub.com\u002Fgaos6e\u002FMyOpenclaw","https:\u002F\u002Fgithub.com\u002Fgaos6e","http:\u002F\u002Fwww.gzhu.edu.cn","2026-04-28 23:02:03",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add gaos6e\u002FMyOpenclaw --skill expo-module",{"tool":68,"command":69},"bunx","bunx skills add gaos6e\u002FMyOpenclaw --skill expo-module",{"tool":71,"command":72},"pnpm","pnpm dlx skills add gaos6e\u002FMyOpenclaw --skill expo-module","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgaos6e\u002FMyOpenclaw\u002Fblob\u002Fmain\u002F.codex-openclaw\u002F.tmp\u002Fplugins\u002Fplugins\u002Fexpo\u002Fskills\u002Fexpo-module\u002FSKILL.md",true,[76,82,86,90,94],{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fconfig-plugin.md","REFERENCE","参考文档",2040,"https:\u002F\u002Fgithub.com\u002Fgaos6e\u002FMyOpenclaw\u002Fblob\u002Fmain\u002F.codex-openclaw\u002F.tmp\u002Fplugins\u002Fplugins\u002Fexpo\u002Fskills\u002Fexpo-module\u002Freferences\u002Fconfig-plugin.md",{"path":83,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Flifecycle.md",3763,"https:\u002F\u002Fgithub.com\u002Fgaos6e\u002FMyOpenclaw\u002Fblob\u002Fmain\u002F.codex-openclaw\u002F.tmp\u002Fplugins\u002Fplugins\u002Fexpo\u002Fskills\u002Fexpo-module\u002Freferences\u002Flifecycle.md",{"path":87,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fmodule-config.md",1139,"https:\u002F\u002Fgithub.com\u002Fgaos6e\u002FMyOpenclaw\u002Fblob\u002Fmain\u002F.codex-openclaw\u002F.tmp\u002Fplugins\u002Fplugins\u002Fexpo\u002Fskills\u002Fexpo-module\u002Freferences\u002Fmodule-config.md",{"path":91,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fnative-module.md",5869,"https:\u002F\u002Fgithub.com\u002Fgaos6e\u002FMyOpenclaw\u002Fblob\u002Fmain\u002F.codex-openclaw\u002F.tmp\u002Fplugins\u002Fplugins\u002Fexpo\u002Fskills\u002Fexpo-module\u002Freferences\u002Fnative-module.md",{"path":95,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fnative-view.md",3590,"https:\u002F\u002Fgithub.com\u002Fgaos6e\u002FMyOpenclaw\u002Fblob\u002Fmain\u002F.codex-openclaw\u002F.tmp\u002Fplugins\u002Fplugins\u002Fexpo\u002Fskills\u002Fexpo-module\u002Freferences\u002Fnative-view.md",[99,134,161,184,207,231],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":114,"publishedAt":49},"01M6GRT346W34GHKHZAV2D772D","render-workflows","Sets up, develops, tests, and deploys Render Workflows. Covers first-time scaffolding (via CLI or manual), SDK installation (Python or TypeScript), task patterns (retries, subtasks, fan-out), local development, Dashboard deployment, and troubleshooting. Use when a user wants to set up Render Workflows for the first time, scaffold a workflow service, add or modify workflow tasks, test workflows locally, or deploy workflows to Render.","https:\u002F\u002Fgithub.com\u002Fgaos6e\u002FMyOpenclaw\u002Fblob\u002Fmain\u002F.codex-openclaw\u002F.tmp\u002Fplugins\u002Fplugins\u002Frender\u002Fskills\u002Frender-workflows\u002FSKILL.md",[105,108,111],{"categoryNo":106,"categoryName":107,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":109,"categoryName":110,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":112,"categoryName":113,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000033","数据分析师",[115,116,117,118,119,120,121,122,123,124,32,125,126,127,128,129,130,131,132,133],"workflows","render","render workflows","python","workflow","test","deployment","tasks","development","SET","up","task","scaffolding","time","local","tests","retries","local development","manual",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":143,"publishedAt":49},"01M6GRSXS3WAZ8XP752NS5JFRE","render-monitor","Monitor Render services in real-time. Check health, performance metrics, logs, and resource usage. Use when users want to check service status, view metrics, monitor performance, or verify deployments are healthy.","https:\u002F\u002Fgithub.com\u002Fgaos6e\u002FMyOpenclaw\u002Fblob\u002Fmain\u002F.codex-openclaw\u002F.tmp\u002Fplugins\u002Fplugins\u002Frender\u002Fskills\u002Frender-monitor\u002FSKILL.md",[140],{"categoryNo":141,"categoryName":142,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[144,145,116,146,147,148,149,150,151,152,153,154,155,156,32,157,128,158,159,160],"monitor","render monitor","MCP","cli","performance","status","metrics","logs","monitoring","Tools","real-time","check","view","deployments","healthy","render mcp","usage",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":168,"publishedAt":49},"01M6GRSRWTMQA26DZ7QKF8P8JH","render-migrate-from-heroku","Migrate from Heroku to Render by reading local project files and generating equivalent Render services. Triggers: any mention of migrating from Heroku, moving off Heroku, Heroku to Render migration, or switching from Heroku. Reads Procfile, dependency files, and app config from the local repo. Optionally uses Heroku MCP to enrich with live config vars, add-on details, and dyno sizes. Uses Render MCP or Blueprint YAML to create services.","https:\u002F\u002Fgithub.com\u002Fgaos6e\u002FMyOpenclaw\u002Fblob\u002Fmain\u002F.codex-openclaw\u002F.tmp\u002Fplugins\u002Fplugins\u002Frender\u002Fskills\u002Frender-migrate-from-heroku\u002FSKILL.md",[167],{"categoryNo":141,"categoryName":142,"taxonomyType":21,"taxonomyTypeDesc":22},[169,116,170,171,146,172,47,173,174,175,176,177,178,129,179,180,181,182,159,183],"migrate","heroku","render migrate from heroku","mcp server","create","verification","server","dependency","Blueprint","files","project","switching","creation","app","enrich",{"skillNo":185,"name":186,"nameZh":6,"description":187,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":188,"categories":189,"keywords":192,"publishedAt":49},"01M6GRSK7JJ10Z7KQ7KS4NPRP5","render-deploy","Deploy applications to Render by analyzing codebases, generating render.yaml Blueprints, and providing Dashboard deeplinks. Use when the user wants to deploy, host, publish, or set up their application on Render's cloud platform.","https:\u002F\u002Fgithub.com\u002Fgaos6e\u002FMyOpenclaw\u002Fblob\u002Fmain\u002F.codex-openclaw\u002F.tmp\u002Fplugins\u002Fplugins\u002Frender\u002Fskills\u002Frender-deploy\u002FSKILL.md",[190,191],{"categoryNo":106,"categoryName":107,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":141,"categoryName":142,"taxonomyType":21,"taxonomyTypeDesc":22},[193,194,116,146,195,147,196,197,198,199,200,201,124,125,177,202,203,204,205,206],"deploy","render deploy","image","dashboard","gitlab","git","repository","publish","analyzing","bitbucket","live","host","render cli","flows",{"skillNo":208,"name":209,"nameZh":6,"description":210,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":211,"categories":212,"keywords":220,"publishedAt":49},"01M6GRSDVM9AW4V8GWB6N5HHDG","render-debug","Debug failed Render deployments by analyzing logs, metrics, and database state. Identifies errors (missing env vars, port binding, OOM, etc.) and suggests fixes. Use when deployments fail, services won't start, or users mention errors, logs, or debugging.","https:\u002F\u002Fgithub.com\u002Fgaos6e\u002FMyOpenclaw\u002Fblob\u002Fmain\u002F.codex-openclaw\u002F.tmp\u002Fplugins\u002Fplugins\u002Frender\u002Fskills\u002Frender-debug\u002FSKILL.md",[213,216,217],{"categoryNo":214,"categoryName":215,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":141,"categoryName":142,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":218,"categoryName":219,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师",[221,222,116,146,147,223,224,150,151,225,226,201,153,32,157,227,159,228,229,230],"debug","render debug","debugging","database","env vars","start","Analyzing Logs","missing","port","errors",{"skillNo":232,"name":233,"nameZh":6,"description":234,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":235,"categories":236,"keywords":238,"publishedAt":49},"01M6GRRFJQKY22ZQRSAN91V9XR","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\u002Fgaos6e\u002FMyOpenclaw\u002Fblob\u002Fmain\u002F.codex-openclaw\u002F.tmp\u002Fplugins\u002Fplugins\u002Fplugin-eval\u002Ffixtures\u002Fminimal-skill\u002FSKILL.md",[237],{"categoryNo":141,"categoryName":142,"taxonomyType":21,"taxonomyTypeDesc":22},[239,240,241,242,243,244,32,245,246,247,130],"minimal skill","minimal","example skill","plugin","eval","user","example","compact","structured"]