[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6GR54C5CF9CKVBK1E9RYDSQ":3,"skill-same:01M6GR54C5CF9CKVBK1E9RYDSQ":72},{"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":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":14,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":6,"updatedAt":51,"install":52,"resources":65},"01M6GR54C5CF9CKVBK1E9RYDSQ","codex-expo-run-actions",null,"Wire Expo projects into the Codex app with project-local run scripts and .codex\u002Fenvironments\u002Fenvironment.toml actions. Use when the user wants the Codex app Run button, build\u002Frun actions, action buttons, or a stable Expo start\u002Frun workflow from Codex.","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\u002Fcodex-expo-run-actions\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"run","codex expo run actions","actions","expo","codex","run workflow","action","environments","with","scripts","app","toml","project","local","build","use","environment","projects","start","workflow","2026-11-10 10:12:30",false,"---\nname: codex-expo-run-actions\ndescription: Wire Expo projects into the Codex app with project-local run scripts and .codex\u002Fenvironments\u002Fenvironment.toml actions. Use when the user wants the Codex app Run button, build\u002Frun actions, action buttons, or a stable Expo start\u002Frun workflow from Codex.\nversion: 1.0.0\nlicense: MIT\n---\n\n# Codex Run Actions for Expo\n\nUse this skill to connect an Expo project to the Codex app action bar.\n\nThe goal is one project-local script plus `.codex\u002Fenvironments\u002Fenvironment.toml`,\nso the user can press `Run` in the Codex app and see the Expo CLI \u002F Metro logs in\nan action terminal.\n\n## Workflow\n\n1. Confirm the current workspace is an Expo app.\n   - Look for `package.json`.\n   - Look for `app.json`, `app.config.js`, `app.config.ts`, or `expo` in `package.json`.\n   - Do not wire the Codex action at a monorepo root if the Expo app is in a child package.\n\n2. Discover the package runner.\n   - Prefer the package manager declared in `packageManager`.\n   - Otherwise infer from lockfiles.\n   - The generated run script should still have a safe fallback to `npx expo`.\n\n3. Create or update `script\u002Fbuild_and_run.sh`.\n   - Use the reference file for the script shape.\n   - Default no-argument mode starts the Expo dev server: `expo start`.\n   - Keep the dev server in the foreground so the Codex action terminal owns logs and Ctrl-C behavior.\n   - Support optional modes for direct buttons:\n     - `--ios` starts Expo and opens iOS simulator.\n     - `--android` starts Expo and opens Android.\n     - `--web` starts Expo for web.\n     - `--dev-client` starts in dev-client mode.\n     - `--tunnel` starts a tunnel.\n     - `--export-web` exports web.\n\n4. Write `.codex\u002Fenvironments\u002Fenvironment.toml`.\n   - Always add or update one primary action named `Run`.\n   - Wire `Run` to `.\u002Fscript\u002Fbuild_and_run.sh`.\n   - Add direct `Run iOS`, `Run Android`, `Run Web`, or `Run Dev Client`\n     actions only when the user asks for those buttons or the project clearly needs them.\n   - If the environment file already exists, update the existing matching action instead of duplicating it.\n\n5. Use the action script as the default local run path.\n   - After wiring, run `.\u002Fscript\u002Fbuild_and_run.sh --help` or a short non-server mode if you need to sanity-check syntax.\n   - Do not start a long-lived Metro server during a setup-only task unless the user asked you to run the app.\n\n## References\n\n- `references\u002Fexpo-run-button-bootstrap.md`: canonical Expo `script\u002Fbuild_and_run.sh` and Codex environment action examples.\n\n## Guardrails\n\n- Try Expo Go \u002F `expo start` first; do not default the Codex Run button to `expo run:ios`, `expo run:android`, prebuild, or EAS Build.\n- Do not wire cloud actions such as `eas build`, `eas submit`, or store deployment into Codex buttons unless the user explicitly asks and accepts the auth \u002F time \u002F cost tradeoff.\n- Do not create a nested git repo.\n- Do not put secrets in `.codex\u002Fenvironments\u002Fenvironment.toml` or in the run script.\n- Do not background Metro from the run script; the action terminal should show the active server logs.\n- Do not hard-code npm if the project uses pnpm, yarn, or bun.\n\n## Output Expectations\n\nWhen setup changes are made, summarize:\n\n- the Expo app root you wired\n- the run script path\n- the Codex environment file path\n- the actions added or updated\n- how to launch the same path from shell\n","# Codex Run Actions for Expo\n\nUse this skill to connect an Expo project to the Codex app action bar.\n\nThe goal is one project-local script plus `.codex\u002Fenvironments\u002Fenvironment.toml`,\nso the user can press `Run` in the Codex app and see the Expo CLI \u002F Metro logs in\nan action terminal.\n\n## Workflow\n\n1. Confirm the current workspace is an Expo app.\n   - Look for `package.json`.\n   - Look for `app.json`, `app.config.js`, `app.config.ts`, or `expo` in `package.json`.\n   - Do not wire the Codex action at a monorepo root if the Expo app is in a child package.\n\n2. Discover the package runner.\n   - Prefer the package manager declared in `packageManager`.\n   - Otherwise infer from lockfiles.\n   - The generated run script should still have a safe fallback to `npx expo`.\n\n3. Create or update `script\u002Fbuild_and_run.sh`.\n   - Use the reference file for the script shape.\n   - Default no-argument mode starts the Expo dev server: `expo start`.\n   - Keep the dev server in the foreground so the Codex action terminal owns logs and Ctrl-C behavior.\n   - Support optional modes for direct buttons:\n     - `--ios` starts Expo and opens iOS simulator.\n     - `--android` starts Expo and opens Android.\n     - `--web` starts Expo for web.\n     - `--dev-client` starts in dev-client mode.\n     - `--tunnel` starts a tunnel.\n     - `--export-web` exports web.\n\n4. Write `.codex\u002Fenvironments\u002Fenvironment.toml`.\n   - Always add or update one primary action named `Run`.\n   - Wire `Run` to `.\u002Fscript\u002Fbuild_and_run.sh`.\n   - Add direct `Run iOS`, `Run Android`, `Run Web`, or `Run Dev Client`\n     actions only when the user asks for those buttons or the project clearly needs them.\n   - If the environment file already exists, update the existing matching action instead of duplicating it.\n\n5. Use the action script as the default local run path.\n   - After wiring, run `.\u002Fscript\u002Fbuild_and_run.sh --help` or a short non-server mode if you need to sanity-check syntax.\n   - Do not start a long-lived Metro server during a setup-only task unless the user asked you to run the app.\n\n## References\n\n- `references\u002Fexpo-run-button-bootstrap.md`: canonical Expo `script\u002Fbuild_and_run.sh` and Codex environment action examples.\n\n## Guardrails\n\n- Try Expo Go \u002F `expo start` first; do not default the Codex Run button to `expo run:ios`, `expo run:android`, prebuild, or EAS Build.\n- Do not wire cloud actions such as `eas build`, `eas submit`, or store deployment into Codex buttons unless the user explicitly asks and accepts the auth \u002F time \u002F cost tradeoff.\n- Do not create a nested git repo.\n- Do not put secrets in `.codex\u002Fenvironments\u002Fenvironment.toml` or in the run script.\n- Do not background Metro from the run script; the action terminal should show the active server logs.\n- Do not hard-code npm if the project uses pnpm, yarn, or bun.\n\n## Output Expectations\n\nWhen setup changes are made, summarize:\n\n- the Expo app root you wired\n- the run script path\n- the Codex environment file path\n- the actions added or updated\n- how to launch the same path from shell\n",{"name":5,"license":15,"version":44,"description":7},"1.0.0","main","2f5832fbc22d173cdfdfb1eb0fbb00c0945c30fe",".codex-openclaw\u002F.tmp\u002Fplugins\u002Fplugins\u002Fexpo\u002Fskills\u002Fcodex-expo-run-actions","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":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add gaos6e\u002FMyOpenclaw --skill codex-expo-run-actions",{"tool":58,"command":59},"bunx","bunx skills add gaos6e\u002FMyOpenclaw --skill codex-expo-run-actions",{"tool":61,"command":62},"pnpm","pnpm dlx skills add gaos6e\u002FMyOpenclaw --skill codex-expo-run-actions","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgaos6e\u002FMyOpenclaw\u002Fblob\u002Fmain\u002F.codex-openclaw\u002F.tmp\u002Fplugins\u002Fplugins\u002Fexpo\u002Fskills\u002Fcodex-expo-run-actions\u002FSKILL.md",true,[66],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fexpo-run-button-bootstrap.md","REFERENCE","参考文档",4972,"https:\u002F\u002Fgithub.com\u002Fgaos6e\u002FMyOpenclaw\u002Fblob\u002Fmain\u002F.codex-openclaw\u002F.tmp\u002Fplugins\u002Fplugins\u002Fexpo\u002Fskills\u002Fcodex-expo-run-actions\u002Freferences\u002Fexpo-run-button-bootstrap.md",[73,110,137,159,182,205],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":92,"publishedAt":39},"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",[79,84,87],{"categoryNo":80,"categoryName":81,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",{"categoryNo":85,"categoryName":86,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[93,94,95,96,38,97,98,99,100,101,34,102,103,104,105,32,106,107,108,109],"workflows","render","render workflows","python","test","deployment","tasks","development","SET","up","task","scaffolding","time","tests","retries","local development","manual",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":119,"publishedAt":39},"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",[116],{"categoryNo":117,"categoryName":118,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000023","Skill与智能体开发",[120,121,94,122,123,124,125,126,127,128,129,130,131,132,34,133,105,134,135,136],"monitor","render monitor","MCP","cli","performance","status","metrics","logs","monitoring","Tools","real-time","check","view","deployments","healthy","render mcp","usage",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":144,"publishedAt":39},"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",[143],{"categoryNo":117,"categoryName":118,"taxonomyType":82,"taxonomyTypeDesc":83},[145,94,146,147,122,148,149,150,151,152,153,154,155,32,31,156,157,29,135,158],"migrate","heroku","render migrate from heroku","mcp server","config","create","verification","server","dependency","Blueprint","files","switching","creation","enrich",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":167,"publishedAt":39},"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",[165,166],{"categoryNo":80,"categoryName":81,"taxonomyType":82,"taxonomyTypeDesc":83},{"categoryNo":117,"categoryName":118,"taxonomyType":82,"taxonomyTypeDesc":83},[168,169,94,122,170,123,171,172,173,174,175,176,101,102,154,177,178,179,180,181],"deploy","render deploy","image","dashboard","gitlab","git","repository","publish","analyzing","bitbucket","live","host","render cli","flows",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":195,"publishedAt":39},"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",[188,191,192],{"categoryNo":189,"categoryName":190,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":117,"categoryName":118,"taxonomyType":82,"taxonomyTypeDesc":83},{"categoryNo":193,"categoryName":194,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000030","开发工程师",[196,197,94,122,123,198,199,126,127,200,37,176,129,34,133,201,135,202,203,204],"debug","render debug","debugging","database","env vars","Analyzing Logs","missing","port","errors",{"skillNo":206,"name":207,"nameZh":6,"description":208,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":209,"categories":210,"keywords":212,"publishedAt":39},"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",[211],{"categoryNo":117,"categoryName":118,"taxonomyType":82,"taxonomyTypeDesc":83},[213,214,215,216,217,218,34,219,220,221,106],"minimal skill","minimal","example skill","plugin","eval","user","example","compact","structured"]